Jump to content

Search the Community

Showing results for tags 'carriers'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Starting Zone
    • Rules & Announcements
    • The Arkship Pub
    • Novark's Organization Registry
    • General Discussions
    • Off Topic Discussions
  • Ideas & Gameplay discussions
    • Idea Box
    • The Builder's Corner
    • The Gameplay Mechanics Assembly
    • DevBlog Feedback
  • Fan Art, Fan Fictions & Roleplay
    • Novark Agora
    • Novark Archives
    • Novark Art Gallery

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location:


Interests


backer_title


Alpha


community_id

Found 2 results

  1. My first thought when I heard about the way they intend the single shard system to work with ship building and player density was "Well what happens if one person builds like 500 tiny ships and puts them in the same valley, free to tumble around and take up valuable server resources?" Another thing I realized once I had heard more about the way they intended the PvP system to work was that people could probably dock other "ships" to them that would function as extra fuel tanks, more armor, or even a shield if done correctly with dozens of tiny "ships" being flung towards an enemy to block line of sight. For these reasons, and more, I believe that there should be a limit to how many dynamic constructs a person can have operational at any time, based on a skill system. Not doing this would allow people to easily lag the server with hundreds of small ships bumping into things, and could also create some interesting but likely laggy pvp strategies. Perhaps a person could simply "deactivate" a ship they weren't using by turning it into a static construct, which is not subject to physics on the same level. But this also brings up something else, which is how far NQ will go with implementing carriers. Obviously if that is something feasible (it could already be in the game, I have no idea) they would want to do it, but what exactly would be able to be shared across 2 connected ships? I think that should be limited to fuel, storage, and whatever power system is added/is in the game. Allowing for a script on the mothership to control features on a docked ship would definitely be too far imo, but what do you guys think?
  2. I'm not sure how the current system works, but in my opinion there should be a way to shift a dynamic construct into a static construct, and back again. To avoid glitches it should only allow you to change if you are not touching any construct (with the exception of docking/being docked, something else I know very little about as far as mechanics). If turning a dynamic construct into a static construct, a period of "anchoring" where the ship goes offline and must be defended for a certain amount of time will occur to avoid people instantly changing their ships to static or dynamic during combat. Assuming this isn't already in the game, adding this would allow for mobile asteroid mining facilities or forward operating bases during the siege of a planet or system. Please comment your thoughts or suggestions, as i'm interested to see what you all think.
×
×
  • Create New...