so this is basicly [lua]CompileString(file.Read("path"),"somename)[/lua]
Oh and will this be available in the menustate?
I'd assume so, pretty much
[lua]local luafunc = CompileFile("data/whatever.txt")
luafunc()[/lua]
I'm assuming it works as per the [url=http://bbservers.co.uk/gmodbt/view.php?id=4]request[/url]. As using include but compiling a file instead.
Whats the point ? I suppose it would be faster if you compile the file at the start and run it atm you need it. But i dont see any use for that.
[QUOTE=ColdFusion;27775449]Whats the point ? I suppose it would be faster if you compile the file at the start and run it atm you need it. But i dont see any use for that.[/QUOTE]
You could run it in a limited environment.
[QUOTE=Wizard of Ass;27745186]so this is basicly [lua]CompileString(file.Read("path"),"somename)[/lua]
Oh and will this be available in the menustate?[/QUOTE]
No, it reads Lua files from the Lua folder, not normal saved Lua files.
[QUOTE=garry;27794075]No, it reads Lua files from the Lua folder, not normal saved Lua files.[/QUOTE]
"../" big difference...
But still, will this be available in the menustate?
There's a huge difference between loading from lua path and adding ../ infront of everything.
Sorry, you need to Log In to post a reply to this thread.