[http://sourceforge.net/p/ufoai/bugs/2833 Item 2833] imported from sourceforge.net tracker on 2013-01-28 19:50:51

The bug is only visible in campaign mode, while using maps with randomspawn.
the phalanx actor starting positions do not get randomized (the aliens/civ positions are). What does get randomized is the weapons loadout of the phalanx actors.

2.4 dev IA 32 Mar 1 2011 Win32 Debug build 1298946421

tilli
===== Comments Ported from Sourceforge =====

====== geever (2011-05-08 21:04:34) ======

Confirmed on current master. This is showstopper, should be fixed for 2.4.

-geever
====== tlh2000 (2011-05-09 05:31:50) ======

cl_game.c:GAME_StartBattlescape calls GAME_SendCurrentTeamSpawningInfo and this is read in g_client.c:G_ClientTeamInfo

the actor starting pos order is not random by default - see g_client.c:G_ClientGetFreeSpawnPoint. The random spawn order is an option in the map worldspawn entity. so this is no bug - "only" the item mixing is
====== tlh2000 (2011-05-09 05:33:45) ======

is the character name, the skin and other stuff correct for each character? or is that mixed, too?
====== darkrainx (2011-05-10 00:01:15) ======

http://ufoai.ninex.info/forum/index.php?topic=5926.msg47227#msg47227

This post makes me think the character name, the skin, and the stats might be the ones that are actually mixed (About the kills being credited to the owner of the gear)
====== *anonymous (2011-05-10 16:03:52) ======

Can sometimes be observed visually in the Alternative HUD

http://imgur.com/cWzB5
====== tlh2000 (2011-05-19 18:33:10) ======


====== tlh2000 (2011-05-22 09:03:12) ======

G_ClientGetFreeSpawnPoint
====== tlh2000 (2011-05-22 09:12:06) ======

the problem is in CL_ActorGetChr - it assumes that the chrList is in the same order as the server returned entities - this is not the case for random spawns
====== tlh2000 (2011-05-22 09:28:23) ======

fixed in ee43ed8ae811622bc897f199851b21f92cfeda53
====== sf-robot (2011-06-05 10:20:03) ======

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).