Jump to content

Introduction of Independent Shuttle Operators (NBT2.0 Concept)


Recommended Posts

Posted

Introduction

This proposal comes as we slowly start to talk about shifting both the server setting and potentially the map in the NBT2.0 talk and survey that’s been put out. In concept, it’s the idea of making us have a number of non-megacorp hired independent shuttle captain’s who’s domains mostly revolve around shuttle ownership and performing off-ship missions - and hireling crew of theirs.

Basic Framework Concept:

  • 1. Two launchpads of a standardized side are on map spawn allocated to independent shuttle operators. These shuttle owners have a well established licence agreement with the SCC allowing them to operate from the NBT2 vessel - giving security domain over them - yada yada but technically being private property and a partner of the ship with responsibilities they’re contractually obligated to fulfil.
     
  • 2. Upon spawn, the shuttle operators get the choice of what shuttle they spawn in their pad area, with a list of pre-made shuttles able to spawn and the name of it. Some might be more like skiffs, salvage teams, explorers, miners and so on. Depends on what the skiff operator’s deal/gimmick is.
     
  • 3. Independent deck crew can also spawn, technically only visitors/assistants on the station; they however are a pool who can team up with these shuttle operators for off ship operations.
     
  • 4. Shuttle operators can come back, trade with the vessel and basically act as a flexible away ship pool. Any task where you don’t want to off-ship half of your departments might be better served by throwing some independent shuttle operator at: like collecting plants for xenobotany, filling in for a lack of a miner, and so on. And if you do want to send some departments away, you can always ask your shuttle operators to do a transport run for the ship.
     
  • 5. Nominally they are under the operations manager, who then reports to the captain but they have a few unique rights for their shuttles technically being theirs and not the ships proper.

Why?

People have been asking off and on for independent crew who aren’t mega corporate. Personally I’d much rather people at least remain functionally aligned on the whole on the vessel and especially in departments. In other RP servers I’ve faced the ‘independent character in the team’ nearly always being obstructive and unhelpful for the mission and generally unfun to play around.

However, in the setting of them being independent little ship operators and their crew I think it makes a lot more sense. I reckon in this format, we could scratch that itch for people.

  • Like 1
Posted

This might be a derailment, but why not make this fully dynamic and make the captains' able to choose whether they are contracted with the SCC at all. Consider that the captain has a list of "presets" to choose from in an interface, and launching shoots an announcement to the Horizon or a fax to the bridge with a "heads up" about the type of vessel it is.

This could then be tailored to each type, whether they are SCC, SCC-contracted, fully independent, potentially hostile, or downright wanted for crimes.

Then the procedures for dealing with them falls to the Horizon bridge crew / command, from "make contact asap" to "provide supervision", "avoid if possible" and "engage to disable/arrest".

Posted

I appreciate the enthusiasm, but these suggestions are coming at far too early of a stage to even be considered. We can't really promise to even remember these two years down the line or however long it'll be when we decide the setting, which isn't even guaranteed to be something that fits these ideas.

There will be a point when we'll announce what we have and listen to community input, but in the embryonic stages of a big project it is impossible to do anything with these suggestions.

Guest
This topic is now closed to further replies.
×
×
  • Create New...