Castle Paradox

Tsunamidog · Posted: Tue Jun 21, 2005 2:13 pm Post subject: ANOTHER PROBLEM

I've heard that this is a bug in Hspeak and I should report it, cause its rare or somethin', but I want to know if I can fix it or what I can do. Every time I try to compile a script, it says "No Data To Compile". What can I do?
_________________
The Following Statement is True.

The Above Statement Is False

Blaze18 · Posted: Tue Jun 21, 2005 3:20 pm Post subject:

It does the same thing to me. It almost drove me insane. I tried compiling it over and over. Luckily a friend of mine is good at making scripts, and he compiled them on his computer for me (even though you don't have to be an expert to compile).

It gets annoying after too long. I even downloaded HSSED and all of the other files. Yet it didn't work. This problem gets tireing. I just hope it can get fixed soon. I will go back to work on my Blaze game now.

~Blaze is busy. Do NOT disturb.
_________________
Once you go hell you never go back.

Current project: Blaze: Dark Legends

Mike Caron · Posted: Wed Jun 22, 2005 5:51 pm Post subject:

Could you possibly post a copy of a script that produces this error? Preferably, it should be the smallest script that makes the error. You don't need to include plotscr.hsd, but any other includes are needed. (don't forget to use [code] tags!)
_________________
I stand corrected. No rivers ran blood today. At least, none that were caused by us.

Final Fantasy Q
OHR Developer BLOG
Official OHRRPGCE Wiki and FAQ

Tsunamidog · Posted: Wed Jun 22, 2005 6:48 pm Post subject:

It's all the scripts....every single one of them Sad...

_________________
The Following Statement is True.

The Above Statement Is False

TMC · Posted: Thu Jun 23, 2005 8:21 pm Post subject:

I think this might depnd on where the script and program is? What folder are they in the same one? Are you uing win XP? XP hates batch files and maybe hspeak too under certain circumstances.

What happens if you try to compile from the command line?

Raekuul · Posted: Fri Jun 24, 2005 4:01 am Post subject:

Okay... easy way to catch this (this is how I caught it).

1) Go to the "Properties" in the right-click menu for hspeak
2) Turn off "Close on exit"
3) If you've gotten it to compile before, compile with the same name as the compiled (back up the compiled first).
4) Otherwise, compile.

Noone's sure why it happens, and according to JP,