It is silly that we either have to travel to the engineer, or lookup blueprints offline, to see what materials we need, or still need to get. If we unlock the engineer, visit the engineer, and see the blueprints, then those blueprints should be permanently stored in our ship's computers, and we should have access to see blueprints whenever we want.
Why are things so silly in the future?
SDK rant.
Why are things so silly in the future?
SDK rant.
If FD would actually implement a proper SDK 3'rd party deveolopers could take care of it. All that would be needed are blank panels where 3'r party apps could render into the game, and take input from the game back to the 3'rd party apps.
I made a suggestion before about implementing a lua interface for Elite: Dangerous, but it never gained any traction.
Plugin's/addons could run directly in the ED runtime, or a 3'rd party app could communicate to ED using IPC/RPC calls.
The SDK doesn't have to expose much. At a minimum, instead of writing to a file, the SDK can provide, at request, the same information via IPC/RPC, or through callback methods in a lua plugin. This information is already being provided, so why not just provide it to a lua plugin?
I made a suggestion before about implementing a lua interface for Elite: Dangerous, but it never gained any traction.
Plugin's/addons could run directly in the ED runtime, or a 3'rd party app could communicate to ED using IPC/RPC calls.
The SDK doesn't have to expose much. At a minimum, instead of writing to a file, the SDK can provide, at request, the same information via IPC/RPC, or through callback methods in a lua plugin. This information is already being provided, so why not just provide it to a lua plugin?