Jump to content

Allow multiple construct cores ?!


MrFaul

Multi core placement your thoughts  

14 members have voted

  1. 1. Would you allow multiple cores in one construct?

    • No, only core should be available.
      2
    • Sure why not, a backup could be useful.
      7
    • Only to allow third parties a option to build in their rented space.
      4
    • Turnip™
      1
  2. 2. Pro opinions (multiple choice)

    • Allows more complexity
      11
    • Should be inactive unless selected as master
      3
    • Would make renting rooms very easy
      8
    • A dirty but expensive way to improve base stats in small builds
      3
    • Should be necessary for moving parts
      4
  3. 3. Contra opinions (multiple choice)

    • Adds unnecessary complexity
      2
    • Is totally op
      3
    • Moving parts should only have an "anchor"
      6
    • The core is a vital part of a ship and additional cores would ruin that
      5
    • Heck no this is just a dumb idea in general
      2


Recommended Posts

I don't think cores have a role in combat, it's just needed to assign an id to a ship, to identify blocks as a ship, and to limit their size relatively to the core block tier. Combat is about shields/armor/structure.

Link to comment
Share on other sites

I feel like the core is the core. I'm not going bother voting in that confusing poll.

 

But the point of it anyways is that you protect it. You tend to put it in the center of the ship and it has the most shielding / protection possible.

Do we even know if ships even blow up and such like can you shoot away part the ship and make it to the core or if it's just pure basics RPG stats like hull, armor, shields, etc and it does not really matter?

Link to comment
Share on other sites

I agree on multiple cores, i can imagine going as far to have individual sections of a ship each with a core, whilst being a master core for the ship as a whole,

this would also allow subsequent ship and space station sections/upgrades to be manufactured  independently perhaps by different organizations and then brought together, so the task doesn't fall on a single organization to construct something truly massive.

Link to comment
Share on other sites

Hm I haven't considered to use cores as means to control the size of constructs but it is actually not a bad idea since a core is considered a serious investment depending on its size.

 

Also interlinking constructs would result in multiple cores but that depends on how it is handled, if it is only handled as some sort of "docking" it would still be two separate constructs with their own respective functions.

 

But the point of having only one as vital part of your construct is also very valid, this makes placement very strategic and knowledge of its placement important intel for battle situations.

 

I don't know if NQ have given it deep thought about that topic yet, yesterdays interview sounded more like "There will only be one" per construct.

Link to comment
Share on other sites

having multiple cores would actually be a benefit: imagine a ship that is cut in half, how do you detect the breach efficiently? you cant, except if you have reference points, like the cores. You could find the face normals of the mesh pointing towards it and differentiate that with the faces moving in the opposite direction and you got the location of the breach, now you just gotta migrate the tree to another reference and you got yourself 2 fully functional ship halves!

 

But dude, how do you merge them together? do you repair them into two ships?

well no, you can choose, either you spend resources to create two or you "relative anchor" them for repair so there only has a gap to be filled in. This would allow for cool separating ships like the prometheus to be built.

Link to comment
Share on other sites

Hm I haven't considered to use cores as means to control the size of constructs but it is actually not a bad idea since a core is considered a serious investment depending on its size.

 

Also interlinking constructs would result in multiple cores but that depends on how it is handled, if it is only handled as some sort of "docking" it would still be two separate constructs with their own respective functions.

 

But the point of having only one as vital part of your construct is also very valid, this makes placement very strategic and knowledge of its placement important intel for battle situations.

 

I don't know if NQ have given it deep thought about that topic yet, yesterdays interview sounded more like "There will only be one" per construct.

Well, the 1 meter Core JC used on the video can build up to 72 meters radius of a construct or something. The largest core is 4 cubic meters in size. My guess is we will need multiple "expansion Cores" to expand our constructs.

Link to comment
Share on other sites

  • 2 weeks later...

Additionally It would add to the pvp layer of the game (team 1 managed to take control of core 1) warning all defenses in that area are now inactive/hostile defenders will know to attack and/or defend core 2. Although if this is gonna be a thing hack time would need to be scaled back a bit for balance or divided between the cores.

 

Would allow build/industrialists to have a bigger role in capturing the ship.

 

However if self destruct is gonna be a thing then im somewhat against the idea.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...