The Dink Network

I'm seeing a very weird issue. When Dink hits a sprite, sometimes it also triggers the hit on a sprite that's in a completely different location.

Here's a screenshot:



I updated my scripts to say stuff when Dink hits them (barrels say "Wah?", mushrooms say "Woo"). Dink just hit a sprite or two next to where he's at with his fancy light sword, but it also triggered a hit on a mushroom hidden behind a rock at the top.

And the weird thing is, this doesn't happen all of the time, just sometimes.

Any ideas?

I doubt anyone else has seen this, but I thought I'd ask just in case.

Does it happen with all the D-Mods, or just with one?

Dunno at all, but to me it looks a lot like a screw-up with "&temphold" stuff or something. Something like this usually happens to me when I try to make a "&temphold" say something, but there isn't a sprite named that in the screen. Instead of crashing, it randomly searches for the next best sprite to deliver the say command. It looks a lot like that same bug here, but if it's not, I really have no idea. If it has nothing to do with that, it's probably a problem that goes beyond your usual Dink scripting.

Sorry if none of that made any sense. The D-Mod creation part of my brain isn't very good at 4am.

&temphold is a very good thought, but the sprites are saying things directly, using &current_sprite.

Some additional investigation identified that the issue actually isn't when hitting the crate, but, rather the sack of pig feed sitting there. Which doesn't have a script attached at this time (it does earlier, but it is killed using kill_this_task).

That leads me to believe that the script of the pig feed isn't actually 'killed', but is somehow pointing to the script of the hidden mushroom.

Wild stuff.

That means I think I can fix it...

Edit: Yep, fixed. Yay!

Edit: Or not. Grr.

Edit: Fixed again. I had some sprites that were nohit/nodraw that I was kill_this_task their scripts on, which it didn't take too kindly to. Changed it to just kill those sprites out-right (sp_active(&current_sprite, 0)), and that seems to have fixed it.

I'll never cease to be impressed by the weird ways this game behaves in ways you don't want.

Thanks, Seth!

Nice banana.

For science, maybe try killing the script with

sp_script(&current_sprite, "");

instead. See if that's cleaner.