Difference between revisions of "Running Bug List"

From Bitfighter
(General Bugs)
(General Bugs)
Line 17: Line 17:
 
# Credits doesn't reset scrolling when you leave and enter in again real quick (Destructor issue?)
 
# Credits doesn't reset scrolling when you leave and enter in again real quick (Destructor issue?)
 
# Joining a game already running won't show your badges in the scoreboard until next level
 
# Joining a game already running won't show your badges in the scoreboard until next level
# Game segfaults on start-up if no Lua scripts exist (e.g. if the scripts folder is empty)
+
# <del>Game segfaults on start-up if no Lua scripts exist (e.g. if the scripts folder is empty)</del>
  
 
===Things that really should be done===
 
===Things that really should be done===

Revision as of 03:10, 22 October 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.
  5. (defer to 019) Shaky commander's map when other player ships move out of bounds
  6. (defer to 019) Handle case of script adding items beyond max level bounds
  7. Seeker sound effects?
  8. 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
  9. /idle command timer is wholly client-side - open to hack
  10. Seeker client-side prediction isn't so great (will go through forcefields, while burst doesn't)
  11. Credits doesn't reset scrolling when you leave and enter in again real quick (Destructor issue?)
  12. Joining a game already running won't show your badges in the scoreboard until next level
  13. Game segfaults on start-up if no Lua scripts exist (e.g. if the scripts folder is empty)

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!