Difference between revisions of "Running Bug List"

Revision as of 11:21, 16 May 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
   • sam686: repeated /addbots /kickbots kindof leaks memory and won't free memory until after running LuaScriptRunner::shutdown() which is normally run only when quitting. Check if everything is freed when a robot is removed.
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! See: http://pastie.org/7818433
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. Render order issues:
    • ships render under flags
    • Objective arrows rendering on top of F2 display
    • server messages/ loadout boxes render on top of F2 level info display
13. 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.
14. Engineer needlessly uses energy here: http://sam6.25u.com/upload/text1304/130414_17-04-58.txt. --Raptor 11:21, 16 May 2013 (UTC) Duplicated. This is because the forcefield isn't in scope so client thinks it can place. Server denies the placement, but client side subtracts energy and server/client are out of sync with energy
15. When running with no joysticks attached, get this message on the system console: Error opening joystick 1 [(null)]
16. Refine graphics for asteroid spawners
17. Scoreboard should be fancy box?
18. /idle always respawns you after 5 seconds (no key press needed)
19. in onShipLeftZone/etc. events with 'ship' object, either the ship or the ship:getPlayerInfo() doesn't return the same userdata object each time anymore
20. 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), It's because uiManager->isCurrentUI(NameEntryUI) is returning 'true' in UserInterface::onKeyDown(), I don't know why yet..
21. Editor team crash with LineItems is back!. This time I got it on valgrind: http://pastie.org/pastes/7898569/text
22. Start game with joystick plugged in; remove joystick; go to Options>Input... crash! Can't even get a stack trace in Windows!

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