Myconnectindex - Revision history

Fox at 00:49, 18 August 2020

2020-08-18T00:49:13Z

← Older revision		Revision as of 17:49, 17 August 2020
Line 1:		Line 1:
	myconnectindex is a [[gamevar]] which hold the ID of the player using the local computer.		myconnectindex is a [[gamevar]] which hold the ID of the player using the local computer in a multiplayer game. In single-player it's always zero.

	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.

Fox at 00:48, 18 August 2020

2020-08-18T00:48:53Z

← Older revision		Revision as of 17:48, 17 August 2020
Line 1:		Line 1:
	myconnectindex is a [[gamevar]] which ~~represents~~ the ~~LOCAL PLAYER~~		myconnectindex is a [[gamevar]] which hold the ID of the player using the local computer.

	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.

DeeperThought at 04:53, 18 May 2006

2006-05-18T04:53:37Z

← Older revision		Revision as of 21:53, 17 May 2006
Line 4:		Line 4:

	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.		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.

			[[Category:Constantly updated gamevars]]

Plugwash at 19:31, 22 August 2005

2005-08-22T19:31:56Z

← Older revision		Revision as of 12:31, 22 August 2005
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.

Plugwash at 13:08, 10 January 2005

2005-01-10T13:08:15Z

← Older revision		Revision as of 06:08, 10 January 2005
Line 1:		Line 1:
	myconnectindex is a [[gamevar]] which represents the LOCAL PLAYER		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.		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.

Plugwash at 08:34, 10 January 2005

2005-01-10T08:34:24Z

← Older revision		Revision as of 01:34, 10 January 2005
Line 1:		Line 1:
	myconnectindex is a ~~constantly updated~~ [[gamevar]] ~~used to determine the order in~~ which ~~players have connected to a game. This is useful for player manipulation in multiplayer, and player manipulation outside of~~ the ~~player [[actor]].~~		myconnectindex is a [[gamevar]] which represents the LOCAL PLAYER

	~~The current version~~ of the ~~network code does not properly keep track of the myconnectindex between players and update their properties accordingly, so any player properties changed outside~~ of the player code ~~this way <i>may</i>~~ cause ~~sync issues, requiring a workaround~~. ~~Future versions of the network~~ code should ~~address or eliminate this issue~~.		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.

Mblackwell at 18:19, 25 December 2004

2004-12-25T18:19:29Z

New page

myconnectindex is a constantly updated [[gamevar]] used to determine the order in which players have connected to a game. This is useful for player manipulation in multiplayer, and player manipulation outside of the player [[actor]].

The current version of the network code does not properly keep track of the myconnectindex between players and update their properties accordingly, so any player properties changed outside of the player code this way <i>may</i> cause sync issues, requiring a workaround. Future versions of the network code should address or eliminate this issue.