Homeworld 2 : DumpsLog
Karos Graveyard ::
Function Reference :: Scope Reference :: Variable Reference
Most recent edit on 2006-01-19 19:07:20 by MiKail

Additions:
bin\profiles\profile1\playercfg.lua [can't dump, no namespaces recognized]
data\locale\english\scripts\keybindings.lua [can't dump, even if quoted (curiously, no errors are produced if quoted)]

Deletions:
pin\profiles\profile1\playercfg.lua [can't dump, no namespaces recognized]


Edited on 2006-01-19 03:31:35 by MiKail

Additions:
data\leveldata\multiplayer\deathmatch.lua [can dump]
dostring
data\ui\newui\main\new\newmainmenu.lua [can dump if quoted]
data\art\battlescar\default.lua [can't dump]
data\effect\hyperspaceeffecttweaks.lua [can't dump]
bin\driverConfig.lua [can't dump]
data\scripts\startingfleets\vaygr00.lua [can't dump]
data\ai\cpumilitary.lua [can dump]
bin\autoexec.lua [can dump]
data\scripts\attack\dogfight.lua [can't dump]
*.campaign [can't dump, no namespaces recognized]
data\scripts\debugfunctions.lua
data\scripts\flightmaneuvers.lua [can't dump]
data\scripts\utilityfunctions.lua [can't dump]
pin\profiles\profile1\playercfg.lua [can't dump, no namespaces recognized]

Deletions:
deathmatch.lua [can dump]
newmainmenu.lua [can dump if quoted]
art\battlescar\default.lua [can't dump]
effects\hyperspaceeffecttweaks.lua [can't dump]
driverConfig.lua [can't dump]
vaygr00.lua [can't dump]
cpumilitary.lua [can dump]
autoexec.lua [can dump]
dogfight.lua [can't dump]
*.campaign [can't dump, namespaces.lua returned nothing]
scripts\debugfunctions.lua
scripts\flightmaneuvers.lua [can't dump]
scripts\utilityfunctions.lua [can't dump]


Edited on 2006-01-19 03:24:05 by MiKail

Additions:
It's important to know if the globals(), print(), and dofilepath() functions are accessible, since these functions can be used to glean information about a particular script's environment, or scope. I think that print() and dofilepath() are in the same library, so only one of them has to be checked for, and not both.

Deletions:
It's important to know if the globals(), print(), and dofilepath() functions are accessible, since these functions can be used to glean information about a particular script's environment, or scope. I think that print() and dofilepath() are in the same library, so I think that only one of them has to be checked for, and not both.


Edited on 2006-01-19 03:23:45 by MiKail

Additions:
It's important to know if the globals(), print(), and dofilepath() functions are accessible, since these functions can be used to glean information about a particular script's environment, or scope. I think that print() and dofilepath() are in the same library, so I think that only one of them has to be checked for, and not both.

Deletions:
It's important to know if the globals(), print(), and dofilepath() functions are accessible, since these functions can be used to glean information about a particular script's environment, or scope. I think that print() and dofilepath() are in the same library, so they maybe only have to be checked for once, and not twice.


Edited on 2006-01-19 03:23:00 by MiKail

Additions:
It's important to know if the globals(), print(), and dofilepath() functions are accessible, since these functions can be used to glean information about a particular script's environment, or scope. I think that print() and dofilepath() are in the same library, so they maybe only have to be checked for once, and not twice.

Deletions:
It's important to know if the globals(), print(), and dofilepath() functions are accessible, since these functions can be used to glean information about a particular script. I think that print() and dofilepath() are in the same library, so they maybe only have to be checked for once, and not twice.


Edited on 2006-01-19 03:22:28 by MiKail

Additions:
It's important to know if the globals(), print(), and dofilepath() functions are accessible, since these functions can be used to glean information about a particular script. I think that print() and dofilepath() are in the same library, so they maybe only have to be checked for once, and not twice.

Deletions:
It's important to know in which files the globals(), print(), and dofilepath() functions are accessible, since these functions can be used to glean information about a particular script. I think that print() and dofilepath() are in the same library, so they maybe only have to be checked for once, and not twice.


Edited on 2006-01-19 03:22:03 by MiKail

Additions:
This page lists the status of various files in regards to whether a successful dump was accomplished using them. Also listed is whether certian functions can be called from within them.

Deletions:
Here is a list of files and their status in regards to whether a successful dump has been accomplished using them. Also listed are whether other functions can be called within them.


Edited on 2006-01-19 03:19:54 by MiKail

Additions:
It's important to know in which files the globals(), print(), and dofilepath() functions are accessible, since these functions can be used to glean information about a particular script. I think that print() and dofilepath() are in the same library, so they maybe only have to be checked for once, and not twice.

Deletions:
It's important to know in which files the globals(), print(), and dofilepath() functions are accessible, since these help you to learn the most about a particular file. I think that print() and dofilepath() are in the same library, so you may only have to check for one and not both.


Edited on 2006-01-19 03:18:03 by MiKail

Additions:
Note that many LUA files have no (or almost no) scope -- they are simply storage for tables and variables. Sometimes, you can get around this if a table stores function calls in strings, which are executed later. This is the case among many of the UI LUAs, as well as the event tables in gametype LUAs.

Deletions:
Note that many LUA files have no (or almost no) scope - they just store tables and variables. Sometimes, you can get around this by quoting the function, and thus storing it as a variable that is parsed at a later time. This is the case among many of the UI LUAs, as well as the event tables in gamerule LUAs.


Edited on 2005-09-12 19:42:13 by MiKail

Additions:
Here is a list of files and their status in regards to whether a successful dump has been accomplished using them. Also listed are whether other functions can be called within them.
It's important to know in which files the globals(), print(), and dofilepath() functions are accessible, since these help you to learn the most about a particular file. I think that print() and dofilepath() are in the same library, so you may only have to check for one and not both.
dofilepath
globals
The 'HW2_' functions seem to only work in campaigns, for some reason.
*.level [can't dump]
dofilepath
getn
tinsert
globals
dofilepath
globals [if quoted]
globals [if unquoted]
*.resource, *.ship, *.missile, etc. [can dump]
globals
dofilepath
art\battlescar\default.lua [can't dump]
globals
effects\hyperspaceeffecttweaks.lua [can't dump]
globals
dofilepath
driverConfig.lua [can't dump]
globals
vaygr00.lua [can't dump]
dofilepath
globals
dofilepath
globals
dofilepath
globals
*.madstate [can't dump]
dofilepath
globals
dogfight.lua [can't dump]
dofilepath
globals
*.campaign [can't dump, namespaces.lua returned nothing]
dofilepath
globals
*.events [can't dump]
globals
scripts\debugfunctions.lua
not loaded by the game engine by default
scripts\flightmaneuvers.lua [can't dump]
globals
scripts\utilityfunctions.lua [can't dump]
globals

Deletions:
Dump/Scope Log Discussionhttp://forums.relicnews.com/showthread.php?t=66996
Here is a list of files and their status in regards to whether a successful dump has been accomplished using "ThoughtDump.lua". Also listed are whether it was or wasn't possible to call some other functions within them. If you wish to add to this list, please choose a type of file that hasn't been done before.
It's important to know in which files the globals(), print(), and dofilepath() functions are accessible, since these provide the most about a particular file. I think that print() and dofilepath() are in the same library, so you may only have to check for one and not both.
If "ThoughtDump.lua" doesn't work, then you could also try "PrintNamespaces.lua". This will at the very least provide a list of namespaces.
print
dofilepath
globals
namespaces
luaATI
luacamera
luacampaign
luacpu
luafx
luagamesettings
luahyperspace
lualight
LuaMenuSupport
luanis
luaobjectives
luaping
luaplayer
luasensor
luasound
luasubtitle
luateamactions
luateamquery
luauniverse
luauserinterface
statlogging
*.level
print
dofilepath
getn
tinsert
globals
namespaces
lualoadlevel
luasound
luafog
lualight
print
dofilepath
globals [if quoted]
globals [if unquoted]
execute
namespaces
debugrender
luaappmainui
luaappmisc
luagameio
LuaMenuSupport
luauserinterface
*.resource
dofilepath
namespaces
dofilepath
namespaces
driverConfig.lua
globals
namespaces
vaygr00.lua
dofilepath
globals
namespaces
print
dofilepath
globals
namespaces
statlogging
print
dofilepath
globals
namespaces
debugrender
luaappmainui
luaappmisc
luacamera
luagameio
luagamemainui
luagamemisc
luagamesettings
LuaMenuSupport
luaplayer_console
luarender
luauniverse
luauserinterface
dogfight.lua
dofilepath
globals
namespaces
*.subs
print
dofilepath
namespaces
none according to PrintLibraries.lua
build.lua
dofilepath
print
globals
namespaces
none according to PrintLibraries.lua
<ship>.events
dofilepath
print
globals
namespaces
none according to PrintLibraries.lua
<ship>.madstate
dofilepath
print
globals
namespaces
none according to PrintLibraries.lua
Related Pages:
<ship>.events
none
<ship>.madstate
none


Edited on 2005-07-01 23:51:25 by MiKail

Additions:
*.level
driverConfig.lua
vaygr00.lua
*.madstate
dogfight.lua

Deletions:
*.level [can't dump]
driverConfig.lua [can't dump]
vaygr00.lua [can't dump]
*.madstate [can't dump]
dogfight.lua [can't dump]


Oldest known version of this page was edited on 2005-07-01 23:50:26 by MiKail []
Page view:
Dump/Scope Log Discussionhttp://forums.relicnews.com/showthread.php?t=66996

Here is a list of files and their status in regards to whether a successful dump has been accomplished using "ThoughtDump.lua". Also listed are whether it was or wasn't possible to call some other functions within them. If you wish to add to this list, please choose a type of file that hasn't been done before.

It's important to know in which files the globals(), print(), and dofilepath() functions are accessible, since these provide the most about a particular file. I think that print() and dofilepath() are in the same library, so you may only have to check for one and not both.

If "ThoughtDump.lua" doesn't work, then you could also try "PrintNamespaces.lua". This will at the very least provide a list of namespaces.

Note that many LUA files have no (or almost no) scope - they just store tables and variables. Sometimes, you can get around this by quoting the function, and thus storing it as a variable that is parsed at a later time. This is the case among many of the UI LUAs, as well as the event tables in gamerule LUAs.


deathmatch.lua [can dump]
did work
dofilepath
globals
didn't work
namespaces
luaATI
luacamera
luacampaign
luacpu
luafx
luagamesettings
luahyperspace
lualight
LuaMenuSupport
luanis
luaobjectives
luaping
luaplayer
luasensor
luasound
luasubtitle
luateamactions
luateamquery
luauniverse
luauserinterface
statlogging


*.level [can't dump]
did work
dofilepath
didn't work
getn
tinsert
globals
namespaces
lualoadlevel
luasound
luafog
lualight

newmainmenu.lua [can dump if quoted]
did work
dofilepath
globals [if quoted]
didn't work
globals [if unquoted]
execute [even if quoted]
namespaces

*.resource
did work
didn't work
dofilepath
namespaces

music.lua
did work
didn't work
dofilepath
namespaces

driverConfig.lua [can't dump]
did work
didn't work
globals
namespaces

vaygr00.lua [can't dump]
did work
dofilepath
didn't work
globals
namespaces

cpumilitary.lua [can dump]
did work
dofilepath
globals
didn't work
namespaces

autoexec.lua [can dump]
did work
dofilepath
globals
didn't work
namespaces
debugrender
luaappmainui
luaappmisc
luacamera
luagameio
luagamemainui
luagamemisc
luagamesettings
LuaMenuSupport
luaplayer_console
luarender
luauniverse
luauserinterface

*.madstate [can't dump]
did work
dofilepath
didn't work
globals
namespaces

dogfight.lua [can't dump]
did work
dofilepath
didn't work
globals
namespaces

*.subs
did work
didn't work
dofilepath
namespaces

build.lua
did work
dofilepath
didn't work
globals
namespaces

Related Pages:
Page History :: 2006-01-19 19:07:20 XML :: Owner: MiKail ::
:: ::