Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
social.tchncs.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
A friendly server from Germany – which tends to attract techy people, but welcomes everybody. This is one of the oldest Mastodon instances.

Administered by:

Server stats:

3.8K
active users

social.tchncs.de: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#elitedangerous

17 posts16 participants0 posts today
Public
smeg

Finally finished claiming my system with the first outpost built! Not sure what to add next, or whether I should focus on putting the minor faction I want in power (already present in the system, but at the #3 position).

#EliteDangerous
Replied to Scopique
Public
B. Kramer

@scopique
I've been playing for 4 months. That early-game money scarcity is real. I started with 'safe' data courier missions, and it seemed like it would take forever to get the millions needed for the more notable, better ships. I saw my starting 250Kcr as pretty meager, but soon realized I'd need a better ship to make more progress. Jump range was my main limiting factor, and I realized something like a Hauler + upgrades was pretty affordable even with the starting credits.
#EliteDangerous

Continued thread
Public
Scopique

As much as I don't like landing on planets, I enjoyed tracking down the samples and such. I was lucky: I found a wide field of these things and was able to drive from one end of the field to the other in order to satisfy the 150m distance between samples, so that was easier.

#EliteDangerous
Public
crypticcelery

Just chatted with someone about #EliteDangerous again...
And wow, do I seem to miss it. At the same time, it also feels somewhat daunting to get back into it, after having last played it in the last decade, and missing a lot of the recent stuff (time and life and stuff getting in the way). Like maybe finding a player controlled faction or a few others to play with would be nice, but like, talking to new people is also scary (a bit).

Public *
Iain Collins

It's late and time for bed - although I'm on holiday for a week after tomorrow and seeing family, which will be nice.

I'm excited to have reached a major milestone with ardent-industry.com tonight.

Players can now sign in using their existing Fdev account and I've attached some (slightly) useful functionality to doing that - using some new API endpoints I created to surface the nearest station services to the CMDR.

#EliteDangerous

More details on the forum: forums.frontier.co.uk/threads/

The homepage of ardent-industry.com displaying information for a player who is signed in, including their CMDR name, ship, credit balance, location, the name and location of their Fleet Carrier (if they have one) a range of the nearest stations offering various services.
Public
Beko Pharm

Parsing the Elite Dangerous Journal

I gave in and changed my event forwarding method in node-red for the Elite Dangerous Journal. This file is updated on various in-game events but in a way that makes it difficult to get new events only since last update. Another problem is that it’s not really a valid JSON file because it has one JSON per line but it’s not a valid JSON array. This is why it has to be parsed line by line and mashed together by event type (name) again to get the latest data for each event type per dump. Each event has it’s own timestamp by set by the game. The latest timestamp is now saved on the special flow const so node-red keeps the value in the “global” memory of the current flow:

msg.payload.event = "Journal";let newJournalTimestamp = flow.lastJournalTimestamp;Object.keys(msg.payload).forEach((key) => {  if (msg.payload[key].timestamp) {    const keyTimestamp = new Date(msg.payload[key].timestamp).getTime();    if (!flow.lastJournalTimestamp || flow.lastJournalTimestamp < keyTimestamp) {      // this entry is new - keep it. MULTIPLE events may have the      //  same timestamp so wait with reassigning so we don't skip      //  em or get the latest a 2nd time if nothing else changes.      // update the next latest timestamp if this is newer      if(!newJournalTimestamp || newJournalTimestamp < keyTimestamp) {        newJournalTimestamp = keyTimestamp;      }    } else {      // lastJournalTimestamp is newer, skip this      msg.payload[key] = null;    }  }});// make sure this is a valid date for the next timeflow.lastJournalTimestamp = newJournalTimestamp || new Date().getTime();// remove all nulled events from the payloadmsg.payload = Object.fromEntries(  Object.entries(msg.payload).filter(([_, p]) => p !== null));msg.payload.timestamp = new Date(flow.lastJournalTimestamp);return { payload: msg.payload };

So I do now keep track of the last read timestamp and reject every event that is older than the last read keeping the Journal dump smaller. This way I don’t have to try to keep track of the “latest” event to drag data from. Refuelling e.g. can happen from whopping 4 (or more) different events and it’s painful to compare all and check which one is the latest to keep track of the real current fuel levels for each tank.

Downside is I won’t get a full set of data for the current session any more if I have to reload my HUD app. This could be mitigated by using MQTT though where I could simply persist each event topic. That is already implemented and I can choose between SocketIO or MQTT in my app anyway.

https://beko.famkos.net/2025/03/29/parsing-the-elite-dangerous-journal/

#EliteDangerous#EliteDangerousOdyssey#homeCockpit
ExploreLive feeds
About