if (playervip)
 

Add that, if (playertrial) exist, i think playervip should exist.

I want to make a little world on adiarde for VIPs only and don't want them to put on tag for that

ummm... better yet... how about if (subscription=index)?

correct me if I'm wrong, but isn't this forum for future improvements??

Ok, so what do you call these requests? :confused:

oh, I don't consider economic devides as an improvement, but thats just me, I guess.

It is an addition to the scripting language, therefore it would be an improvement.

Ya like:

0 = Trial
1 = Classic Only
2 = VIP
3 = Gold
4 = VIP + Gold

the variable idea sounds interesting, that way it could be possible to give classic or gold players different features aswell

I probably wouldn't use it, but the variable idea would make a lot more sense.

Zokemon said
0 = Trial
1 = Classic Only
2 = VIP
3 = Gold
4 = VIP + Gold

The 4 there would be insignificant since you could do 2&3. Although if there was ever another subscription plan created, you could more easily go up a number rather than having to make a predefined flag for each one.

the numbers would have to be like this:

1 - Trial
2 - Classic
4 - Gold
8 - VIP

bitflags, see showstats, enablefeatures.

So no two numbers added could be equal to another bitflag.

e.g, 1+2 = 3, 1+2+4 = 7, etc.

why would they HAVE to be like that?
And whats up with bitflags?

Put it this way:

If you want all players with Gold or VIP, and not, you could do:

NPC Code:

---

  bitflag = 4+8;

  if (accounttype == bitflag){

    message YOUR IN!;

  }

---

Whereas elsewise, you'd have to say:

NPC Code:

---

  bitflag = {2,3};

  if (accounttype in bitflag){

    message Your In!;

  }

---

The first method is more effiecent with the engine, whereas the second one is still easily done.

Most people would put:

NPC Code:

---

if (accounttype == 2 || accounttype == 3){

  message Your In!;

}

---

And... That way looks ugly. To prevent ugliness, they use bitflags.

Personally, I don't mind either way.

How about variables for playergoldtime and playerviptime, and a builtin function to get years and months and days and hourse and minutes and seconds out of really big amounts of seconds?

lol builtin?

minutes = seconds / 60
hours = minutes / 60
days = hours / 24
years = days / 365.25
weeks = years * 52
months = years * 12

omg, so hard.. need... builtin...command.

How bout an accurate time variable, and timestamping on RC messages while we are at adding the "builtin" seconds command?