Difference between revisions of "Running Bug List"

Revision as of 23:46, 22 September 2012

This is a running bug list.

General Bugs

1. 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 haven't duplicated in a long while...
2. Flip (H, V) of test items, flags, and other items seems broken (i.e. no effect)
3. 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
4. repair always does the circle around your ship, even if at full health
5. the level-changer '+' on other players seems to go away after switching levels
6. Core debris doesn't disappear
7. Editor core rendering problem. Add a Core, move it, then press <tab> : http://sam686.maxhushahn.com/upload/1111screenshot_5.png
8. (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
9. Can't type in game lobby when there are no servers
10. /idle command needs a timer to stop people from un-idling too fast (to prevent abuse) (implemented client-side only)
11. if you hold down the fire button, energy doesn't recharge at normal rate (easy to see with Mine set as the weapon)
12. editor geometric sorting is not working -- repairs can be under zones (for example).
13. turret will not shoot resource item if it is in line with a ship on the same team, even if the ship is behind resource item (sorting problem?)
14. Can't chat in lobby when server list is not empty (before the problem was, can't chat with empty server list)
15. Phaser hitting a Barrier makes a different sound now?
16. sam686 found something else that needs to go here
17. fix bots after Lua stabilizes (already stable?)
18. spybug not included in stats
19. Ship::isInZone always returns NULL, this makes energy jumpy client-side when on a loadout zone
20. Fix the bug detailed here: http://bitfighter.org/forums/viewtopic.php?f=28&t=1533 Basically, we need to print an error message when BF is started with wrong parameters
21. Fix twoplayer.bat
22. Sensor zoom isn't smooth when using sensor until out of energy
23. Modules are shown as always 'on' to other players (recent pack/unpackUpdate changes?)
24. Green help text for entering level change password is too long and is cut off screen
25. Modules sometimes get stuck 'on'. It is fixed when you are killed Easily happens when holding down mouse button, move mouse off the Bitfighter window, then release mouse button. SDL problems? (only on windows?)
26. Typing in chat windows should reset idle timer
27. mounted item problems when cloaked: resources aren't being hidden and nexus flag count isn't shown
28. Escaping out of game lobby, then going back in quickly, makes player names disappear
29. heat seeker goes through walls!
30. TextItems + Bitfighter logo sometimes disappear when still on screen - probably extents issue?
31. Badges aren't updated after earned in scoreboard unless you rejoin game server
32. When pressing alt-tab to leave the game window, game still thinks alt is down when you return to that window. Test by pressing enter -- if window changes mode (like it does with alt-enter) then the bug has manifested itself
33. heat seeker graphics
34. Fix music (remove in lobby, add variety to in-game)
35. Fix editor Tab after moving and adding any of: Spybug, Mine, Resource, Asteroid, and all MoveObject. Mostly fixed, but doesn't update Spybug and Tab's moveObjects while dragging.
36. Editor: Can't change team names after testing level, probably bad cast problem.
37. When engineering a teleporter, if the level ends, and you've been idle for a while, you get locked out of the game until you press Escape. We should better handle this situation, rare as it is! (Should exit helper when level ends.)
38. When making a screenshot, size should be standardized at 800x600.; current bahavior is to use the current window dimensions. This regression may have been intentional, so feel free to make a case for keeping it the way it is as an alternative to fixing this bug.
39. Inner layer of destroyed Core panel should be Core team color (but lighter, like in 017)
40. Show engineered teleporter green outline in commander's view
41. Fade in cloaked ships if sensor is equipped, by applying an alpha modifier based on distance
42. Apply BBB badge hierarchy so you can be granted multiple in the database, but only the highest valued is displayed
43. Level changer scoreboard mark '+' isn't always shown with several clients?
44. Laying own mines sometimes are shown dimmed (found in single-team bitmatch)
45. Can lay two spybugs really fast sometimes
46. Shaky commander's map when other player ships move
47. spybug's don't actually work: if enemy ships go out of player's scope, they're never picked up by your spybugs

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!