Difference between revisions of "Running Bug List"

Revision as of 05:45, 7 January 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. When all players on a server go /idle, something bad happens
3. Black screen of death reported with /idle. Maybe we should look into preventative measures like forcing menu to be available still, etc..
4. When testing a level, enter full screen unstretched, then go back to editor, then test level again. You will now be in fullscreen stretched.
5. Editor fullscreen scaling sticks around when leaving editor
6. If game can't write to level folder (simulate by adding .standalone to install folder on windows, for example), testing a level will fail (obviously), but will not tell you why until you press escape.
7. Slashes/backslashes mixed on F7 screen for windows
8. Start Bitfighter, edit a level with forcefields (but do not test) quit, then host, you will get spurious forcefields. Beautiful!: http://sam6.25u.com/upload/2screenshot_21.png
9. When starting standalone version, console flashes and grabs good icon; does not happen in installed version (windows only)
10. The carrot in 'rabbit' is not the right color
11. Teleporters will only teleport one ship at a time regardless of the number of ships on it. Result: most dungeons are now broken... I can't remember if we did this deliberately
12. Asteroids don't start with an initial velocity upon level load
13. Bots without getName() will crash game in debug mode with stack dirty assert
14. Zone ids aren't saved in editor
15. addToGame() on objects in Lua scripts has gone missing.. looks like you use levelgen:addItem()
16. Generic 'Zone' doesn't trigger ShipEnteredZone (ShipLeftZone untested) event. LoadoutZone works.
17. Make sure players can only get credit for playing game once, even if they are logged in with multiple clients using the same name. The stats may already work this way, just think we should double check.
18. Fix (or kill) /suspend command
19. Can we get Zones out of the pseudoitem list the way we did with spawns?
20. Spazzy forcefield snapping in the editor
21. Players running in debug mode (i.e. me and raptor and sam) shouldn't show up on json player list ||| Watusimoto 20:10, 6 January 2013 (MSK) ==> This is essentially done, needs master rebuild and incrementing MASTER_PROTOCOL_VERSION to 6 to ensure it is working
22. Editor: pressing up/down while holding down left or right fails to scroll diagonal (to scroll left and up at the same time) See: http://code.google.com/p/bitfighter/issues/detail?id=187#c1
23. Scripting bug: items should have consistent userdatas throughout the game. Test with player enter zone/player exit zone. Ids should be the same, but aren't. Example: 'ship' userdata is different in enteredZone and leftZone events for the same ship
24. Assign all objects a user-assigned id upon construction. Make these negative so as to not interfere with user assigned ones.
25. Need better error handling for timer events that cause errors in levelgens.
26. If ship dies on a zone, fire onLeftZone
27. Engineer a teleporter from a resource item created by a script, then have the script remove the resource item. Upon destruction of the teleporter, crash! because resource item was removed. Possible solution: don't revert engineered item to resource item, just let it quietly be destroyed
28. teleporting onto asteroid with flag causes flag to remain behind
29. burst explosions only add x-direction momentum to testitems. was in 018, too; bobdaduck says it was in Zap! also
30. Figure out how to get ids working properly with walls/polywalls
31. /showbots should not work on production game server -- test server only!
32. Editor funkiness: when editing polygons, middle mouse drag does some weird stuff. Only way to undo is to select affected poly and then undo; bare undo has no effect. NOT FIXED, BUT CAN NO LONGER REPRODUCE. PERHAPS OTHER FIXES ADDRESSED THIS AS WELL
33. 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."

    I was unable to reproduce, we need a test case Kaen 01:33, 31 December 2012 (MSK)

    -- 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

34. Can't kill your own turrets with burst weapon (like you can on older 017) - why? (other weapons works fine)

    The reason is that burst weapons (unlike projectile weapons) call Zap::GameType::objectCanDamageObject() before dealing damage. In this function a check is performed for the value of GameWeapon::weaponInfo[weaponType].canDamageTeammate which is false for bursts, mines, and spybugs. Kaen 02:56, 31 December 2012 (MSK)

35. If spawn on loadout, loadout should immediately update
36. Client side FFs seem to not be blocking ships or projectiles
37. Test updater fix