Should be fixed now.

Now only if GNA would fix the uploading errors...

Note, the way the game currently handles this is wrong, and prone to cheating.
Will have to fix that aspect of it another day.

I found the reason for this, but I didn't have time to make a patch yet.

The problem is that when the droid (cyborg) goes into the transporter, it gets removed from the apsDroidLists. (I don't really know the logic behind that, I would just set a flag that it is on a transport ship, not remove it from the list.)

When it exits the transporter, we check apsDroidList first, and we notice it isn't there (well duh! We removed it), and then it bails out with that error in IdToDroid().

Also, unless I am blind, I don't see a sendDroidDisEmbark() when we remove a droid from the transport. (Though, that routine also checks IdToDroid().)

In short, we need to get the droid back in apsDroidList via addDroid() (which is already done), then after that, we must send the same info to all other clients (which isn't done), so they update their apsDroidList also.

If nobody beats me to it, I will have a patch ready when I get some time.

This is also a trunk issue.

Are you using a debug build while testing this?

If so, can you post the stdout.txt & stderr.txt?

If not, you may still get some info in those files.

Looking for stuff like :
warning |000001731376: [strresGetString] Couldn't find string for id "Flamer"
or
error |000002068417: [recvDroidInfo] recvDroidInfo: Packet from 0 refers to non-existent droid 161664!