Difference between revisions of "Running Bug List"

From Bitfighter
(→‎General Bugs)
(→‎General Bugs: cleanup)
Line 8: Line 8:
  
 
# 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.
 
# 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.
−
# <del>When all players on a server go /idle, something bad happens</del>
 
−
# <del>Black screen of death reported with /idle.  Maybe we should look into preventative measures like forcing menu to be available still, etc..</del>
 
−
# <del>When testing a level, enter full screen unstretched, then go back to editor, then test level again.  You will now be in fullscreen stretched.</del>
 
−
# <del>Editor fullscreen scaling sticks around when leaving editor</del>
 
−
# <del>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.</del>
 
−
# <del>Slashes/backslashes mixed on F7 screen for windows</del>
 
−
# <del>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</del>
 
−
# <del>When starting standalone version, console flashes and grabs good icon; does not happen in installed version (windows only)</del>
 
 
#: (sam686) The install version have bficon.bmp with bitfighter.exe, while your stand alone version may be missing bficon.bmp in exe folder, bficon.bmp is in resource folder.  Try putting bficon.bmp to where your exe is to allow your standalone to have icon.
 
#: (sam686) The install version have bficon.bmp with bitfighter.exe, while your stand alone version may be missing bficon.bmp in exe folder, bficon.bmp is in resource folder.  Try putting bficon.bmp to where your exe is to allow your standalone to have icon.
−
# <del>The carrot in 'rabbit' is not the right color</del>
 
−
# <del>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</del>
 
−
# <del>Asteroids don't start with an initial velocity upon level load</del>
 
−
# <del>Bots without getName() will crash game in debug mode with stack dirty assert</del>
 
−
# <del>Zone ids aren't saved in editor</del>
 
−
# <del>addToGame() on objects in Lua scripts has gone missing..</del> ''looks like you use levelgen:addItem()''
 
−
# <del>Generic 'Zone' doesn't trigger ShipEnteredZone (ShipLeftZone untested) event.  LoadoutZone works.</del>
 
−
# <del>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.</del>
 
 
# Fix (or kill) /suspend command
 
# Fix (or kill) /suspend command
−
# <del>Can we get Zones out of the pseudoitem list the way we did with spawns?</del>
 
−
# <del>Spazzy forcefield snapping in the editor</del>
 
−
# <del>Players running in debug mode (i.e. me and raptor and sam) shouldn't show up on json player list ||| [[User:Watusimoto|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 </del>
 
−
# <del>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</del>
 
 
# 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
 
# 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
−
# <del>Assign all objects a user-assigned id upon construction.  Make these negative so as to not interfere with user assigned ones.</del>
 
−
# <del>Need better error handling for timer events that cause errors in levelgens.</del>
 
−
# <del>If ship dies on a zone, fire onLeftZone</del>
 
−
# <del>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 </del>
 
−
# <del>teleporting onto asteroid with flag causes flag to remain behind</del>
 
−
# <del>burst explosions only add x-direction momentum to testitems.  was in 018, too; bobdaduck says it was in Zap! also</del>
 
 
# Figure out how to get ids working properly with walls/polywalls
 
# Figure out how to get ids working properly with walls/polywalls
−
# <del>/showbots should not work on production game server -- test server only!</del>
 
−
# <del>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</del>
 
 
# 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."
 
# 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 [[User:Kaen|Kaen]] 01:33, 31 December 2012 (MSK)
 
#:I was unable to reproduce, we need a test case [[User:Kaen|Kaen]] 01:33, 31 December 2012 (MSK)
Line 45: Line 17:
 
# Can't kill your own turrets with burst weapon (like you can on older 017) - why? (other weapons works fine)
 
# 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 <tt>Zap::GameType::objectCanDamageObject()</tt> before dealing damage. In this function a check is performed for the value of <tt>GameWeapon::weaponInfo[weaponType].canDamageTeammate</tt> which is false for bursts, mines, and spybugs. [[User:Kaen|Kaen]] 02:56, 31 December 2012 (MSK)
 
#:The reason is that burst weapons (unlike projectile weapons) call <tt>Zap::GameType::objectCanDamageObject()</tt> before dealing damage. In this function a check is performed for the value of <tt>GameWeapon::weaponInfo[weaponType].canDamageTeammate</tt> which is false for bursts, mines, and spybugs. [[User:Kaen|Kaen]] 02:56, 31 December 2012 (MSK)
−
# <del>If spawn on loadout, loadout should immediately update</del>
 
−
# <del>Client side FFs seem to not be blocking ships or projectiles</del>
 
−
# <del>Test updater fix.  ''raptor tested (once), it works''</del>
 
 
# When joining a game, a player should go to the team with the most bots on it already
 
# When joining a game, a player should go to the team with the most bots on it already
 
# Test bots correctly join a team that has fewer players
 
# Test bots correctly join a team that has fewer players
 
# When teleporting on top of walls (layered walls?) sometimes a player gets stuck and cannot move or commit suicide
 
# When teleporting on top of walls (layered walls?) sometimes a player gets stuck and cannot move or commit suicide
−
# <del>music folder still taken from 'program files' on Windows 7? <== appears not </del>
 
−
# <del>integer overflow when bringing back 20000+ flags to the nexus at once (amgine's favorite bug) <=== deferred to 019 </del>
 
 
# Cannot move forcefield further along the wall to the right in this picture:  http://sam6.25u.com/upload/5screenshot_4.png  Issue is in EngineeredItem::findAnchorPointAndNormal()
 
# Cannot move forcefield further along the wall to the right in this picture:  http://sam6.25u.com/upload/5screenshot_4.png  Issue is in EngineeredItem::findAnchorPointAndNormal()

Revision as of 04:31, 18 January 2013

Contents

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.
    (sam686) The install version have bficon.bmp with bitfighter.exe, while your stand alone version may be missing bficon.bmp in exe folder, bficon.bmp is in resource folder. Try putting bficon.bmp to where your exe is to allow your standalone to have icon.
  2. Fix (or kill) /suspend command
  3. 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
  4. Figure out how to get ids working properly with walls/polywalls
  5. 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
  6. 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)
  7. When joining a game, a player should go to the team with the most bots on it already
  8. Test bots correctly join a team that has fewer players
  9. When teleporting on top of walls (layered walls?) sometimes a player gets stuck and cannot move or commit suicide
  10. Cannot move forcefield further along the wall to the right in this picture: http://sam6.25u.com/upload/5screenshot_4.png Issue is in EngineeredItem::findAnchorPointAndNormal()
Retrieved from "http://bitfighter.org/wiki/index.php?title=Running_Bug_List&oldid=4857"