[b]Content
[/b][html]
You're in the right location, here's a cookie!<br/>

<!-- content separator -->

You are not allowed to view this from here!!<br />
[/html]


[b]<< MD-PHP Script >>[/b]
[code]
(locations 1_0x0_1)
if
(uv('location') == '1_0x0_1') { //checks the location the player is at and matches it against where they should be
echo @content['0']; //if they're in the correct place, it displays the first content te xt
}
else {
echo @content['1']; //if they're in a different place, it displays the second content te xt
}
[/code]



You can modify this with keys and such to ban people from the quest if they try and use alternate means

Edited September 14, 201015 yr by Grido(polis)
adding html tag bbcode into it because i have OCD

A note: due to the locations restriction "[b](locations 1_0x0_1)[/b]", the player has to be at that scene in order to access the script.
Checking that the player is actually there, is already provided by MDS
However, it does make sense to use it if you have multiple locations allowed (but whether or not it is good to use that feature is a different matter entirely)

no it doesnt

talk to me on yim

[quote name='Grido(polis)' timestamp='1284497697' post='68420']
no it doesnt

talk to me on yim
[/quote]

Actually the reason I requested this function (a long time ago) was so that you could make a single script which functions differently at different locations based on the players current location. This is much cleaner than having to make multiple scripts at each site and bug check each and every one.

It also allows quests where multiple people are working in unison to satisfy a condition for example "have someone at every fountain in MD at the same time". Without a location function that isn't possible.

Cheers,

Cutler

So does this works as Grido says it works or as Rendril says it works? Is (locations 1_0x0_1) enough to restrict it only to GoE or do I have to use the whole thing even though script will be runable only in one location?

The location restriction that Rendril states, restricts the compiling of code to be anywhere other than the listed locations. People could potentially still access it from other locations though.

 

The function listed in the initial post restricts players from trying to access the clickable from anywhere else, meaning the player has to be in the location you want them to be in.

I don't understand the difference.... but yes I don't want unauthorized remote access, thank you.

I don't understand the difference.... but yes I don't want unauthorized remote access, thank you.

Yeah, The location setting is broken, and doesnt work as intended, Has been so for a while and I havent had time to fix it since rendril stopped coding.