Difference between revisions of "Running Bug List"

Revision as of 01:25, 10 November 2012

This is a running bug list.

General Bugs

1. (Mac) Cursor disappears when pressing <ESC> in a game to access the menus. Possible SDL2 problem? seems to happen when alt-tab away first on 10.6
2. Fix twoplayer.bat
3. Fix music (remove in lobby, add variety to in-game)
4. Level changer scoreboard mark '+' isn't always shown with several clients? When admin use "/setlevpass" the '+' status doesn't update.

1. Seeker sound effects?
2. Put this in the bot documentation: logprint(debug.traceback()) prints stack trace See http://bitfighter.org/forums/viewtopic.php?f=12&t=14&view=unread&sid=294322f71fe40d0344d26186b94317a6#unread
3. /idle command timer is wholly client-side - open to hack
4. Seeker client-side prediction isn't so great (will go through forcefields, while burst doesn't)
5. Joining a game already running won't show your badges in the scoreboard until next level
6. (Windows) WONTFIX Game pauses when moving window. See here for problem description and solution: http://stackoverflow.com/questions/7450156/c-sdl-application-pauses-when-dragged Basically the solution is to render in a different thread.. so defer until a long time...
7. Two turrets or the same team on top of each other don't fire at enemies/TestItems/etc. when near.. was in 015a don't care..
8. Client-side prediction problems with TestItem (MoveItem?). Duplicate by hosting a level with a TestItem and pushing it around, you'll see the TestItem jump around like it had lag. Happens with resources and soccer balls, too.. Also increasing lag (with /lag ), you can see that client-side doesn't predict collisions with MoveItems really well..
9. Instructions are probably wrong: look for static ControlStringsEditor consoleCommands1[] and verify this actually works.
10. Arbitrary resizing of walls in editor doesn't render the newly created walls, only the spines
11. When soccer ball is just a tiny bit on the top of the screen (i.e. mostly off screen), it appears to flicker (scope issue?)
12. Need something to tell players they can hit enter to edit attributes of items in the editor (instructions, in-editor message, something)
13. In editor, space disables grid snapping, and shift+space disables grid + vertex snapping. This works fine if you press shift then press space, but does not work if you are holding space, then press sift (as is natural to do). This should be fixed. The problem is probably in string InputCodeManager::makeInputString(InputCode inputCode); the editor works properly, but the keycode Shift+Space does not get generated properly if shift is not pressed first.
14. Editor fullscreen only goes stretched at lower resolution now..
15. Add note to comments in INI file that you can configure quick chat to enter /commands
16. Add new joystick profile: http://bitfighter.org/forums/viewtopic.php?f=4&t=1608

Things that really should be done

1. Master writeConnectRequest() should send gameType as a stringTableEntry rather than a straight string. Easy change, but will break compatibility with the master unless we're clever.

ideas

1. A /nextmap feature to determine what the next map will be would be quite helpful
2. Currently, Bitfighter prevents players from switching teams multiple times... instead, I think Bitfighter should prevent any player from purposely stacking the teams. Ex. If it's 8v7, no player on the team with 7 should be allowed to switch over to the team with 8. This would also need a toggle however, otherwise it would break dungeons.
3. rotate/scale commands -- make use new quickmenus we created for plugins, also id menu (! or #)
4. Get rid of getValueForDisplayingInMenu() or of getOptionText()... seem to do similar thing in menus
5. /maplist to view the maps on the server would be nice. Make it a toggle if the server owner wants privacy
6. shield countdown timer
7. Why do we have MD5 classes in 'zap/' when we have libtomcrypt? Should we consolidate them? Yes, if possible! Keep the ones in libtomcrypt, and create a friendly wrapper for in-game use.
8. When tons of bots, remove some from scoreboard to avoid making text too small... include some note like (+ 10 more robots). Remove lower scoring ones first.
9. Add level rating system (+1/0/-1) as described in forums citation needed!