Karos Graveyard Wiki
(reword)
Tag: sourceedit
(formatting)
Tag: sourceedit
Line 7: Line 7:
   
   
===data\leveldata\multiplayer\deathmatch.lua===
+
==data\leveldata\multiplayer\deathmatch.lua==
 
;status
 
;status
 
:can dump
 
:can dump
Line 17: Line 17:
   
   
===.level===
+
==.level==
 
;status
 
;status
 
:can't dump
 
:can't dump
Line 32: Line 32:
   
   
===data\ui\newui\main\new\newmainmenu.lua===
+
==data\ui\newui\main\new\newmainmenu.lua==
 
;status
 
;status
 
:can dump if quoted
 
:can dump if quoted
Line 43: Line 43:
   
   
===.resource, .ship, .missile, etc.===
+
==.resource, .ship, .missile, etc.==
 
;status
 
;status
 
:can dump
 
:can dump
Line 53: Line 53:
   
   
===data\art\battlescar\default.lua===
+
==data\art\battlescar\default.lua==
 
;status
 
;status
 
:can't dump
 
:can't dump
Line 62: Line 62:
   
   
===data\effect\hyperspaceeffecttweaks.lua===
+
==data\effect\hyperspaceeffecttweaks.lua==
 
;status
 
;status
 
:can't dump
 
:can't dump
Line 71: Line 71:
   
   
===music.lua===
+
==music.lua==
 
;status
 
;status
 
;did work
 
;did work
Line 79: Line 79:
   
   
===bin\driverConfig.lua===
+
==bin\driverConfig.lua==
 
;status
 
;status
 
:can't dump
 
:can't dump
Line 88: Line 88:
   
   
===data\scripts\startingfleets\vaygr00.lua===
+
==data\scripts\startingfleets\vaygr00.lua==
 
;status
 
;status
 
:can't dump
 
:can't dump
Line 98: Line 98:
   
   
===data\ai\cpumilitary.lua===
+
==data\ai\cpumilitary.lua==
 
;status
 
;status
 
:can dump
 
:can dump
Line 108: Line 108:
   
   
===bin\autoexec.lua===
+
==bin\autoexec.lua==
 
;status
 
;status
 
:can dump
 
:can dump
Line 118: Line 118:
   
   
===.madstate===
+
==.madstate==
 
;status
 
;status
 
:can't dump
 
:can't dump
Line 128: Line 128:
   
   
===data\scripts\attack\dogfight.lua===
+
==data\scripts\attack\dogfight.lua==
 
;status
 
;status
 
:can't dump
 
:can't dump
Line 138: Line 138:
   
   
===.campaign===
+
==.campaign==
 
;status
 
;status
 
:can't dump, no namespaces recognized
 
:can't dump, no namespaces recognized
Line 148: Line 148:
   
   
===.events===
+
==.events==
 
;status
 
;status
 
:can't dump
 
:can't dump
Line 157: Line 157:
   
   
===data\scripts\debugfunctions.lua===
+
==data\scripts\debugfunctions.lua==
   
 
;not loaded by the game engine by default
 
;not loaded by the game engine by default
Line 163: Line 163:
   
   
===data\scripts\flightmaneuvers.lua===
+
==data\scripts\flightmaneuvers.lua==
 
;status
 
;status
 
:can't dump
 
:can't dump
Line 172: Line 172:
   
   
===data\scripts\utilityfunctions.lua===
+
==data\scripts\utilityfunctions.lua==
 
;status
 
;status
 
:can't dump
 
:can't dump
Line 181: Line 181:
   
   
===bin\profiles\profile1\playercfg.lua===
+
==bin\profiles\profile1\playercfg.lua==
 
;status
 
;status
 
:can't dump, no namespaces recognized
 
:can't dump, no namespaces recognized
Line 191: Line 191:
   
   
===data\locale\english\scripts\keybindings.lua===
+
==data\locale\english\scripts\keybindings.lua==
 
;status
 
;status
 
:can't dump, even if quoted (curiously, no errors are produced if quoted)
 
:can't dump, even if quoted (curiously, no errors are produced if quoted)

Revision as of 12:04, 5 August 2017

This page lists the status of various files in regards to whether they were successfully used to create a dump.

It is important to know if the globals, print, write and dofilepath functions are accessible, since these functions can be used to glean information about a particular script's environment (a.k.a. scope), or are very important to how mods work.

Note that many LUA files have no (or almost no) functions working in them -- they are simply storage containing tables and variables. Sometimes, you can get around this if a table stores function calls within strings that are executed at a later time. This is the case among UI button presses and mouse clicks, as well as the event tables in gametype LUAs.


data\leveldata\multiplayer\deathmatch.lua

status
can dump
did work
dofilepath
globals
didn't work


.level

status
can't dump
did work
dofilepath
didn't work
getn
tinsert
globals
dostring
dofile
call


data\ui\newui\main\new\newmainmenu.lua

status
can dump if quoted
did work
dofilepath
globals [if quoted]
didn't work
globals [if unquoted]


.resource, .ship, .missile, etc.

status
can dump
did work
globals
didn't work
dofilepath


data\art\battlescar\default.lua

status
can't dump
did work
didn't work
globals


data\effect\hyperspaceeffecttweaks.lua

status
can't dump
did work
didn't work
globals


music.lua

status
did work
didn't work
dofilepath


bin\driverConfig.lua

status
can't dump
did work
didn't work
globals


data\scripts\startingfleets\vaygr00.lua

status
can't dump
did work
dofilepath
didn't work
globals


data\ai\cpumilitary.lua

status
can dump
did work
dofilepath
globals
didn't work


bin\autoexec.lua

status
can dump
did work
dofilepath
globals
didn't work


.madstate

status
can't dump
did work
dofilepath
didn't work
globals


data\scripts\attack\dogfight.lua

status
can't dump
did work
dofilepath
didn't work
globals


.campaign

status
can't dump, no namespaces recognized
did work
dofilepath
didn't work
globals


.events

status
can't dump
did work
didn't work
globals


data\scripts\debugfunctions.lua

not loaded by the game engine by default


data\scripts\flightmaneuvers.lua

status
can't dump
did work
didn't work
globals


data\scripts\utilityfunctions.lua

status
can't dump
did work
didn't work
globals


bin\profiles\profile1\playercfg.lua

status
can't dump, no namespaces recognized
did work
dofilepath
didn't work
globals


data\locale\english\scripts\keybindings.lua

status
can't dump, even if quoted (curiously, no errors are produced if quoted)
did work
dofilepath
didn't work
globals