Difference between revisions of "Running Bug List"

Revision as of 17:46, 21 March 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. When teleporting on top of walls (layered walls?) sometimes a player gets stuck and cannot move or commit suicide. This may be hard to track down.
5. One black screen of doom case left: Open two clients; don't move in one to let spawn delay kick in (30 seconds); go to a /next level, the first should now be spawn delayed; go to /next level again, the first cannot come back to game now
6. 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
7. When a script deletes a ff projector, bobdaduck reports the ff is not also removed. Also problematic: setTeams, setLoc, etc. Basically anything with FFPs don't appropriately update the attached FF
8. /shuffle is broken...
9. Disable fast regen when standing still trying to build something with engineer
10. Ship is rendered behind repair items?
11. Public Lua API members for the 'Item' object should probably be moved somewhere more appropriate. See http://bitfighter.org/luadocs/class_item.html isOnShip() should not apply to EngineeredItem, etc.
12. Clean-up master chat commands. Add consistency; /raptor -> /pm raptor etc.
13. Lua API setHealth on Turrets/FFs not working
14. health items set at no regen still regen at default rate
15. Quartz' kaen test euthanasia:
    • Ghost ship hitting an energy item
    • Set teleporter entrance == exit; set Delay=0 (should we remove this?)
    • ghost (neutral) ship touching a levelgen'd zone (goalzone did the job)
16. Lua API doc fixes:
    • event method signatures are not documented
    • 'LuaPlayerInfo' class?
    • what happen to the 'Ship' methods?
17. Lua event onShipSpawned isn't triggered when starting a level already connected to a server. the 'suppressEvents' part of EventManager::fireEvent(EventType eventType, Ship *ship) [EventManager.cpp:292] returns true in this case for some reason

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