I've noticed that there have been some threads on this recently, and I have spent most of my Star Made career working on providing some sort of crewable system on my ship. I have decided to write up a thread on the subject.
Crewability is important for several reasons. One, it allows several different players to collaborate on a ship, creating a sense of teamwork and comradery. Second, it allows for a player's skill to be more prevalent in a fire fight, as there would be more systems that he and his team can edit in order to gain the upper hand. Third, it gives a point to having interiors and better looking ships.Fourth, when Star Made's population booms (Hopefully, it will) you can't have 200 people all in ships. And lastly, there is a feeling of satisfaction from walking around a ship, managing the systems, working in a team and enjoying the view of space that I think is currently absent from Star Made.
This is what I suggest: Allowing people to directly interface with a ship's systems so they can effectively improve its efficiency in combat by a certain margin. It needs to be enjoyable at any time - whether on a long voyage, sitting in space dock, in combat, or going down a wormhole. I am not going to place down specifics of how this system should work, because honestly its up to Schema and dreaming up specifics creates more argument than productive discussion. So no statistics here. All I want is: A way for a few bridge player crew members to improve the ship, large amounts of AI crew that could contribute/replace bridge crews in an enjoyable and fun way. AI crew are important because you can't always find players, they could give life to anything (Space station, ship, factory, etc) and they give a point to an interior. Essentially, if you only hire AI crew, they give you a set bonus at the expense of building an interior.
But honestly, you don't have to take whatever I said above into stock. Any sort of being able to contribute to a ship would be great. If you think sitting on someone else's ship is boring, that's fine, but there would be many other people who would enjoy it. Please don't argue specifics/statics, as I find that always torpedoes a thread.
Crewability is important for several reasons. One, it allows several different players to collaborate on a ship, creating a sense of teamwork and comradery. Second, it allows for a player's skill to be more prevalent in a fire fight, as there would be more systems that he and his team can edit in order to gain the upper hand. Third, it gives a point to having interiors and better looking ships.Fourth, when Star Made's population booms (Hopefully, it will) you can't have 200 people all in ships. And lastly, there is a feeling of satisfaction from walking around a ship, managing the systems, working in a team and enjoying the view of space that I think is currently absent from Star Made.
This is what I suggest: Allowing people to directly interface with a ship's systems so they can effectively improve its efficiency in combat by a certain margin. It needs to be enjoyable at any time - whether on a long voyage, sitting in space dock, in combat, or going down a wormhole. I am not going to place down specifics of how this system should work, because honestly its up to Schema and dreaming up specifics creates more argument than productive discussion. So no statistics here. All I want is: A way for a few bridge player crew members to improve the ship, large amounts of AI crew that could contribute/replace bridge crews in an enjoyable and fun way. AI crew are important because you can't always find players, they could give life to anything (Space station, ship, factory, etc) and they give a point to an interior. Essentially, if you only hire AI crew, they give you a set bonus at the expense of building an interior.
But honestly, you don't have to take whatever I said above into stock. Any sort of being able to contribute to a ship would be great. If you think sitting on someone else's ship is boring, that's fine, but there would be many other people who would enjoy it. Please don't argue specifics/statics, as I find that always torpedoes a thread.
Last edited: