- Joined
- Nov 25, 2007
- Messages
- 1,665
- Reaction score
- 13
- Points
- 38
- Location
- Germany
- Website
- www.enderspace.de
- Preferred Pronouns
- Can't you smell my T levels?
I'll be copy-pasting my posts here from my dev thread at m6.
Orbitrader will be a multiplayer economy system. The actions that you perform have impact on prices and product production in bases (and later - at space stations). The products' prices and amount are stored on a server, so other users will benefit from your actions... or just the opposite.
This is how the MFD looks currently:
News:
Now, Orbitrader detects certain events of your flight, such as:
- launching
- landing
- leaving orbit
- entering orbit
- slinging
- powered slinging
and after these events occur, it stores the details of your orbit, as well as state vectors, date and fuel reserves on the server. After logging in again, the MFD tries to validate your ship (currently only class name and ship's name are taken into account), and after successful validation, it downloads the latest saved data. Using the data, your previous state can (and must) be restored.
here's how such reports look via www interface:
Below, I've just slinged Jupiter, so I've reached system escape velocity, and I had no apohelium. Otherwise, I'd get apohelium distance and time. The first would let admins and other users know what was the destination, and the latter, along with saved MJD, would let determine if somebody "accelerated" his ship a bit too much. As such, this info is a good remedy against ScnEditor cheaters... or worse. Unfortunately I'll still have to think of something to allow for constant acceleration transfers.
What's left to do is making the status checker function act as a module, not as MFD, so you don't need to have your MFD switched on all the time. The next thing will be thread support, because even the libCurl multi interface lags Orbiter.
Orbitrader will be a multiplayer economy system. The actions that you perform have impact on prices and product production in bases (and later - at space stations). The products' prices and amount are stored on a server, so other users will benefit from your actions... or just the opposite.
This is how the MFD looks currently:
News:
Now, Orbitrader detects certain events of your flight, such as:
- launching
- landing
- leaving orbit
- entering orbit
- slinging
- powered slinging
and after these events occur, it stores the details of your orbit, as well as state vectors, date and fuel reserves on the server. After logging in again, the MFD tries to validate your ship (currently only class name and ship's name are taken into account), and after successful validation, it downloads the latest saved data. Using the data, your previous state can (and must) be restored.
here's how such reports look via www interface:
Below, I've just slinged Jupiter, so I've reached system escape velocity, and I had no apohelium. Otherwise, I'd get apohelium distance and time. The first would let admins and other users know what was the destination, and the latter, along with saved MJD, would let determine if somebody "accelerated" his ship a bit too much. As such, this info is a good remedy against ScnEditor cheaters... or worse. Unfortunately I'll still have to think of something to allow for constant acceleration transfers.
What's left to do is making the status checker function act as a module, not as MFD, so you don't need to have your MFD switched on all the time. The next thing will be thread support, because even the libCurl multi interface lags Orbiter.
Last edited: