590 replies to this topic

[Cukeman]

Noticed two things today, might be bugs, might not.
1. When you slash a fire trail enemy and it recoils it drops a bunch of extra fire trails - about 15 in a space of about 4 combos.
2. When Link is charging his extended sword and strafes left to a new screen a sword graphic appears on the left side of the new screen while it is scrolling.

If it's not a problem, it's not a problem, just making sure.

Edited by Cukeman, 20 July 2012 - 12:37 AM.

[Saffith]

I can't quite decide about something. Currently, the "Save Point->Continue Here" screen flag doesn't affect Game->Save(). Should it?

I'm also adding Game->ShowSaveScreen() and Game->ShowSaveQuitScreen(). Same question with those.

[Cukeman]

I forget, someone mentioned moldorms going off the screen before right?

[Jared]

I forget, someone mentioned moldorms going off the screen before right?

Yeah, that was me. That was many months ago.

[Saffith]

I can't quite decide about something. Currently, the "Save Point->Continue Here" screen flag doesn't affect Game->Save(). Should it?

I'm also adding Game->ShowSaveScreen() and Game->ShowSaveQuitScreen(). Same question with those.

I still want answers here, even if they're arbitrary.
I guess making the functions take arguments would be an option, as well.

[LinktheMaster]

I can't quite decide about something. Currently, the "Save Point->Continue Here" screen flag doesn't affect Game->Save(). Should it?

If I'm understanding correctly, I would think it should. After all, if for some reason a quest maker has a save point on a screen as well as a scripted save, then they can always toggle "Save Point -> Continue Here" via scripting temporarily while they save.

[Saffith]

Nah, can't do that. Screen flags are read-only.

I just remembered, though: you can set Game->ContinueScreen/DMap, which does the same thing, so that should suffice.

[LinktheMaster]

Forgot about that. Sometimes I get mixed up as far as which stuff you can and can't set.

[Moosh]

So I know there's been a feature freeze for like 200 or some builds now and I by no means want to delay 2.5 further, but I just spent an entire day trying to figure out why my script wasn't working when it turned out it was and I had just drawn the whole screen on layer 1 so I was wondering if you guys could make some kind of warning for when a screen has stuff drawn on its layers, but not on layer 0. Would this be possible?

[Xenix]

I have noticed this, if I use the sword while the screen warp triggers, link's sprite will be offset from his real position.

[Russ]

Well, I was testing Evan's quest, and I ran into the oddest bug. I shot my hookshot, and it just went offscreen... and kept going... and going. It might have been because of Link's position next to the block all combos, I don't know. Here's a video of the weird bug:

[HylianGlaceon]

Something else I've noticed. Remember that Spin Attack Whistle Whirlwind glitch I reported a page or too ago? I was messing around and found out it'll do it with the Hammer too if you have the Quake Hammer Scroll, at least in RC3.

Has this been fixed in the newest version or just the Spin attack? I can't think of any other items it'll mess up tbh.

[Saffith]

Yeah, that got fixed along with the other.

[Eurysilas]

Serious bug in Hero of Dreams QST-



See that closed door? I'm actually behind it. It is supposed to open automatically from that side ( as seen on this LP http://youtu.be/hQ3WNSgiSeU ). It does not, forcing a reset to escape that particular dungeon.

Edited by Eurysilas, 27 July 2012 - 09:30 PM.

[LinktheMaster]

Hmm... is there any way to disable the mouse pausing ZC with scripting? I know there's the ZC option, but if a quest uses the mouse, that option is just counterproductive.