We have made a minor adjustment to rule 3.0 of the Player Owned Base Rules:
This segment:
Original Rule Wrote:Siege Declarations last for two weeks once active. Once a Siege Declaration expires, the base may not be subject to another Siege Declaration for four weeks.
Has been changed to instead read:
Amended Rule Wrote:Siege Declarations last for two weeks once active. If the vulnerability window of a base changes during this siege period, the Declaration will remain valid for two additional days. Once a Siege Declaration expires, the base may not be subject to another Siege Declaration for four weeks.
Changing the vulnerability window of a base in response to a siege declaration is perfectly valid, and if it makes it easier for players to organize a defense, should definitely be done. However, it is not intended for players to change the siege window in the middle of a siege to deliberately "rob" the attackers of one of the 14 days they are allowed to siege for. In the 24-hour period before a siege fully kicks in, changing the vulnerability window will not extend the siege period. Any changes made thereafter, during the two weeks of active siege, will.
As of the next server restart, the following (minor) change to PoB wear & tear mechanics will be going live:
PoBs with insufficient - or insufficiently cared for - crew will take 6 times the usual wear and tear damage instead of the previous multiplier of 3. This means that an uncrewed PoB will be taking 1,200 damage per minute instead of 600, reducing the amount of time a poorly-maintained PoB will stick around for.
These are some (rough, rounded up) numbers of days an uncrewed PoB at full HP previously remained around for:
Quote:Core 1 - 14 days
Core 2 - 19 days
Core 3 - 24 days
Core 4 - 28 days
The new numbers are:
Quote:Core 1 - 7 days
Core 2 - 10 days
Core 3 - 12 days
Core 4 - 14 days
Howdy, everybody. It's been a minute. We've had a few staff changes since the last announcement (...in August of last year), and since we've been proactively targeting staff recruitment to try and get a handle on the mounting staff workload, I figured it'd be good to go over all the changes since then.
But first, please welcome our newest administrators and moderators!
I will be taking the Discovery game server down for a few hours over the coming fortnight.
I will use this time to migrate the game VM to a different host. This new host is a different hypervisor on different hardware, which is better located, which should offer better connection times (e.g. ping) for most of Europe & the Americas, and provides better single core performance, so I'm hoping it'll be able to handle slightly larger groups of players in close proximity better than we've had before.
I'll probably also use it as a convenient opportunity to perform other unrelated maintenance.
I estimate this work will take 3 or so hours and provisionally schedule it in the window of 00:30-06:30 UTC on Saturday 16th.
The web server should still function during this time, so the forums, development tools, wiki, etc. should still work - but obviously the forum integration with the game will be out of action.
If you've restarted your launcher and FL since 22:46 on Monday 11th, there should be no need for you to take any action - when the game server returns it should appear on the server list for you immediately.
In the mean time, if you're curious and want to compare connectivity, the current game IP is 95.217.88.9, and the new game IP will be 88.198.43.188. Those of you with test server access can go and try it today.