Difference between revisions of "Running Bug List"

From Bitfighter
(ideas)
(General Bugs)
Line 8: Line 8:
 
# Editor: Testing a level with flagitems will put them at 0,0.  If map is save afterwards, they are at 0,0 when loaded up next time
 
# Editor: Testing a level with flagitems will put them at 0,0.  If map is save afterwards, they are at 0,0 when loaded up next time
 
# Crash when copy/pasting forcefields?
 
# Crash when copy/pasting forcefields?
 +
# ldw keys not working in host menu... regression since 017a
  
 
=== ideas ===
 
=== ideas ===

Revision as of 09:33, 28 April 2012

This is a running bug list.

General Bugs

  1. F5 doesn't exit global chat
  2. Editor: Testing a level with flagitems will put them at 0,0. If map is save afterwards, they are at 0,0 when loaded up next time
  3. Crash when copy/pasting forcefields?
  4. ldw keys not working in host menu... regression since 017a

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.