PTR Changelog 2018-10-19: attackController

[artch]

This post describes changes on the Public Test Realm.

Commits on GitHub:

• engine#440cc83
• common#68d9b1d

Changes:

• Controller downgrade timers are changed to these values:
  • 1 level: 20000 ticks
  • 2 level: 10000 ticks
  • 3 level: 20000 ticks
  • 4 level: 40000 ticks
  • 5 level: 80000 ticks
  • 6 level: 120000 ticks
  • 7 level: 150000 ticks
  • 8 level: 200000 ticks

• When the controller gains or loses one level, its downgrade timer is set to 50% instead of 100%.

• Safe mode activation unavailable period starts from this 50% point minus 5000 ticks.

See previous discussion in this forum thread.

This feature is supported in private server ptr branch:

npm install screeps@ptr

[NobodysNightmare]

Any way to determine “time to safe mode unavailable“ except for calculating based on those numbers?

I would love to have a stable way of retrieving that number without updating my code with each balance patch

[artch]

@nobodysnightmare It was before:

CONTROLLER_DOWNGRADE[level] - CONTROLLER_DOWNGRADE_SAFEMODE_THRESHOLD

Now it is:

CONTROLLER_DOWNGRADE[level] / 2 - CONTROLLER_DOWNGRADE_SAFEMODE_THRESHOLD

So you're safe even if you don't make any changes to your code.