Running Bug List
From Bitfighter
Contents |
This is a running bug list.
General Bugs
- Sometimes a forcefield seems undestroyable: seems to be only client-side? Can still heal it after shooting the project for a while, but the field always shows active
- Flip (H, V) of test items, flags, and other items seems broken (i.e. no effect)
- In the editor, when your mouse is over the object palette but no object is highlighted, if you click and drag, the mouse changes to the 4 arrows making it seem like you should be able to move the palette itself
ideas
- A /nextmap feature to determine what the next map will be would be quite helpful
- 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.
- rotate/scale commands -- make use new quickmenus we created for plugins, also id menu (! or #)
- Get rid of getValueForDisplayingInMenu() or of getOptionText()... seem to do similar thing in menus
- /maplist to view the maps on the server would be nice. Make it a toggle if the server owner wants privacy
- shield countdown timer
-
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. - 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.
