I’m using Adventuron to program adventures, then convert to DAAD format so they can run on retro systems..
however, when I try to lad them on the Amstrad CPC, it doesn’t seem to load beyond the first file and the screen is always black. Is there a list of colours for each format, so i can get the colours right for each format please?
I’ve got a condition in Adventuron which changes a few of the room descriptions depending on certain conditions but it doesn’t work in DAAD. What would be the equivilant of it please?
This is the code in question
strings {
farm_description : dynamic_string {( is_raining ? “You are at what you believe to be a farm. You can see a door in a building plus what looks like a barn.” : “Here in daylight, you can tell you are not on a farm after all. You are outside an ordinary stone wall house, with the barn nearby.” )}
and when i try to make Amiga and Atari ST versions, it says I’m missing MALUVA and I can’t find the file anywhere and searching on Google doesn’t give results.
Probably worth giving all the manuals and documentation a read at DAAD Ready, re. Maluva etc.
Re. different descriptions. I would leave the main description section blank and then use condacts to trigger the text (e.g. AT for the location number and then whatever flag you are using to check the different conditions) and drop that into the process that runs directly after the location description is called. (I think it’s process 3 in the default template in DAAD… been a very long time since I’ve had chance to do any coding).
e.g.
> _ _ AT farm ZERO daylight MESSAGE “You are at what you believe to be a farm. You can see a door in a building plus what looks like a barn.”
> _ _ AT farm NOTZERO daylight MESSAGE “Here in daylight, you can tell you are not on a farm after all. You are outside an ordinary stone wall house, with the barn nearby.”
Thanks - sadly it doesn’t tell me where to get the correct Maluva files for comiling on the Amiga and Atari ST.. This is the text that I get when trying to compile on the Amiga and Atari ST.
Thanks - the main problem is getting onto it.. Sadly Telegram overrides Dark Mode and I can’t see anything without it. Some of the DAAD Ready documentation isn’t very understandable and while I have the EAAD program and can load my source code into it, I wouldn’t know where to go to to make the corrections.
I’m not a DAAD developer/user, but from what I read Amiga and Atari ST targets don’t need Maluva, because they provide its features natively.
That means that instead of commands starting with letter X, like XPICTURE, XMESSAGE you can use the analogous commands without the preceeding X, like PICTURE, or MESSAGE.
These X commands are used to load external resources.
From what I read you should use DRC compiler instead of DC to make the X commands replaced with native counterparts, while keeping support for other targets. You can find more information on Utodev GitHub page - MALUVA Wiki.
When I looked (using Notepad++) into the TEST.DSF file which was generated by Adventuron’s DAAD export for the sample game “Cave of Magic”, the file started with the 3 lines:
#ifndef "nomaluva"
#extern "MALUVA"
#endif
If you delete these lines, then the DAAD compiler won’t complain about Maluva anymore.
Further into the compilation process, it will throw this error:
“XSAVE condact has been deprecated.”
I looked for XSAVE in the file and found the line XSAVE 0. Since XSAVE is deprecated, and only SAVE is mentioned in the current DAAD-Ready manuals, I just experimentally changed it to SAVE 0 in order to get the game to compile. (In accordance with what Robert said above.)
Honestly, since I am not really knowledgeable about DAAD, I don’t know if that’s the right solution, but it sounds sensible enough , and it did actually let me continue with the compilation.
Next error:
“XLOAD condact has been deprecated.”
So I also changed XLOAD 0 to LOAD 0, and then the process went through, so that the game could be played in the ZEsarUX emulator. (And saving and loading within the game seemed to work as well.)
Apparently, Adventuron’s export function targets an older version of DAAD-Ready, so you could either try what I did above, or you could try a previous release of DAAD-Ready from here and check whether that is a better match for Adventuron’s export.
Thanks - I’ve got the latest version of DAAD Ready so will give it a try later! Next problem is to find out why the generated Amstrad CPC files don’t work (all I get is a blank screen and no traces of loading) and what the right colour codes for each machine are..
, and it did actually let me continue with the compilation.