Myconnectindex: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
It is of little actual use in con (despite the impressions of some mod authors who misunderstand dukes netplay). In singleplayer it will always be fixed at the first player index. In multiplayer actor code it will cause different results on different computers which will almost certainly cause some form of [[desync]]. In display code [[screenpeek]] should be used instead to allow viewing of others screens in coop. | It is of little actual use in con (despite the impressions of some mod authors who misunderstand dukes netplay). In singleplayer it will always be fixed at the first player index. In multiplayer actor code it will cause different results on different computers which will almost certainly cause some form of [[desync]]. In display code [[screenpeek]] should be used instead to allow viewing of others screens in coop. | ||
Initially player indexes go from 0 to [[numplayers]]-1 however they do not change when a player quits so you will end up with non continuous indexes. | |||
Revision as of 11:31, 22 August 2005
myconnectindex is a gamevar which represents the LOCAL PLAYER
It is of little actual use in con (despite the impressions of some mod authors who misunderstand dukes netplay). In singleplayer it will always be fixed at the first player index. In multiplayer actor code it will cause different results on different computers which will almost certainly cause some form of desync. In display code screenpeek should be used instead to allow viewing of others screens in coop.
Initially player indexes go from 0 to numplayers-1 however they do not change when a player quits so you will end up with non continuous indexes.