How about a way to remove EF agro ?

dunno

I think it has something to do with AI bases...

EF agro curently is 24 ish hours and imposible to remove

options 1. reduce agro time to 1 hours~


2. Make it posible to remove agro

3. Make them not randomly attack ppl

Do you mean:

Earthforce (fuzz etc)

or

Earth Force (capital ships etc)?


Kinda important to know which one.

These are who i ment, your babys are runing crasy, they sometimes just randomly chose to attack ppl and sometimes they dont even bother to attack someone whos agro aswell as imposible to lose agro other then waiting and please ider remove random agro or fighters (slaves returning fire giving me agro to all EF is anoying and realy limiting lvlingcapabiletys)

The earlier issue was because someone (who is now banned) was extremely sneaky:

They created a player team called "Earth Force" then the client got confused, thought all the AI were on the player team, and any aggro against the team became their aggro. And, unlike AI teams, player teams have to manually forgive aggro.... We thought it'd been solved, but I guess not.

It was quietly brilliant, and I think it was an attempt to get the EF to rampage over wildspace, but luckily they're prevented from doing that. Their levels are raised for next uni, and I'll look over their aggro code again ~ they're also hunter AI type, which means they should behave like Vigilante.

/under investigation



Hint: I do say banned here. Creating player teams named after AI teams is one way to have the team & that account deleted.

Would u please explain for what reason i just agroed EF by healing my Slave? -.-

Earthforce (fuzz) or Earth Force (Capitals).

The Capitals use usual AI code, they shouldn't care less if you heal your own slave, unless it's shot them.

my slave shot it, i got agro, i suesided to lose agro and removed slave, then when healing the slave that initaly attacked it i regained agro

We've tracked down the issue, which is that AI are losing their Spawners, and thus:

a) Being able to wander where they want, e.g. Wildspace for EF when they're supposed to be bound to EF space

b) Ignoring Min/Max targeting restrictions / team aggro restrictions (because, literally, they don't think that they are bounded by loss of team aggro rules)



We're looking into it; the issue is effecting more than just EF ships, but thanks for bringing it up.