Numplayers: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
Returns the number of non-bot players in the game. | |||
In singleplayer, it is set to 1. | |||
The non-bot player IDs range from zero to '''numplayers''' minus 1. Meaning bots will always hold the highest IDs. | |||
In | |||
In the original Duke Nukem 3D, once a player quit, '''numplayers''' would decrease permanently, meaning it was impossible for a new player to join mid-game. | |||
It can also be used for when making a loop through all non-players. Example: | |||
appendevent EVENT_WORLD | |||
for My_Player range numplayers | |||
{ | |||
[...] | |||
} | |||
endevent | |||
[[ | While [[MULTIMODE]] stores the total of player in the game, '''numplayers''' stores only non-bot players. | ||
[[Category:Constantly updated gamevars]] | [[Category:Constantly updated gamevars]] |
Revision as of 05:22, 19 February 2020
Returns the number of non-bot players in the game.
In singleplayer, it is set to 1.
The non-bot player IDs range from zero to numplayers minus 1. Meaning bots will always hold the highest IDs.
In the original Duke Nukem 3D, once a player quit, numplayers would decrease permanently, meaning it was impossible for a new player to join mid-game.
It can also be used for when making a loop through all non-players. Example:
appendevent EVENT_WORLD for My_Player range numplayers { [...] } endevent
While MULTIMODE stores the total of player in the game, numplayers stores only non-bot players.