Bug: The max loop limit can no longer be avoided serverside with a sleep.

[fowlplay4]

Levels are instances of TServerLevel objects.

Level files are parsed/processed and loaded into memory as TServerLevel objects.

player.level refers to the TServerLevel object the player is currently in.

[Devil_Lord2]

Originally Posted by fowlplay4

Levels are instances of TServerLevel objects.

Level files are parsed/processed and loaded into memory as TServerLevel objects.

player.level refers to the TServerLevel object the player is currently in.

D: So why is .name added to it?
Does it make a difference for levels?

[Skyld]

Originally Posted by Devil_Lord2

D: So why is .name added to it?
Does it make a difference for levels?

Well, player.level is an object which represents the level, so player.level.name gets the name attribute of the level object. The name attribute is already a string, so it does not result in the object being coerced (the example I posted above shows why relying on object-to-string coercion is a really bad idea).

[ffcmike]

Originally Posted by Devil_Lord2

D: So why is .name added to it?
Does it make a difference for levels?

Perhaps a good example would be the 'player' object. Within your script you're using player.account, 'player' being an object which can have variables written to and functions invoked on it, '.account' being a string/text value. If you can recognise that it is correct to use player.account instead of just 'player', you should also recognise it as correct to use level.name instead of just 'level'.