14 replies to this topic

[BitZero]

-2.5 Build 842-
Question Number One: In scripts, is it possible to activate warps or make a warp happen? If so, how?

Question Number Two: When compiling scripts, is it supposed to make your quest file ridiciously large?

[Plissken]

Disclaimer:

DO NOT USE 842 TO COMPILE SCRIPTS. There is a horrid bug that deletes all of your map data every once in awhile you compile. Just download 846, it's fixed in there.

To warp use this:
Link->Warp(Dmap, Screen);
Of course Dmap and Screen need to be replaced by the values of those things. It uses warp return A on the screen he warps to. Or if you want to Pitwarp (make Link warp to a new screen while not changing his position on the screen use this:

Link->PitWarp(Dmap, Screen);

Also, check out the zscript.txt file in your build folder to find functions you can use such as these.

[BitZero]

DO NOT USE 842 TO COMPILE SCRIPTS. There is a horrid bug that deletes all of your map data every once in awhile you compile. Just download 846, it's fixed in there.

I can't really upgrade. It gives me an error message and then crashes.
But, thanks for the answer to Number 1.

[Plissken]

If the error message is about not finding alleg42.dll then find the file in your folder kinda similar to that name with a little stuff added in the name and rename it to alleg42.dll.

You NEED 846 if you're scripting. You WILL lose your progress a bunch of times and you most likely will lose your quest if you aren't careful with backups. I hate 842 so much.

Edited by Plissken, 06 August 2008 - 12:02 AM.

[BitZero]

If the error message is about not finding alleg42.dll then find the file in your folder kinda similar to that name with a little stuff added in the name and rename it to alleg42.dll.

You NEED 846 if you're scripting. You WILL lose your progress a bunch of times and you most likely will lose your quest if you aren't careful with backups. I hate 842 so much.

It finds it, but it has something to do with an entry point...which, I am totally clueless to what to do for that.

[Plissken]

Tell me exactly what it's saying, also are you using ZCLauncher to run ZQ?

[BitZero]

Tell me exactly what it's saying, also are you using ZCLauncher to run ZQ?

I'm not using ZCLauncher. But it still gives the same message.

Here's the message:
The procedure entry point file_size_ex_password could not be located in the dynamic link library alleg42.dll.

[Plissken]

Hmmmm, I have never heard of that before. Try redownloading the build see if that helps. If not I'd highly suggest using the build below 842. Do not use 842.

[BitZero]

Hmmmm, I have never heard of that before. Try redownloading the build see if that helps. If not I'd highly suggest using the build below 842. Do not use 842.

That didn't help, so I guess I'm going to downgrade...
Would it matter if I'm on Vista or not?

Edit: Okay, this is really bad...it displays the same error message for the one below...Should I continue lower?

Edited by SerpitaX, 06 August 2008 - 12:19 AM.

[Plissken]

Doesn't for me, make sure you are running as an admin account though.

[BitZero]

Doesn't for me, make sure you are running as an admin account though.

Running as Admin does not help...
Plus no other one works. Which, I'm guessing is bad.

[Plissken]

A lot of people have reported running as an admin is the only way (except for ZCLauncher) they can get ZC to work on their vista so...yeah...it might help.

Edited by Plissken, 06 August 2008 - 12:28 AM.

[BitZero]

A lot of people have reported running as an admin is the only way (except for ZCLauncher) they can get ZC to work on their vista so...yeah...it might help.

Yes, well I tried...but it continues giving me the message.
Edit: Well, I can't open Zelda Classic, nor Romview...as it says the same message.

Edited by SerpitaX, 06 August 2008 - 12:32 AM.

[Plissken]

Eh, I read it wrong. Sorry, I'm tired read it as if you were saying, "No way would that work you serious?" Sorta way.

Anyways, yeah I suggest you downgrade, then try the newest build whenever it comes out.

[BitZero]

Okay, finally worked after getting it down to Build 816.
Hopefully that doesn't hurt my quest...
And you were right, scripting does kill the quest! But I back-up every day.
That problem doesn't persist with this build, does it?

Edited by SerpitaX, 06 August 2008 - 12:37 AM.