Running Bug List
From Bitfighter
Revision as of 09:41, 13 June 2013 by Watusimoto (Talk | contribs)
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
- Fix (or kill) /suspend command. Removed client-side by raptor Do we need to remove the server ability to suspend client?
- Figure out how to get ids working properly with walls/polywalls
- 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.temporary workarounds in 4d6f2a48d254 and 01414236b4ed
-
- Disable fast regen when standing still trying to build something with engineer
- 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'?
- 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
- 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.
- in onShipLeftZone/etc. events with 'ship' object, either the ship or the ship:getPlayerInfo() doesn't return the same userdata object each time anymore
- Start game with joystick plugged in; remove joystick; go to Options>Input... crash! Can't even get a stack trace in Windows!
- Shooting a burst or mine while in commander's map makes the map flicker -- Can reproduce on Windows if I have the sensor in my loadout
Things to test after next lua rewrite
- 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