#Own territory suddenly conquered by teammate in "teams" mode

1 messages · Page 1 of 1 (latest)

thorny veldt
#

Some of my ("fungi") territory (most) got taken over by my teammate "[MOL] ESTER" suddenly at the ~15m mark. https://openfront.io/#join=QSxg2uyx

tribal pulsar
#

Looks kind of normal to me. [Mol]ester was to your right and to your left at that point. And your territory was quite slim after the h bomb fell. His namebox was shortly displayed over your territory because of that, it looks like

thorny veldt
#

at the 6second mark in that clip, why would that happen?

#

right when the city finishes building

tribal pulsar
#

Oh yeah I missed that one at 6 seconds

#

This is about separated clusters of territory being automatically annexed

#

Annexing only happens when territory changes, for performance reasons. That is why bots or players inside of your territory aren't always automatically annexed anymore like they would be in the past.

#

What happened here: the hydrogen bomb split up your territory. Most of it was to the north of the fallout. And you had a little seperate territory left to the south of the fallout

#

Then you won back some territory west of that. At the 6 second mark you can see the two parts of your territory south of the fallout, connect to each other. Right at that time the game decides that there was a territorial change and that that is now your main cluster of territory. Because it has a larger border surrounding it than the other cluster

#

So then your non-main seperate cluster of territory to the north of the fallout is automatically annexed. Precisely when the two parts to the south of the fallout meet and form one cluster.

#

Now, this would all have been normal. But it should not happen that a team member gets the land. Only if an enemy had been bordering it, then it would have been automatically annexed by the enemy

#

TL;DR: the annexation is normal in itself and explainable. That a team mate gets it, is a bug.

#

The dev team made a fix and thought the problem was gone. But it isn't. Someone made another definitive fix awhile ago. But that fix wasn't merged into the game yet. I'll go and check if it can be added