Sorry, been busy lately... :p
Try putting a Trace() as the very first statement in run(), where it can't possibly miss it. If that doesn't give you something, it must be unable to write to the file properly for some reason.
I think I got it to work once, but... It gave me a lot of numbers that made no sense....
Edit: By the way, do you happen to know how to correctly work the functions "Link->Warp" and "Link->PitWarp"? Every time I use the latter, nothing really happens when it's called. Take a look at this excerpt of code from my Harp of Ages script:
If he has item x, this code will warp Link to a certain dmap (The "WrpScrn2" is always the same screen number Link is on), but for some reason, it never really does anything... See, I put all the code for all 3 tunes from OoA into this one script, for ease, but... Could that be the problem? Or is it, for some reason, checking for ALL the maps there?Code:else if (Link->Item[ID2]) { if (CurMap == 2 || CurMap == 4 || CurMap == 6 || CurMap == 8 || CurMap == 10) { Time = 0; Link->PitWarp(WrpDMap2, WrpScrn2); Quit(); } else if (CurMap == 1 || CurMap == 3 || CurMap == 5 || CurMap == 7 || CurMap == 9) { Time = 1; } }
How do you mean? They just weren't what you expected, or they literally couldn't have been generated by the script?
Hm. They should work just about the same way. If one works and the other doesn't, I'm inclined to think it's a bug.Edit: By the way, do you happen to know how to correctly work the functions "Link->Warp" and "Link->PitWarp"? Every time I use the latter, nothing really happens when it's called.
I've been meaning to start looking at the compiler stuff. I suppose I'll look into it if DD doesn't beat me to it.
1: They were a lot of numbers that were usually things like "0.000000001" and then all these seemingly-random numbers placed to tell what that stupid number's value was....
2: Yeah, the code for the Tune of Currents part of the script is basically the same as the code for the Tune of Ages part. Neither work. Only the "Tune of Echoes" part works, because it changes a certain combo (And I also have to MOVE the FFC at its location because of the bug I was told about with FFCs. )... Or, maybe I'm using the wrong items.....
*sigh* Okay, the stuff is still in the allegro.log file...
Decrypting...okay.
Opening...okay.
Reading Header...okay.
Reading Rules...okay.
Reading Strings...okay.
Reading Doors...okay.
Reading DMaps...okay.
Reading Misc. Data...okay.
Reading Misc. Colors...okay.
Reading Game Icons...okay.
Reading Items...okay.
Reading Weapons...okay.
Reading Maps...okay.
Reading Combos...okay.
Reading Combo Aliases...okay.
Reading Color Data...okay.
Reading Tiles...okay.
Reading MIDIs...okay.
Reading Cheat Codes...okay.
Reading Init. Data...okay.
Reading Custom Guy Data...okay.
Reading Custom Link Sprite Data...okay.
Reading Custom Subscreen Data...okay.
Reading FF Script Data...okay.
Reading SFX Data...okay.
Done.
128 83 0
128 83
128 83 0
128 83
128 83 0
128 83
128 83 0
128 83
128 83 0
128 83
128 83 0
128 83
128 83 0
128 83
128 83 0
128 84
128 84 0
128 84
128 84 0
128 84
128 84 0
128 84
128 84 0
128 84
128 84 0
128 84
128 84 0
128 84
128 84 0
128 84
128 84 0
128 84
128 84 0
128 85
128 85 0
128 85
128 85 0
128 85
128 85 0
128 85
128 85 0
128 85
128 85 0
128 85
128 85 0
128 85
128 85 0
128 86
128 86 0
128 86
128 86 0
128 86
128 86 0
128 86
128 86 0
128 86
128 86 0
128 87
128 87 0
128 87
128 87 0
128 87
128 87 0
128 87
128 87 0
128 88
128 88 0
128 88
128 88 0
128 88
128 88 0
128 88
128 88 0
128 89
128 89 0
128 89
128 89 0
128 89
128 89 0
128 89
128 89 0
128 90
128 90 0
128 90
128 90 0
128 90
128 90 0
128 91
128 91 0
128 91
128 91 0
128 91
128 91 0
128 91
128 91 0
128 92
128 92 0
It's basically a lot of that with increasing numbers...
Edit: Which eventually start becoming random...
Ah, that? That's not from Trace(). It's just some debugging stuff in the current build.
Trace() will only print one number on each line, and it will always be to four decimal places.
Just to be sure, you have tried putting a call to Trace() somewhere where it can't possibly be missed (like as the first statement in run()) to be absolutely certain whether it works, right?Well then, Trace() is broken, since it's not giving me ANYTHING.
The thing is, I haven't heard of any problems with it before, and I haven't seen any myself. If you're the only one it's not working for, well, I'm having trouble thinking of a reason that might be.
Isn't that the one that works with Link->Warp() but not Link->PitWarp()?Oh, what about my other problem? I tried changing the item required to use the "Tune of Currents" effect, but the effect STILL doesn't happen.
If that's the one, I really think it must just be a bug, or else the function simply hasn't been implemented yet.
There are currently 1 users browsing this thread. (0 members and 1 guests)