Hi!

This package contains lots of useful tools for Manila3D Lua5.1 editing. You can find here a compiler a decompiler, a small script repository at post #3 and ExtLua, which provides developers the possibility to extend M3D's functionality.

Also check m9editor which is a really great application to edit mode9 files by 6Fg8!
And check Manila kitchen project which hosts the decompiled scripts with a LUA IDE and everything ready to go.
You might want to try out mode9 converter too.

ChangeLog

LuaDec 2.0

• Finds out where locals are
• Read more here

• Some changes regarding LDS(2) strings and for loops (it's still a bit unstable)
• LuaDec has a new option to disassemble instead of decompile
• The provided lua package (lua, luac and luadec) is now unicode compilant, it will read and write the unicode variants of the scripts instead of the ascii variants.
• Read more here

• Added LDS2 support to both luadec and luac
• Fixed OP_TFORLOOP handling
• Read more here

• Improved luadecguesser with fast mode
• Fixed a crashing when encountering boolean values
• Increases happy face rate in XDA-developers forum
• Read more here

• Improved luadecguesser
• Read more here

• Upvalue handling
• Added a brute-force local variable searcher application
• Read more here

• Generic for loop handling
• Improved local variable handling
• Read more here

• Initial release
• Read more here

• Less crashing
• More decompiling
• Read more here

• Decompiling simpler scripts and recompiling them will result in a semantically identical compiled lua script!
• Numeric for loops are fixed, they should work fine
• Complex boolean expressions and conditional statements will make luadec crash
• Only works with ascii files. Don't forget to convert the lua files to ascii then back to unicode

• Luadec will output a "-- Lua5.1" or "-- Warning" comment to lines, where you should check the output.
• If luadec crashes try running it with the "-d" parameter to acquire as much information as you can.
• Compile your lua files with the "-s" parameter set.
• It was compiled with Visual C++ 2008, so you might need the MSVC++ 2008 redistributables too.
• Valid Numbers are in range from -32768.0 to 32767.0. Numbers not in this range will be cropped by the compiler.
• There is a decompilation tutorial starting here

Does not work for me.

Succesfully decompiled scripts

All rhodium and rhodium2 scripts:
http://winmo.sztupy.hu/manilakitchen.html

Run an application:

Shell_NavigateTo(command,parameters)

Add an eventhandler to an event: (thx D-MAN666)

object.EventName:connect(functionRef, scopeRef);
object.EventName:disconnect(functionRef, scopeRef);

Where events can be: onPress, onRelease, onReleaseOutside

Example (from 4aefb03d_manila):

require("hitfeedback")
OnPhotoTouchPress = function(loc_0)
   gnPhotoTouchPressY = loc_0._ymouse
   Camera3DHitFeedback:Press()
end
PhotoHitTarget.onPress:connect(OnPhotoTouchPress)

Originally Posted by sztupy  

More detail please... no output? crash ? missing dlls?

It simply return "cannot execute this file", tested on XP and Win7 beta

do you have to do something first at manila files?
for me say bad headers!

@udk : i'm running on win 7 beta too and it's working in CMD...

Originally Posted by utopykzebulon  

@udk : i'm running on win 7 beta too and it's working in CMD...

That's strange, maybe I miss some files.

Originally Posted by udK  

It simply return "cannot execute this file", tested on XP and Win7 beta

Do you have the MS Visual C++ 2008 redistributables? (MSVCR9 and MSVCP9)

Originally Posted by utopykzebulon  

do you have to do something first at manila files?
for me say bad headers!

@udk : i'm running on win 7 beta too and it's working in CMD...

did you unicode2ansi them?

Originally Posted by sztupy  

did you unicode2ansi them?

yes it's work onw thx man
For "ERROR_nil" you have to decompile lua files with chunkspy and correct it manually

Originally Posted by utopykzebulon  

yes it's work onw thx man
For "ERROR_nil" you have to decompile lua files with chunkspy and correct it manually

I' now comparing the VM docs of 5.0 and 5.1 and I'm comparing the changes. I already corrected a lot of bugs, so in the next version you might not even need chunkspy