Difference between revisions of "Running Bug List"

Revision as of 14:58, 28 April 2013

This is list of our current high-priority bugs for Bitfighter.

Not all issues belong on this list -- only those that are a high priority for the next release. Other cases should be added to the Google Code bug tracker.

General Bugs

1. Joining a game already running won't show your badges in the scoreboard until next level. Existing clients get info on the joiner, but joiner doesn't get the full 411 on the existing players. GameType::serverAddClient::s2cAddClient isn't sending proper badge info to joiner.
2. Fix (or kill) /suspend command. Removed client-side by raptor Do we need to remove the server ability to suspend client?
3. Figure out how to get ids working properly with walls/polywalls
4. Fix memory leak with robots/levelgen because of disabling every luaW_hold<T>(L, obj); --> use reference counting to delete proxy when appropriate, and reenable this line
5. Disable fast regen when standing still trying to build something with engineer
6. Clean-up master chat commands. Add consistency; /raptor -> /pm raptor etc.
7. Lua API doc fixes:
   • event method signatures are not documented
   • Check that all the old the Lunar classes mentioned at http://bitfighter.org/wiki/index.php/Scripting_018 are also in the luadocs.
   • How to document the global enums 'WeaponInfo' 'ModuleInfo'?
8. Bobdaduck's Lua API crashes:
   • create and delete a spybug each tick, then shoot the spybug. crash!
9. Improve screen for loading levels in editor -- perhaps general keyword search, or options for picking by author/title/file, or perhaps navigating a folder tree
10. Remove access to dangerous Lua libraries (esp. os and io) See http://lua-users.org/wiki/SandBoxes for ideas.
11. Bot balancing bug: 3 people join on two teams, balance to 6 players. then all humans go on the same team. Result: bots's don't rebalance and you're left with 4 on 2.
12. Sneaking suspicion that if one client is spawnDelayed, the server is delayed too
13. Render order issue -- ships render under flags
14. Objective arrows rendering on top of F2 display
15. bitfighter.ini [QuickChatMessages] is empty with missing comments after a newer version of Bitfighter is run, when "[Settings] version=" is older. Comments only appears after "[QuickChatMessages]" is removed and bitfighter is run.
16. Engineer needlessly uses energy here: http://sam6.25u.com/upload/text1304/130414_17-04-58.txt
17. When running with no joysticks attached, get this message on the system console: Error opening joystick 1 [(null)]
18. /showzones spikes CPU on commander's map (bug in 018a, too) (only on maps with lots and lots of zones)
19. Font artifacts still exist? Switch screen modes make them apparent in-game
20. Leaving a level hosted in the editor triggers botzone building again. Trace of when it is called: http://pastie.org/7669397 Does not happen in 018a
21. Editor team crash with LineItems is back!: http://pastie.org/7677652
22. Refine graphics for asteroid spawners
23. Scoreboard should be fancy box?
24. Really weird segfault on game shutdown: http://pastie.org/pastes/7727826/text
25. /idle always respawns you after 5 seconds (no key press needed)
26. Typing in chat will move your ship (a,s,d,f)
27. Picking up a resource with engineerwill not show it client-side on you ship. Instead the resource stays rendered at where you picked it up. Everything is working server-side though.
28. Something has gone wrong with CLientInfo:
    • Crash 1: http://pastie.org/7731600
    • Crash 2: http://pastie.org/7731621
29. in onShipLeftZone/etc. events with 'ship' object, either the ship or the ship:getPlayerInfo() doesn't return the same userdata object each time anymore
30. pressing F5 for global chat in-game is broken Watusimoto 18:58, 28 April 2013 (MSK) F5 loads the chat window properly on my latest build (did not test functionality beyond that)
31. If you get kicked from a server while idle, when you rejoin, you're stuck in 'press any key to continue' mode
32. Owner commands on F1 Help screen have gone missing
33. /shutdown command should be an owner command

Things to test after next lua rewrite

1. Levelgen: Having addItem() in main() may randomly fail on repeated ctrl+R in editor or repeated level restart, showing message "***LEVELGEN ERROR*** Error encountered while attempting to run script's main() function: ***.levelgen:44: attempt to call missing or unknown method 'addItem' (a nil value). Aborting script."

   -- for bug #33 from sam686
function main()
  for x = 0, 20 do
    for y = 0, 20 do
      item2 = ResourceItem.new()
      item2:setGeom(x * 100, y * 100)
      levelgen:addItem(item2)
      textitem = TextItem.new()
      textitem:setText(x .. "," .. y)
      textitem:setGeom(x * 100, y * 100, x * 100 + 100, y * 100)
      levelgen:addItem(textitem)
    end
  end
end