Elite Dangerous | Trailblazers Release Schedule

So, quick calc, that's 30 full loads of a 750t cargo cutter (22,352t of commodities in total) to build my scientific outpost. Might take a while...

Also noted that naming actually sounds good (or at least not bad - really pleased to see there is a full custom option)
Thanks for the numbers I've gone for the same outpost layout as you...in my T9 (currently 744T) this will be 8 trips per week, not too bad though might mean I don't do anything else in game for the next 4 weeks :)

EDIT: I was kinda hoping (assuming?) that we would be getting a very large cargo vessel with this update...dare I say it?...like a Panther Clipper LX.
 
Last edited:
I need to understand this better - the construction ship has appeared in a crap location - 395k ls from the star - not sure why it picked there in an empty system. If anyone fancies delivering to help, feel free! (note 4 weeks to complete)
Maybe the orbiting body has to be linked to a scoopable star ?
Hope we will have a real answer from Frontier soon
 
Am I wrong or does it cost several billions of credits to finish first starport?
Edit: I was wrong... its just around a billion and I think thats fair!
 

Attachments

  • 20250226_184217.jpg
    20250226_184217.jpg
    538.6 KB · Views: 152
Last edited:
Am I wrong or does it cost several billions of credits to finish first starport?
Given that this is a frontier settlement in a newly settled system, I'm more curious as to why you don't seem to have an option for the first starport to be an Odyssey style painted landing pad and a metal shack with a bucket round the back for the cost of a Cutter load of steel, a few machinery bits and a tin of paint.
 
Is there a good place to provide feedback for this? The 5,000,000 "softcap" on weekly income is kinda low, like is it a percentage on future income past the first 5 mil like 10% or something?

Edit Thread's here:
 
Last edited:
You should work with Klingon Programmers where I once worked....

The Klingon Programmer's Code of Honour:
  1. A TRUE Klingon warrior does not comment his code!
  2. This machine is a piece of GAGH! I need dual Pentium processors if I am to do battle with this code!
  3. I have challenged the entire ISO-9000 review team to a round of Bat-Leth practice on the holodeck. They will not concern us again.
  4. Behold the keyboard of Kalis! The greatest Klingon code warrior that ever lived!
  5. Defensive programming? Never! Klingon programs are always offensive. Yes, offensive programming is what we do best.
  6. Klingon programs don't do accountancy. For that, you need a Ferengi programmer.
  7. Klingon function calls do not have 'parameters' - they have 'arguments' - and they ALWAYS WIN THEM.
  8. This code is a piece of crap! You have no honour!
  9. By filing this bug you have questioned my family honour. Prepare to die!
  10. I am without honour...my children are without honour... My father coded at the Battle of Kittimer...and...and...he... HE ALLOWED HIMSELF TO BE MICROMANAGED. <Shudder>
  11. You question the worthiness of my code?! I should kill you where you stand!
  12. Specs are for the weak and timid!
  13. Klingons do not believe in indentation - except perhaps in the skulls of their project managers.
  14. Klingon search engines don't just search the internet - they hunt!
  15. Klingons do not "release" software. Klingon software escapes, leaving a bloody trail of design engineers and quality assurance testers in its wake.
  16. Debugging? Klingons do not debug. Bugs are good for building up character in the user!
  17. As for project orders (requirements, goals): Klingons do not deliver; we EXECUTE. For the glory of the empire!
  18. Perhaps it IS a good day to die! I say we ship it!
  19. Our users will know fear and cower before our software! Ship it! Ship it and let them flee like the dogs they are!
Explains why console got dropped !
 
Back
Top Bottom