onPlayertouchsLink()

[DustyPorViva]

onPlayertouchsLink(id) {}

A function that is called when a player touches a link, and is processed before the player is warped out of the level. id = the id of the link itself, so we can access the info like the destination level and such. Why? To make links a bit more workable with custom systems perhaps, or to maybe add screen effects when the player exits a level, for example. And maybe the ability to cancel the link's effect?

[fowlplay4]

Would like this.

[DustyPorViva]

I'd actually like a lot more ability to work with the default level data. Right now, for example, there is no way to disable default signs and no way to access the data clientside. That means in order to make a custom sign system you'd have to script the actual signs themselves(and why change a function many are familiar with?). I want to be able to make custom systems that work backwards compatible with the default systems for developers, but Graal doesn't make it easy.

[Tigairius]

Great suggestion, I agree. Would be nice to also disable default linking somehow.

[Chompy]

I totally agree that this suggestion would be an useful addition, always wanted an easier way to trigger screen effects on exiting a level

[Loriel]

Originally Posted by Tigairius

Great suggestion, I agree. Would be nice to also disable default linking somehow.

return false from onPlayerTouchesLink(...) to prevent the player from being warped by the engine?

[DustyPorViva]

Originally Posted by Tigairius

Great suggestion, I agree. Would be nice to also disable default linking somehow.

I like Loriel's idea, though I wouldn't object to serveroptions to disable default functions like links/signs/baddies and such when a server has no intention of using any of them.

[Crono]

Nice idea, probably won't be implemented for another 3+ years.

[coreys]

Originally Posted by Loriel

return false from onPlayerTouchesLink(...) to prevent the player from being warped by the engine?

That would work great if Graal events didn't work the way they do. You could have multiple instances of onPlayerTouchesLink being called at the same time that could potentially return different values.

[DustyPorViva]

Originally Posted by coreys

That would work great if Graal events didn't work the way they do. You could have multiple instances of onPlayerTouchesLink being called at the same time that could potentially return different values.

Well Stefan could probably only let a single NPC use it, like Control-NPC or something.

[Loriel]

Originally Posted by coreys

That would work great if Graal events didn't work the way they do. You could have multiple instances of onPlayerTouchesLink being called at the same time that could potentially return different values.

I was assuming it would be an event delivered to all weapons, clientside, and it defaulted to true.

[coreys]

Originally Posted by DustyPorViva

Well Stefan could probably only let a single NPC use it, like Control-NPC or something.

Would be better for him to just add to it to enablefeatures or something around those lines.