What's new
Embers Adrift

Register a free account today to Ignite your Adventure! Once signed in, you'll be able to participate with the Embers Adrift community. Your active account will also be the same account used to purchase, download, and login to the game.

Bug I've been cloned!

is this a bug?

Calkrow

Well-Known Member
I also did /report in game but was incorrect in saying I'd just logged in. In fact game had been left running overnight with character sitting at the fire at camp 3 in SNH.

When I went past a group of about 12 characters running in place my character was cloned. Clone initially followed me a bit but after standing a the mass of running in place chars for a few mins (whilst I copied the log file) when I moved away the clone didn't follow.

Log file available but too large to attach.
 
Combat log has gone funny and no notification of xp for the kill, and no increase in xp bar.
1650261959040.png
 
The option to go back to character selection logged me out of game, but as world is locked can't get back in to see if that clears the issues. Final log attached.
 

Attachments

  • embersadrift - Clone 2.zip
    1.4 MB · Views: 1
Thanks for the reports. This appears to be isolated to your machine. Your computer doesn't know who the incoming packets belong to and freaks the hell out. Still investigating...
 
Knowing that you made some network changes recently, which helped resolve the memory leak issue, are you perhaps being too keen in tiding up memory buffers for network traffic or similar that are actually still in use?

Could just be coincidence that the cloning issue has just appeared, but perhaps not and it's also linked to the higher number of players recently online simultaneously.
 
Knowing that you made some network changes recently, which helped resolve the memory leak issue, are you perhaps being too keen in tiding up memory buffers for network traffic or similar that are actually still in use?
Unlikely as those cleanups only happen on disconnect & reconnect - not in the middle of someone's session.

Could just be coincidence that the cloning issue has just appeared, but perhaps not and it's also linked to the higher number of players recently online simultaneously.
I wouldn't say player counts are higher/lower than they were previously so I doubt that is the issue.
 
I got this issue as well once this weekend in South Newhaven. Logout/Login fixed it. It was on a new game session just after starting the game.
 
Back