Lachenlaud

That practice would work poorly against a highly coordinated universal body. No Leaders per se, just concensus. Any group that stands in solidarity with a universal governing belief might prove a challenge. Edit: The other thing I would caution against in practice is this, never doubt for a moment that the smaller group you choose to target -may- be supported or protect by a Much larger one.

They had me up to that part... I much prefer defenestration.

Yep and I wouldn't be surprised if you actually either a) rez to the 'nearest' one or b) are given a menu to 'select rez node to rez to'

We can hope.

Oh ye of little faith.... haven't you ever heard the expression.... "If you build it, they will come?" You don't truly believe that just means customers do you? It's not a matter of 'can' or 'will'.... it's just a matter of 'when' it will happen. And it will. You'll run into one of three situations; Give us your stuff and die. Give us your stuff and work for us or die. Die so we can take your stuff (cuz we just can't resist taking your stuff after you're dead!)

Pew Pew Pods? Truly I am hoping that weapons systems don't have much in the way of automated targeting and that they are more reliant on People than in most games, or at least are more efficient when Not in an automated configuration.

I see what you are saying. You want to store revision information. A blueprint comparator, so to speak. I like the concept and would be fully supportive of such a thing. Being able to store itterative information within the Blueprint would be a great idea. I would also like the ability to 'swap' ingredients for materials, if not elements, out of a blueprint. (for instance if its made from blue plastic, let me substitute red, etc.) Or, if I go to spawn a blueprint for which I don't have all the materials, allow me to spawn it anyhow with a warning that missing parts/materials will have to be added manually afterward.

The bottom line is that Resurection Nodes are supposed to be just that..... You die you end up there. We can't die right now because we can't be hurt. BUT.... The whole concept of 'Force Respawn' right now is an immediate teleport, inventory and all. If the mechanic works as I believe it will in the future, Force Respawn may as well be named 'Suicide to Clone' because when you die all your stuff is going to be with your 'body' and it can be looted. If that were the case now, how many of us would 'Suicide to Clone' leaving all our stuff behind with our Body? It is the way it is only for testing purposes and as a QoL feature that is quite likely Very Temporary. ~pictures a landscape of dead DU citizens scattered about~ Oooh... piece of candy... wonder whats on THIS corpse.....

I use a simple methodology for BP's to distinguish variants. Version Numbers. [TAG] (S/D|XL|L|M|S|XS) BPName v0.1 Tag is Corp Tag, in my case [GOI] for Golden Oak Industries. An S or a D to indicate Core Type, and a size designation. If I have a ship that is called the Explorer on an XS Dynamic Core the example would be; GOI DXS Explorer v0.1 Any time I make a 'change' to the ship that warrants remaking the BP I update the value; GOI DXS Explorer 0.2 This way I always -know- what the current iteration is. If you rename your construct prior to each BP, you're set.

I find it amazing. The original Yama-BOT doesn't take any 'personal' information. It grabs a key posted on your PUBLIC DU Forum Profile and grabs the fact that you are or are not alpha authorized (also public) so that the discord unlocks a few channels by giving you a tag. (And NQ has SEEN his code which is good enough for ME... I've been coding for over 30 years.) It simply can't do anything else, it can't grab your Discord PW, it can't grab your forum PW. It's secure. It's safe. Whether @yamamushi made/makes the code for the bot public or not is moot. The same would essentially apply to the author of this bot. Please, don't take MY word for it. Go learn how to make one on your own, and if you've the ability to do so, you'll see I'm right. I get the reservations from those that don't understand the 'magic' behind the scenes. That's fine... don't use it, but don't speak badly from ignorance or being uninformed... unless your intent is to merely troll the post (and in a civilized society that would be the ONLY reason ANYONE would do so... cuz they'ze ig-nant), in which case you can just go <insert your choice of nasty self-inflicted idiocy here.> I give you the following URL to discover for yourselves just how makeing a bot is done; How to make your own Discord BOT Have a cookie... 🍪 'nuff said!

Only if we can add a spacesuit to them along with an engine or two...

I wouldn't count out the possibility of it. We're a long way from release and docked ships will in all probability (I hope) be possible then. If you can remote control the larger vessel it might be possible to leave in the smaller vessel in a pinch (i.e. shuttle/pod/whatever) Though I don't know how far you could fly from the mother ship and still control it from the pod.

@NQ-Nyzaltar @NQ-Entropy You guys need to add a scroll bar to the talent page to get down to a larger view of the queue - it is very difficult as it is to re-prioritize talents as of the last iteration of the menu, and if you are adding more talents and taking more space away from the queue itself it is going to be virtually impossible. (Example attached)

Frankly having the game be a flat fee inclusive of some type of cash shop for elements and other accessories would drive me away from this particular game only because of the fact that the developers would be spending all of their time developing more crap for players to buy in order to maintain their income and to have the funds to continue developing more crap for players to buy it is a ridiculous model and one that the industry as a whole should be ashamed of. Whole thing is a vicious circle and makes for poor player interaction and poor support because quite frankly it's designed to be a cash cow.