O7!
Paul_CrowtherGreetings Commanders,
We will be releasing a new update for Elite Dangerous on Wednesday March 19.
Release Schedule (All times in UTC)
Please be aware these are estimated times and are subject to change.
- 9AM - Servers offline for maintenance
- 11AM - Servers back
Update Notes
Features of Note/Journal Additions
The following Journal entires are now actually logged:
- A temporary system has been introduced relating to "System Claim Unsuccessful" errors - after one such unsuccessful claim, the system will be marked as invalid and no further claim attempts will be permitted.
- This is a known issue which is caused by the game being unable to locate a suitable position for the initial starport, which can occur for many different reasons. Repeated claim attempts by any player on an affected system will never result in success.
- As these positional issues are resolved, affected systems will be removed from the invalid list and will once again be claimable.
Community Goal
- The powerplay data in the event "Location" and "FSDJump" supplied regards of if the players is pledged to a power or not.
- "PowerplayCollect"
- "PowerplayDeliver"
- "PowerplayMerits"
- "PowerplayRank"
- "CarrierLocation"
- Added a new status flag for the npc crew to indicate if they're active or not.
- Added a new status flag SupercruiseOvercharge for overcharge status.
- Added a new status flag SupercruiseAssist for whether assist is active.
- Ensured that the lightsOn status flag is active when the flashlight is active.
- The new megaships from the recent Community Goal will be deployed with the update
Bug Fixes:
Server side improvements:
- Fixed a crash when switching views in the System Map
- Fixed an instance of a mission interaction crash
- Fixed instances of crashes when scanning a megaship or installation
If you encounter any further issues please be sure to report them on our Issue Tracker.
- Renaming of facilities should be now be consistently permitted for the system architect
- Planetary ports can now be renamed by the system architect
- Inactive system colonisation ships will now be marked as they jump back to the registration origin system
- Star system information will now be updated correctly when completing facilities with differing game language settings
- Improved stability of game client during system colonisation ship jumps
- Significantly improved capacity for server-client information transfer relating to player colonised systems
- This is intended to prevent any further instances of temporarily deactivating the colonisation contact. The team will continue to monitor the situation closely as humanity expands.
Paul_Crowther
I'm a bit uncomfortable bringing this up, but could you advocate for the idea that tritium should be automatically taken from the Fleet Carrier's cargo hold without the need for an intermediary like the Type-9?![]()
Are you on the 'Aisling Duval Comms' on Discord? if not, I highly recommend joiningMonths have passed. I quit powerplay and I suggest you do the same. If it goes like this, we'll quit the game completely anyway
That would decimate the forums.Ha, yes, could we please open a support ticket to fix outdated bug griping?
Can you confirm please if the Journal Manual is being updated to V38 with specifics of the journal changes.Greetings Commanders,
We will be releasing a new update for Elite Dangerous on Wednesday March 19.
Release Schedule (All times in UTC)
Please be aware these are estimated times and are subject to change.
- 9AM - Servers offline for maintenance
- 11AM - Servers back
Update Notes
Features of Note/Journal Additions
The following Journal entires are now actually logged:
- A temporary system has been introduced relating to "System Claim Unsuccessful" errors - after one such unsuccessful claim, the system will be marked as invalid and no further claim attempts will be permitted.
- This is a known issue which is caused by the game being unable to locate a suitable position for the initial starport, which can occur for many different reasons. Repeated claim attempts by any player on an affected system will never result in success.
- As these positional issues are resolved, affected systems will be removed from the invalid list and will once again be claimable.
Community Goal
- The powerplay data in the event "Location" and "FSDJump" supplied regards of if the players is pledged to a power or not.
- "PowerplayCollect"
- "PowerplayDeliver"
- "PowerplayMerits"
- "PowerplayRank"
- "CarrierLocation"
- Added a new status flag for the npc crew to indicate if they're active or not.
- Added a new status flag SupercruiseOvercharge for overcharge status.
- Added a new status flag SupercruiseAssist for whether assist is active.
- Ensured that the lightsOn status flag is active when the flashlight is active.
- The new megaships from the recent Community Goal will be deployed with the update
Bug Fixes:
Server side improvements:
- Fixed a crash when switching views in the System Map
- Fixed an instance of a mission interaction crash
- Fixed instances of crashes when scanning a megaship or installation
If you encounter any further issues please be sure to report them on our Issue Tracker.
- Renaming of facilities should be now be consistently permitted for the system architect
- Planetary ports can now be renamed by the system architect
- Inactive system colonisation ships will now be marked as they jump back to the registration origin system
- Star system information will now be updated correctly when completing facilities with differing game language settings
- Improved stability of game client during system colonisation ship jumps
- Significantly improved capacity for server-client information transfer relating to player colonised systems
- This is intended to prevent any further instances of temporarily deactivating the colonisation contact. The team will continue to monitor the situation closely as humanity expands.
We need the demolish facility button, and boosted insulating membrane production. Please.Greetings Commanders,
We will be releasing a new update for Elite Dangerous on Wednesday March 19.
Release Schedule (All times in UTC)
Please be aware these are estimated times and are subject to change.
- 9AM - Servers offline for maintenance
- 11AM - Servers back
Update Notes
Features of Note/Journal Additions
The following Journal entires are now actually logged:
- A temporary system has been introduced relating to "System Claim Unsuccessful" errors - after one such unsuccessful claim, the system will be marked as invalid and no further claim attempts will be permitted.
- This is a known issue which is caused by the game being unable to locate a suitable position for the initial starport, which can occur for many different reasons. Repeated claim attempts by any player on an affected system will never result in success.
- As these positional issues are resolved, affected systems will be removed from the invalid list and will once again be claimable.
Community Goal
- The powerplay data in the event "Location" and "FSDJump" supplied regards of if the players is pledged to a power or not.
- "PowerplayCollect"
- "PowerplayDeliver"
- "PowerplayMerits"
- "PowerplayRank"
- "CarrierLocation"
- Added a new status flag for the npc crew to indicate if they're active or not.
- Added a new status flag SupercruiseOvercharge for overcharge status.
- Added a new status flag SupercruiseAssist for whether assist is active.
- Ensured that the lightsOn status flag is active when the flashlight is active.
- The new megaships from the recent Community Goal will be deployed with the update
Bug Fixes:
Server side improvements:
- Fixed a crash when switching views in the System Map
- Fixed an instance of a mission interaction crash
- Fixed instances of crashes when scanning a megaship or installation
If you encounter any further issues please be sure to report them on our Issue Tracker.
- Renaming of facilities should be now be consistently permitted for the system architect
- Planetary ports can now be renamed by the system architect
- Inactive system colonisation ships will now be marked as they jump back to the registration origin system
- Star system information will now be updated correctly when completing facilities with differing game language settings
- Improved stability of game client during system colonisation ship jumps
- Significantly improved capacity for server-client information transfer relating to player colonised systems
- This is intended to prevent any further instances of temporarily deactivating the colonisation contact. The team will continue to monitor the situation closely as humanity expands.
Demolishing badly placed or unwanted facilities.You need an undo button? For what?
Except when I place a facility in a bad spot, not the game.That is called bug and needs to be fixed. Still no need for an undo button...
This very much.Months have passed. I quit powerplay and I suggest you do the same. If it goes like this, we'll quit the game completely anyway
nopeAre we there yet?
Don't we have this already? I'm currently building a primary port and when I go to a Sys Col contact it gives me the option to release my claim. Or asking you for something different?3. "Cancel Colonization" button to stop colonization of new system.
(music) plucky plucky PLUCKY pluckypluckypluckypluckynope