Difference between revisions of "Running Bug List"

Revision as of 23:18, 27 February 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
3. Figure out how to get ids working properly with walls/polywalls Can be deferred
4. 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

5. When joining a game, a player should go to the team with the most bots on it already. Not necessarily true.. removing
6. Test bots correctly join a team that has fewer players. Test passed.
7. 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 and not worth the effort before 018a. Can be deferred
8. Fix/finish /announce command
9. Armor problem: either put slide back, or remove completely. Discuss (probably want to keep it for 018a)
10. 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
11. Editor teams crash again??: http://bitfighter.org/forums/viewtopic.php?f=29&t=1726 ==> Last post suggests this bug has been fixed. Is this still current? No.
12. Investigate reports that flags disappear in CTF when a client holding one disconnects Watusimoto 14:26, 17 February 2013 (MSK) Could not reproduce on 018 client/server -- tested with geowar, 1 hosting player, and two remote clients; 1 remote client held flag and quit; flag was visible to both remaining players; tested twice with similar scenarios; did not observe problem. That, and there is a dismountAll() call in the ship destructor, so I don't see how this could really happen. I say close the case unless someone can reproduce it. Unreproducible by raptor, as well
13. engineer teleport disables chat
14. 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
15. Check rabbit single-team colors (also maybe team colors) with bots added to the level after level start
16. Editor: are object IDs supposed to be displayed now?
17. Mac PPC: Editor: Some sort of endian problem with dragging vertices in the editor. Reported by Fordcars, verified by raptor. Trying to drag 1 vertex on an object will sometimes drag muliple vertices
18. Editor bug: add a Core, copy it, paste it, arbitrary rotate it. Press <tab> and you'll see the positioning problems
19. Adding a SoccerBall with a levelgen script crashes game after interacting with a zone. This happens because there is no spawn point in non-soccer games. Fixed by adding a spawn point at starting position if it is a Lua created ball
20. Transmit new stats to master -- all stats marked with xx in gameStats.h should be pushed up to master with a new version of versionedStats