- GameConnection::getPlayerName() - It would be nice if the auth system referenced the client's base name, not what this function returns; the main practical use of having a function like this to me seems to be so I could parent it if I wanted to have custom names for an RPG mod or somesuch, but unfortunately doing this causes authfails without massive amounts of hacking. ie parenting workaround variables onto something like 20 other functions, and even then half of it doesn't seem to work perfectly.
The purpose of the moving the client name into a set/get function is to prevent people from changing it and impersonating other users. Your name is your name. You can't be an impersonating friend anymore. Sorry.
- BLB Downloading - Now I don't think this is likely to make it into V13, but come on, Badspot. You made this big format and it sees so little use because people have to go and find the right copy of the mod to see any of it - why hasn't this been in since the advent of BLBs? If people don't want to download them, it's not like you couldn't add a 'Download Custom Bricks' option.
The Torque resource manager is completely forgeted. It took an incredible amount of effort just to be able to connect to a server, download files, and not crash (there are still some crash/invalid packet bugs in v12 that are fixed for v13). I do not want to rewrite it right now.
- Event system upgrades - now I'm not 110% sure on this, but I believe that a lot of the WrenchEventsDlg is hardcoded so that new objects will cause problems. One could, in theory, add an input event logic/arguments dialog when you select an input event, but I don't believe that dynamically adding to the format of an event line in the GUI would be feasible.
On top of that, it may also be nice to have a 'Default Targets' list for adding targets like the Named Brick input (ie on every event), or a per-client list argument (like the named brick list but for event arguments and of other types). I know it seems like I'm whining, but this stuff may possibly allow for some quite unique event sets.
That isn't even coherent enough to read, let alone program.
- That engine fix that Trader wanted since something like four versions ago.
Right, let me use my time traveling mind rays to figure out wtf you're talking about.
- The ability to enable/disable default events
Some default events may cause issues for specific servers running certain Add-Ons. An easy way to enable and disable events would be most appreciated by many.
unRegisterInputEvent(%class,%name)
unRegisterOutputEvent(%class,%name)