Jump to content

Atmosph3rik

Alpha Team Vanguard
  • Posts

    875
  • Joined

  • Last visited

6 Followers

Contact Methods

  • Website URL
    https://twitter.com/Atmosph3rik

Profile Information

  • Gender
    Male
  • Location:
    US
  • backer_title
    Silver Founder
  • Alpha
    Yes

Recent Profile Visitors

2274 profile views

Atmosph3rik's Achievements

  1. My nephew plays Minecraft on his parent's ipad. I don't think DU will run on an ipad... But when he's old enough, i'm sure he'll be tired of Minecraft, like i am, and looking for something new. Personally i hope NQ sticks to their vision, because i think that's why Minecraft was so successful. But if i wanted to play Minecraft, i would just play Minecraft.
  2. To make a copy of the Blueprint, enter Build mode on the construct, and right click "Create Core Blueprint". That will make a new "Core Blueprint" with DRM on. There is also another option to make a Core BP with DRM off. I'm not sure what they mean by "put rights on it" though.
  3. DRM is like copyright protection for the construct. It can be turned on or off by the original creator of the BP. With DRM on, no one except the creator of the BP can make another Blueprint from the construct, or copy voxels from the construct to another core. Blueprints can be made with DRM turned on or off by default when a construct is deployed. So if your Blueprint has DRM off, that means that you will be able to make more BPs from the construct, and copy voxels from it, even if you are not the original creator. If DRM was on, and you were not the original creator, then you can still edit the construct, you just can't copy from it, or duplicate it.
  4. You need the BP and all the materials to be in the same place. Everything in your nanopack, with the nonopack set as primary, or everything in a linked container, with the container set as your primary container.
  5. That is weird. I think you should be able to dock without any permissions if you own both ships. When you try to Dock i think you need to hit ALT-T to initiate the docking. Did you try that?
  6. I haven't done any testing on this myself so i'm just going by what i've heard. But i think it affects the game's performance for anyone near the ship. When a ship has a few hundred engines or adjusters all firing at the same time, all those visual effects at once can't be good for performance. But it would be easy enough for NQ to give us an option to turn those effects off, so there is probably more to it then that. I think the ability to dock cores together to make larger ships is a bit like element stacking. NQ is letting us do it for now, to see how it affects the game. But i wouldn't expect it to work like that forever. It's not giving anyone an unfair advantage, so i wouldn't expect a big crackdown from NQ, but they might change how docking works in the future so it's not possible anymore.
  7. You need to give the pilot permission using the R.D.M.S. (Rights and Duties Management System). There is an in game tutorial that will explain this better then i can here, it is a bit complicated. On the RDMS tab (F7), you need to create a "Policy". Then you need to add an "Actor", that is the pilot you want to give permission to. Then add a "Right" to the policy, "Dock Construct". And finally you need to add a "Tag" to the policy, and then Save & Close the tab. And then you will need to add that same Tag to the construct by right clicking the construct, Construct > Advanced > Set Construct rights, and find the Tag you created in the dropdown list and add it, then Save and Close. You might need to log out and back in for the Policy to take effect also.
  8. Unless something changed with the last update, we've always been able to dock multiple cores together to build larger ships. The real limitation on ship size is elements. You can only use so many of them before it starts to affect performance. So until NQ gives us larger more powerful elements, there's not much point in building larger ships. But you can.
  9. referring to yourself as "the community" is kinda weird.
  10. Any element placement that requires an exploit is not allowed. Seems pretty straight forward to me. All that matters is how you were able to achieve S2. If S2 requires an exploit, then it's an exploit. If it doesn't, then it's not. Currently there is only S0 and S1. Anything else requires an exploit. Honestly i think the word stacking is making this whole thing harder for people to understand. Forget about stacking. There is element placement that doesn't require an exploit, and element placement that does. That's it.
  11. One or two engines wouldn't be the max though, it would be the middle, or balanced. I'm over simplifying how this would work hopefully, but imagine each type of element needed one unit of power to function, and you had something like 14 units available on your core. two for atmo engines, two for space engines, lift, brakes, shields, storage and weapons. So if you don't need weapons, you've got two more points to spend somewhere else. That would still allow you to totally ignore PVP, or hauling, or build a ship that's space or atmo only, and dedicate all that power somewhere else. Hopefully it would be a lot more interesting then that, with different tiers of elements requiring different amounts of power, higher tier cores with higher power output maybe. But the goal would be that if you want your ship to be above average in one area, you have to give something up in another area, like you said. The docking thing could be a problem. But i don't think docking was really intended to be used to tow another ship that's the same size/mass. Maybe docking should disengage if the docked ship weighs too much compared to the parent ship, or something like that. Although that's the only way people are able to build larger ships right now, so if they changed that hopefully they give us XL cores too.
  12. You have to right click the core element itself and there's an option to enable/disable DRM. Turning DRM on or off only applies to that individual construct also. When you create a Blueprint by default it should make a construct with DRM enabled, and only the creator can disable it. There's also an option to create a DRM free Blueprint that will create a construct with DRM off by default. At least that was how it was supposed to work when they introduced it. Who knows now i guess 😕
  13. From the perspective of a ship builder, @EpicPhail is right. A lot of people were using element stacking to build ships that looked good, but could still haul the most weight possible. There were other reasons people were using element stacking too. But all you have to do is read the OP to see that isn't the topic. So in my opinion the first thing NQ needs to do is decide how much thrust, lift, brakes ect they want each core size to be able to handle. Then they need to make the elements powerful enough that you only need one or two of each type of element to reach that level. Because having a thousand elements is bad for performance and it looks like crap. Then they need a new way of limiting the number of functional elements that we can put on a ship. Something like a power management system that makes you choose where you want to use power, instead of simply deciding how much power you want to pile on. Hopefully NQ is already working on it. And if they aren't, hopefully this whole element stacking thing makes them realize that we need it.
  14. Except they're right. There's two totally separate issues here but your so caught up on the idea that someone might have gotten more stuff then you, that your just having your own little argument against element stacking and ignoring everything else. Stacking was an exploit and it needed to be fixed. Literally no one is disputing that. Stacking was giving people an unfair advantage in PVP. Stacking was also an easy way around the fact that the only method of balancing how many functional elements can fit on one ship is the choice to sacrifice aesthetic appeal. When building a ship you have to choose between a ship that looks good, or ship that can compete with other ships in terms of functionality. That's a terrible way of balancing it. and stacking wouldn't have been nearly as prevalent if that wasn't the case. Stacking was an exploit, but it was also a symptom of the fact that they need a better method of balancing power. See how the one topic leads into the other one? if you actually read the words. So do you think we could all go back to the other thread and have a nice discussion about engine buffs and power management now, without all the derailing?
  15. This is the same idea from the other thread that you've posted in like 5 times arguing against it though lol It's too bad you worked so hard to derail that thread or we could have had a nice discussion about the idea.
×
×
  • Create New...