Use LUADOC console command to get a list of engine functions. "import" is not a statement, it's a function. Basically, the lua core is LuaPlus, so most of the changes: ~= as well as != # and -- for comments no need to use an iterator on a table in "for k, v in table do" construct continue ... and all the other 'improvements' provided by LuaPlus. Though it uses lua 5.0 as a base, so there are coup
[quote who="BulletMagnet" reply="2" id="1983385"] that said, there's another solution to this (depending on what you want to do); give each mod it's own scratch file (or better yet, folder) that's isolated from the others and the rest of the computer. [/quote] That's not really a solution, there's already the LOG / prefs file you can write stuff to. Also, I'm not only speaking about I/O. Mostly about loading new libs (socket, md5, struct or whatever). Moreover the
It does tell you.
One of the biggest cons of supcom in terms of moddability was the inability to use the io module and load external libraries. It'd be great if the loading of "dangerous" libraries could be switched on with a command line argument. (as far as I know it's pretty simple to enable / disable builtins of lua in c...) That way GPG could make the user take all responsibility when manually creating a shortcut and enabling the command line... (or so I hope, I'm not sure how this goes le
I've been having the same problem, no matter what the fps display always stays around 20-30 fps both in low and high fidelity. I'd suggest using fraps, that shows the proper fps. This issue doesn't happen with supcom.
Demigod Forums