(this file is an abstract of the 'readme.txt' in the DEACC11.ZIP)


DEACC.EXE v1.1 by Luc Cluitmans

DEACC11.ZIP contains DEACC.EXE, my hexen script decompiler.


*About Decompilation*

DEACC tries to decompile hexen scripts into ACS files. It can
read both raw behavior lump files (ACC output) and behavior lumps
from a wad file.

Some info that was in the original ACS source for the script is
not available in the compiled form of the script: DEACC will not
be able to recover this information. DEACC is not able to:
- recover the original variable names
- recover any comments
- recover the exact source for constructs that can be written
 in several ways. DEACC tries to generate 'break' and
 'continue' statements only if no other construct can be found.

I tested DEACC on all scripts of the original Hexen.Wad. The output
it produces for each original hexen script was compilable by ACC.
When ACC compiled the ACS files produced by DEACC, the resulting
behavior lump was exactly equal to the original for all maps (the bug
for MAP22 and MAP39 in deacc 1.0 has been fixed)!


*Acknowledgements*

Thanks to:
- Raven Software and id Software for creating Hexen
- Ben Morris for the Hexen Specs
- John B. Williston for getting me on the track of
 hexen decompilation


*History*

21 November 1995
   Released version 1.0 of DEACC

05 December 1995
   Version 1.1:
   - fixed the string variable problem (DEACC 1.0 did not correctly
     decompile scripts containing string variables, like MAP22 and
     MAP39 in the original hexen wad).
   - fixed a few small and barely noticable bugs.


*Feedback*

If you have comments or bug reports: send me  a message via email:
  [email protected]


   Luc.

You are viewing proxied material from liquiddoom.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.