Skip to content

A black market way to transfer a ship from an uncontrolled system to a controlled one? #20

@jpcsupplies

Description

@jpcsupplies

Perhaps add an extensible way to pack the ship while in an uncontrolled server when about to cross into a controlled one, such as a one time security code or if the player knows the controlled system network dedicated server password.

Behaviour: When in interstellar space (or a depart LCD) add the one time code (perhaps buyable from the controlled system trade hub) or the controlled server group passcode to the /depart command.

Example1:
Admin of Controlled system knows system passcode:
/depart MyReallyReallySecretUniverseCode12345!!!

Example 2:
Normal player in controlled system purchases a "customs entry VISA" code for a million credits, then travels to an uncontrolled system where they may have just pirated themselves a ship...
/depart 23451-92112-23333-92937
(Argh! I'm a pirate!)

Thoughts:
Servers sometimes shut down, maybe add a "salvage my ship" feature too, where from a controlled server, you can list all the packed offline ships owned by the player, and designate a steep "recovery fee" to spawn it into the current server and use it again.
Logic: is not an admin, calculate size/value of ship, wait for payment.
Admin Logic: show stats of size/value, allow to recover for free.

In Either case once it has been confirmed spawned in game, remove the packed file with the ship; to minimise misuse. Packed ships themselves could be encrypted with the players steam ID or such in a single file, making it difficult to exploit even ships with no passcode.

Issues: packed ships in "storage" may use an unknown passkey from the shut down server; unless it was an uncontrolled system - in which case there was no passcode. In effect only the "pirate/contraband" ships would be salvagable. Interesting thought. It might give an incentive for server admins to link servers with gleeful abandon that are not a controlled network of worlds.
Alternate solution: store ships in a single combined file, and only encrypt a sanity check string with the server passkey. This would allow the controlled system ships to still be accessible, while still preventing them spawning when they should not.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions