New F2 compiler/decompiler

noid · Post by **noid** » Sun Feb 02, 2003 5:49 pm

There is a new compiler / decompiler for fallout 2 at:

http://members.fortunecity.com/noid84/c ... mpiler.zip

Documentation isn't finished yet, but there is a start.

Comments anyone?

Helios2000 · Post by **Helios2000** » Sun Feb 02, 2003 11:19 pm

Cool a new Compiler/Decompiler but it donÃƒâ€šÃ‚Â´t work:
decompile:2452:in `require': No such file to load -- getoptlong (LoadError)
from decompile:2452

this is my problem.

noid · Post by **noid** » Mon Feb 03, 2003 4:58 am

[quote="Helios2000"]

decompile:2452:in `require': No such file to load -- getoptlong (LoadError)

from decompile:2452

this is my problem.[/quote]

Does this file exist ?:

c:\usr\local\lib\ruby\1.6\getoptlong.rb

If not then the interpreter was not installed into the root directory.

The ruby interpreter must be installed into the root directory of the drive so that it can find all the libraries.

Let me know if this helps.

Helios2000 · Post by **Helios2000** » Mon Feb 03, 2003 3:35 pm

Sorry but the interpreter is korekt installed.I have the files in c:\usr\local\lib\ruby\1.6\

ABel · Post by **ABel** » Tue Feb 04, 2003 7:18 am

The ruby interpreter must be installed into the root directory of the drive so that it can find all the libraries.

The interpreter can be installed in any directory of any drive (I have installed it into d:\lang\ruby\ instead of c:\usr\local\).
The libraries are searched relatively to location of ruby.exe.

The compiler and decompiler are great!
They both work with native Interplay's syntax. Import/export of variables and even of functions is supported. There are also those "indirect" subroutine calls. This is simply amazing!
Where did you get all the information? And why you used that strange interpreted language, is there any way to make a Win32-executable?

Jargo · Post by **Jargo** » Tue Feb 04, 2003 9:04 am

Yes :D Abel is right this (deco/co) mpiler is great.
Importing/exporting values cool!!! Great job
But native interplay names are little hard to understand why not make it compatible with ipp.
And the ssl file is not very readable in "txt edytor" what edytor you use?

But it is great job!!! :wink:

Helios2000 · Post by **Helios2000** » Wed Feb 05, 2003 12:19 am

Now it work.
IÃƒâ€šÃ‚Â´dont know why but it works!
The comp/decom is very great!!!

noid · Post by **noid** » Wed Feb 05, 2003 2:55 am

[quote="ABel"]

Where did you get all the information? And why you used that strange interpreted language, is there any way to make a Win32-executable?[/quote]

I got the Interplay syntax from the KA compiler docs. The KA compile.exe was used to compile simple test programs, which I then hand disassembled to work out how that compiler works. To work out everything and write the compiler / decompiler took about a month.

I used the ruby language as it is really good for writing prototypes. There is no ruby to C converter, but I will probably rewrite the decompiler / compiler into C (at some stage) and post a native windows version.

noid · Post by **noid** » Wed Feb 05, 2003 3:02 am

[quote="Jargo"]But native interplay names are little hard to understand why not make it compatible with ipp.

And the ssl file is not very readable in "txt edytor" what edytor you use?[/quote]

The interplay names are those used by the original interplay compiler (examine fallout2.exe with a hex editor to see them). I use these names as I feel they are more "correct".

The problems with the ssl not being readable is my fault. I do all my development under unix where the end of line is "\n", but under windows the end of line is "\r\n". Wordpad.exe should be able to read and edit the ssl files.

Red · Post by **Red** » Wed Feb 05, 2003 3:07 am

Remember that BIS might release their own compiler (I officially got this information, though when's another story, so (IMHO) it's better to support BIS's format over IPP since then we could later possibly simply convert the code into the native compiler (though maybe at that point we might not want to do that if too many features were added not supported in the original compiler).

To that effect I was wondering wether that import/export stuff was really supported in the normal compiler or wether this was something added...

It's nice though to see it in ruby since this means anyone can fiddle with the code fgiven a bug is found without even recompiling...

I started decompiling the entire Fallout2 scripts to see if I can find discripencies. Great work!

Oh and for the command line ABel's perfectly right. you just need to make sure that the lib directory is properly placed in relation to the EXE (and that the DLL is found beside the EXE of course). Although I'm using the mswin32 port of ruby. Here's my extraction line:

Code: Select all

E&#58;\games\Fallout2_extracted_reference\data\scripts>for %a in &#40;*.int&#41; do @D&#58;\apps\ruby\bin\ruby \games\falloutdec\decompile %a

Jargo · Post by **Jargo** » Wed Feb 05, 2003 12:58 pm

Thx Noid, It's cool that your compiler/docomplier is open source. :wink:
I have compiled many script's with no problem.
But found problem with:

Code: Select all

if &#40;op_local_var&#40;11&#41; != 0 == 0&#41; then

or

Code: Select all

if &#40;op_global_var&#40;6&#41; != 0 == 0&#41; then

in decompiled file DCVic.int
What does this mind: (a != 0 == 0)

Red · Post by **Red** » Wed Feb 05, 2003 11:42 pm

You mean what does this "mean"?

Sometimes the script actually does that... Check the precedence of the operatros to be sure but suppose a is true (ie: 1).

true != false == false becomes true == false becomes false.

For false:

false != false == false becomes false == false becomes true.

So effectifly it's just a "not". Now the reason something like this might come up is because the original compiler might not optimize anything in the original code. Suppose in the original script, the script wrote something along the lines

(GVAR_WHATEVER != GVAR_WHATEVER_SOMETHING_WAS_SET) == FALSE you might have endede up with such code, it would (kind of) make sense in the script, but look funky once compiled without optimization.

Jargo · Post by **Jargo** » Thu Feb 06, 2003 2:32 pm

THX for answer. I get it now :)
But it still is a problem when using Noid's compiler.
In ipp it work's fine.

Ah and sorry for bad english :?

Red · Post by **Red** » Fri Feb 07, 2003 2:38 am

I'm used to bad english. I try my best to understand it but sometimes it's a bit confusing... English isn't my first language either...

I didn't try the compiler yet so I don't know.

Per · Post by **Per** » Fri Feb 07, 2003 6:38 pm

Hiya, can I pop in? :) Great work on the (de)compiler, and I can run it on my computer, too (the old one never did even after I got the database stuff several times over).

My gripe with the new compiler if I have one is not technical but graphical (and not just because I always preferred TurboPascal to C), the ssl output files look, well, a little cluttered compared to ipp, and the indention could be clearer as well. Also each script seems to have a pointless "checkPartyMembersNearDoor" procedure tagged onto it (the old ones often have ChooseFromList and TimeOfDay at the top but not that other one). Some scripts are almost 150% the size of their ipp counterparts.

But anyway, does this mean we're getting closer to my dream of a playermade patch for Fallout 2 along the lines of the Baldurdash fixpack for Baldur's Gate 2...? A totally commensurable compiler and the mod enabler should be all it takes really. Good ending for Gecko, here we come.

/Per

Red · Post by **Red** » Fri Feb 07, 2003 7:20 pm

Hey Per! :)

For the idents you can look at the ruby code and change it to your liking.
It's on line 27 in fact for easy access...

This in fact also applies to the function names as well if you feel like it, you could convert it to "ipp compatible format".

To that effect I wonder if we add such options wether we should post it for Noid to merge with his own code...

I have no idea about the "extra near door function" though. Maybe they indded all have it but for some reason dec ingored it? I just don't know (and don't know enough about the code to figure it out yet either).

Jargo · Post by **Jargo** » Fri Feb 07, 2003 8:51 pm

Yes, all scripts have checkPartyMembersNearDoor procedure.
IPP is always adding it when compiling the script so no need to write enything.

Red · Post by **Red** » Sat Feb 08, 2003 12:15 am

Hmm, but is it really needed though? Chances are it isn't - at least not always (why it's there is probably simply because of an include someone added to the main scripts which slaps that code wether you need it or not)... I like to have to option to stick whatever I want there, and from what I gather IPP won't. Unless of course removing it legitimitely breaks it, but I doubt that.

noid · Post by **noid** » Sun Feb 09, 2003 2:04 am

[quote="Jargo"]But found problem with:

[code]if (op_local_var(11) != 0 == 0) then[/code]

or

[code]if (op_global_var(6) != 0 == 0) then[/code]

in decompiled file DCVic.int

What does this mind: [i](a != 0 == 0) [/i][/quote]

!= and == have the same precedence, so the decompiler doesn't put in the parenthesis. As Red stated, these should have been decompiled as:

((op_global_var(6) != 0) == 0)

(Note the extra parenthesis).

I will fix this and the "\r\n" end of line bug in the next version.

Does anyone else have any bugs / enhancements they'd like implemented?

noid · Post by **noid** » Sun Feb 09, 2003 2:13 am

[quote="Red"]To that effect I was wondering wether that import/export stuff was really supported in the normal compiler

Here's my extraction line:

[code]E:\games\Fallout2_extracted_reference\data\scripts>for %a in (*.int) do @D:\apps\ruby\bin\ruby \games\falloutdec\decompile %a[/code][/quote]

import/export was supported in the original interplay compiler. You can see it in several of the scripts (e.g. broken1.ssl and hcliz.ssl).

The keyword "critical" does not seem to be supported by the fallout scripting engine, though my compiler does support it. See the KA compiler docs for info on critical.

For extracting multiple INT files at once, you can the wildcards "*" and "?".

e.g. ruby decompile *.int