Apiai on 25/7/2013 at 16:33
Hi guys,
since NewDark, before playing an old FM, I systematicaly rebuild it in 32bits.
Then I save the .mis file into miss17_32bits.mis
After I launch a batch file (swap_and_play.bat) which is swapping the two files like this :
- Rename the original mission file (16bits) into miss17_original.mis
- Rename the 32bits mission into miss17.mis
- Launch Thief
What i wanna do is integrate this batch file to a new DromEd menu.
I've created this one in menus.cfg :
menu_playtest &Mission Swap and Play:run Mission_swap_play.cmd
I've also created Mission_swap_play.cmd into Dromed directory, here's the content :
cd "C:\Dark Project 2\"
swap_and_play.bat
In windows, when I click on Mission_swap_play.cmd, everything is working.
In DromEd, no effect at all !
Am I missing something ?
(I think DromEd is dealing with .cmd files that are not real .cmd DOS batch file.
DromEd cannot translate real DOS command, only internal commands)
ps : Thief and DromEd are in differents directories.
R Soul on 25/7/2013 at 17:37
Quote Posted by Apiai
(I think DromEd is dealing with .cmd files that are not real .cmd DOS batch file.
DromEd cannot translate real DOS command, only internal commands)
This.
Dromed doesn't need the files to have the .cmd extension. They can have any extension, or none at all.
I don't see the need to keep the original mis file on your hard disk because it will be inside the FM's zip file. I think you should have a dromed cmd file that relights the mission and then runs the save_mission command. A Save As box will come up and you can select the original mis. Dromed will automatically make a backup.mis file for you if you need it, but I doubt you will.
Apiai on 25/7/2013 at 20:09
Well sometimes I have to switch to the 16bits mission when i'm stuck to be sure there is no bug related to NewDark. It happens that an extinguished torch don't obscure a room in 32bits version.
Nameless Voice on 27/7/2013 at 14:35
I regret using the .cmd extension for the commands in the DromEd Toolkit, it implies that they are Windows command files, which they are not. I should have picked some obscure new extension instead.
