First of all thanks to thoose who have made it possible to play DM and CSB on PC, its great to enjoy thoose games again.
I have tried the editor that comes with Return To Chaos V0.32 on CSB, but after making the changes and save it "just" makes a TXT file and the changes dont seems to be there, have also tried just editing, that also dont do anything.
Then I thought maybe its just about about renaming the new file so it overwrites the original CSB, that just does that CSB is no longer availble in the start menu.
So either this editor dont work or I am missing something, can anyone help please?
Return To Chaos V0.32 editor
Forum rules
Please read the Forum rules and policies before posting.
Please read the Forum rules and policies before posting.
-
George Gilbert
- Dungeon Master
- Posts: 3022
- Joined: Mon Sep 25, 2000 11:04 am
- Location: London, England
- Contact:
Hi - you need to compile the text file to run it. Instructions for how to do this are in the file "editing.txt" that came with RTC. I've reproduced these below for your easy reference...
***************
Once you have a dungeon in the text format it can be compiled into an RTC module
by including a COMPILE instruction into the "config.txt" file of the main game.
This instruction takes a single parameter, the filename (including any
sub-directories) of your dungeon - for example:
COMPILE Modules\New\MyDungeon.txt
Remember that ALL FILES FOR USE WITH RTC ARE TAB-DELIMITED so the gap between
the "COMPILE" and the filename is a tab and not lots of spaces. Alternatively
you can specify the name of the dungeon as an additional command line parameter
when starting RTC - for example:
RTC.exe Modules\New\MyDungeon.txt
The value given on the command line will over-ride any given in the config file.
The next time you run the game the engine will then attempt to compile and run
your dungeon. After the introduction sequence a menu screen will appear giving
a summary of the compilation including the number of errors and warnings found
(see below) - a more detailed description of any problems is written to a log
file in the same directory as the text file (for the above example this would
be Modules\New\MyDungeon.log).
- Errors are normally a result of typos in the text file or the incorrect syntax
of a line. Examples of errors include mis-spelling an object or instruction
so that it can not be recognised by the interpreter or omitting a key property
from an item definition.
- Warnings are normally a result of inconsistencies in the dungeon layout.
Although they usually indicate something is wrong it may be that you intended
the dungeon to be this way and as a result the RTC engine will create a dungeon
exactly as you have specified it. Examples of warnings include teleporters which
point into walls, doors without doorframes or a staircase down on one level
without a corresponding staircase up on the next level.
Regardless of the number of errors or warnings, RTC will then display the dungeon
entrance and you are ready to enter and test your dungeon. The game will try and
cope with any errors that it finds, but you should remember that it is very likely
that your dungeon will not appear as expected and the game may abort at any point.
As such, a compiled version of your dungeon (e.g. Modules\New\MyDungeon.rtc)
will only be created if there are no errors.
After fully testing your dungeon, as the final step, remove the COMPILE instruction
from your config.txt file. When you next re-start the game your new dungeon will be
available for selection from the main start-up menu and is ready for distribution to
other players. As the compiled files can not be viewed or edited, to preserve the
mystery of your new dungeon, it is recomended that you only distribute the compiled
*.rtc file to others. Equally, it is vital that you do not delete your copy of the
text file as the only way to make modifications to the dungeon is to alter that file!
***************
Once you have a dungeon in the text format it can be compiled into an RTC module
by including a COMPILE instruction into the "config.txt" file of the main game.
This instruction takes a single parameter, the filename (including any
sub-directories) of your dungeon - for example:
COMPILE Modules\New\MyDungeon.txt
Remember that ALL FILES FOR USE WITH RTC ARE TAB-DELIMITED so the gap between
the "COMPILE" and the filename is a tab and not lots of spaces. Alternatively
you can specify the name of the dungeon as an additional command line parameter
when starting RTC - for example:
RTC.exe Modules\New\MyDungeon.txt
The value given on the command line will over-ride any given in the config file.
The next time you run the game the engine will then attempt to compile and run
your dungeon. After the introduction sequence a menu screen will appear giving
a summary of the compilation including the number of errors and warnings found
(see below) - a more detailed description of any problems is written to a log
file in the same directory as the text file (for the above example this would
be Modules\New\MyDungeon.log).
- Errors are normally a result of typos in the text file or the incorrect syntax
of a line. Examples of errors include mis-spelling an object or instruction
so that it can not be recognised by the interpreter or omitting a key property
from an item definition.
- Warnings are normally a result of inconsistencies in the dungeon layout.
Although they usually indicate something is wrong it may be that you intended
the dungeon to be this way and as a result the RTC engine will create a dungeon
exactly as you have specified it. Examples of warnings include teleporters which
point into walls, doors without doorframes or a staircase down on one level
without a corresponding staircase up on the next level.
Regardless of the number of errors or warnings, RTC will then display the dungeon
entrance and you are ready to enter and test your dungeon. The game will try and
cope with any errors that it finds, but you should remember that it is very likely
that your dungeon will not appear as expected and the game may abort at any point.
As such, a compiled version of your dungeon (e.g. Modules\New\MyDungeon.rtc)
will only be created if there are no errors.
After fully testing your dungeon, as the final step, remove the COMPILE instruction
from your config.txt file. When you next re-start the game your new dungeon will be
available for selection from the main start-up menu and is ready for distribution to
other players. As the compiled files can not be viewed or edited, to preserve the
mystery of your new dungeon, it is recomended that you only distribute the compiled
*.rtc file to others. Equally, it is vital that you do not delete your copy of the
text file as the only way to make modifications to the dungeon is to alter that file!
