TODO:

Tremulous | Website | Coding |
  1. Fix the titling CSS
    On narrow windows, not all of the title will fit. It should wrap, but this is gonna be difficult to reconcile with the floating (and more to the point, the body going under the title).
  2. MGDev
    Norf 'noticed that going from printing to walking keeps the sprinting-level stamina drain', adv granger doesn't take fall damage if ww is on, Item_Text_Wrap continues to cause issues for me.
  3. Fix my line-breaking and tabbing issues
    Much of my website is lovely and indented for super source readability, but it turns out that Firefox includes these indents in its copy/paste along with the newlines I use to keep things convenient for vim. In order to make my website more copiable, I really need to poke around, un-indenting the website and using alternative methods to re-establish readability. The portfolio is an example of where I've started this practice.
  4. Decide on a content licence for the Sauerbraten map
    The textures, source code, and map files are made free to download but by the rules of my Licensing page, rights to distribution, modification etc. are still held. It is my full intention to release everything under a fairly permissive licence, but I need to read one first. Still. I hope I don't just public domain everything out of sheer laziness again.
  5. Adapt !info system to mgdev's help window
    mgdev has a help system whereby users get a neat tabulated presentation of some helpful information in text form. It's pretty and easy to use but the text is hard-coded and therefore inflexible. My server-delivered info system allows for customisability on a per-server basis, which allows for a wider range of uses or applications. The system of transmitting this information across the network is inefficient but well worth it if properly implemented.
  6. Rewrite buildlog/revert
    Rereading the revert code recently, I've seen a number of ways in which it could be improved: basically all of the logging stuff should be functionalised, as currently they make a big mess everywhere. This would be a good opportunity as well to cut down on the bloat that surrounds the function, as really the Swiss-Army knife it is now mostly serves to confuse its users.
  7. Make basilisks emit little hearts as they run along
    No, I don't have any sane justification for this.
    Yes, it most certainly would be awesome.
  8. Get some advertising
    I want cash to fund all sorts of things, and Google's program is unobtrusive and stylish, although its actual level of revenue is to be doubted. Other appealing options include Project Wonderful, although I think I might need a greater viewership to make it worthwhile.
  9. Inform buildlog of how much teamdamage some buildable took
    Medic: 'When a structure get's TKed, wouldn't it be nice to see how much hp was lost in game and in the buildlog? I think it could help settle that arguement of "hey man, don't ban me, I only put the last shot on it."'
  10. Better damage feedback for buildables.
    Currently, thumping an mgturret with a few well-placed tyrant swipes gets you nothing but a clunk sound. Constructing buildables don't even give that. Alien buildables should bleed like alien players, and human buildables should spit little shards of metal at you. Damaged human buildables should spit sparks, thicker smoke, perhaps even behave erratically. Some buildables need a [better] death animation, although that's not really my field.
  11. Update my documentation
    I maintain a list on this website of contributions I've made to Tremulous' source, but it has not been updated for some time, and I've come a long way as a developer since then. I need to catalogue this work properly, for my own benefit as much as anyone else's
  12. Give funds for bleeding
    We've all been in those rifle-tyrant deadlocks, where it's quite simply impossible to get that final shot in. Although perhaps biasing towards humans (unless I implemented the floating-point alien system) this could prove an interesting game mechanic (and a solution for those moments where you desperately want a shotgun but have 149 creds in the bank)
  13. Visual feedback for credit income
    Sometimes credits can be added and you don't even notice, let alone know why. Some kind of UI item that highlighted when you gained or lost credits and perhaps even a reason (e.g. Dretch: 175) would look pretty cool and might be genuinely useful.
  14. Learn C++
    Bit of a big one, this, but shouldn't be too hard given my C knowledge base. Knowledge of C++ should finally put me in a position to a) mod Sauerbraten and b) finally get onto that collaborative text editor project that I've been thinking about for some time.
  15. Make and release a serious mod
    I've a few ideas knocking around, including a spinup chaingun, shell-loading shotgun, stream lasgun etc. that I think deserve an airing. Most of these are done, however releasing them together as a mod is something I've not yet managed.
    Things to be in it: