Threaded Mode | Linear Mode

Khaos · (12-06-2013)

Now this is more a tutorial/display for something I saw in BugTracker for a new trigger implementation. Basically, the user wanted control over regions and stopping players from leaving while on a quest.

What is shown below is one way of doing this. You can also check for character <src.p> as well and stop someone from leaving. I have XuN test this code using a <src.p> check.

During the tests we concluded that the player couldn't leave the area by gate, recall, walking, teleporting, or any custom items (telepads), etc.

What does this mean? Simple. Regions are checked before anything happens with a character moving from one. Same with entering one. So really the @WorldTeleport control is not needed.

Example code block:

Code:

[events e_region_block]

on=@RegionLeave

if <argo.defname> == r_painted_caves

 if !(<src.tag0.quest.0001.complete>)

  src.msg You cannot leave this place until your quest is done.

  return 1

 endif

endif

Anarch Cassius · 12-06-2013 08:44 AM

Holy crap, that's a useful little concept. So many event and quest ideas Smile

Extreme · 12-06-2013 09:12 AM

No need of ON= before @RegionLeave ?
Cool Big Grin

Khaos · 12-06-2013 09:23 AM

Sorry guys. Forgot to add in <ARGO.DEFNAME> Updated now.

Khaos · 12-06-2013 12:15 PM

Fixed the on= extreme. Didn't even think about it since it was supposed to be an example.

Threaded Mode \| Linear Mode @RegionLeave Example for Bugtracker Request
Author	Message