administrators

@tigga said in AttackController too easy to recover from:

For an RCL 8 base the defender loses maybe 15% of the energy into the controller. Ticking down an RCL 8 to RCL 1 takes significantly longer than 6 ticks.

Consider this: 15% of an RCL8 controller equals to 1.6M energy, or 160K ticks per source harvesting. This is the time which the owner has lost even if he managed to recover.

you need to regain power in a room for 6 ticks to undo that seiging

Not exactly true. The defender needs to fight back and regain control over the controller for 1000 ticks in order to execute those 6 ticks. The 1000 ticks is the crux, not the 6 ticks. And the attacker is supposed to guard the attacked controller while he's downgrading it. If your tactic is sending an one-time raiding party and then just simply sending a lone claimer every 1000 ticks, you're not supposed to success.

@gankdalf said in Invaders die when pvp starts:

It might be better to just not allow spawning invaders manually while hostiles are in the room...

As far as I know, it's not currently allowed. If you're able to so so, please report a bug.

Also, summoned invaders should kill themselves when room is under attack. If that's not happening, please report a bug, replay link (or replay coordinates in case of swc) is very welcomed!

This is interesting. Thank you for report, that looks like a bug most definitely, we'll take a look as soon as possible.

User-summoned invaders die immediately if there's another player in the room, see here:

https://github.com/screeps/engine/blob/master/src/processor/intents/creeps/tick.js#L118-L120

@semperrabbit We could store such objects in the short {__objId: 'abc123'} form, but it would disable debugging using Memory inspector UI then.

@gankdalf

If they get used to serializing game objects like this, how much more confused will they be when they try to serialize one of their own objects and the instance is destroyed?

They will be confused anyway, since Memory object is going to become persistent, i.e. you can store live data in it without any serialization, and it will be parsed from JSON only on global restarts.

@ags131 We can add RawMemory.autoCreateObjects boolean property which is true by default, but you can change it to false before accessing Memory first time on the tick.

@semperrabbit It highly depends on how you use your Memory. In our synthetic tests the increase is only about 15%. And if you don't save objects to Memory (i.e. if there is no __objId key), it's even less.

@semperrabbit It doesn't matter how bad it is, if it's being run only once a day (with IVM).