Search results

Yeah, it's a shame that this will probably be mod-only stuff.

Why not a shield block?

Very nice little turrets. Just a personal preference on the systems, usually I put the thrusters on top and remove them after I dock. It saves a bit of room for more systems.

Hmmm.... I'm not so sure about the private system bit. After all, if everyone is off in their own system, there's limited interaction between members. But without asteroids respawning (planned) you're right about the resource issue. Opinion about "taxes:" I'm going to vote for the faction just...

Reminds me of Gundam Virtue's burst mode a bit. Very shiny.

Docked reactors and turrets should only draw power when they run out of power (that is, they try to do something and they don't have enough power)

Also keep in mind that an image of a planet's surface not only has to have its colors but also lighting information. Well even right now there's a difference between people who have good and bad computers with regards to planets. If the size a derpcomputer can handle goes up, that means the...

So, what happens when I try to build an orbital elevator? Also for the image you may just want to have the image be one pixel per block.

Pizza, that would be Neonstrum, an experimental AI that visits the forums often. I suppose how we allocate bits to orientation/ID should depend on how well they can be optimized. Letting use build/remove blocks that actually have multiple IDs would be trivial. The problem would be that not all...

Because it's way more complex then what we have now. Building the weapon in a seperate environment, having twenty different blocks to make the weapon (from what your suggestion puts out it seems you need at least 6 or 7 modules to make one weapon, where as right now you need only one to make a...

Pics or it didn't happen doesn't work. Also, would it work for this hanger? Which, by the way, has a room almost directly beneath it, so nothing that sticks into the floor too much.

The problem is that not all shapes need 24 orientations. So you wind up wasting space. Having your shapes mixed in with the orientations means you get more bang for your buck.

Oh really?

With your example of having multiple switches for lighting or a door or something, it's honestly best to have all the switches wired together. That lets you toggle from any location.

Or at least have it only check if the center of a block will intersect mothership, not the entire block.

It isn't so much that core-centered docking should be removed as it had annoying limitations. To continue the baking analogy: We had, with the box-based system, poorly made cupcakes. Now, we are getting much better cookies and candy. Some of us see that cupcakes can actually be delicious if...

My reasons I support this? Fighters, shuttles, drones. Sutff <10m will benefit from this. My reasons also include not having ugly spikes all over my landing bay, spikes which also reduce what can be docked there, and not wanting to have spikes on the bottom of my ships. So because a mechanic...

Well, let's say you have three buttons: One on the inside of the ship, one in the airlock, and one outside the ship. You want to be able to switch the door state at all of them. So you would want parity-XOR. But really, it's easier just to chain the switches/buttons together in a lot of cases...

Sven's got the right idea here. "Build a spike" is ugly, still isn't universal for small ships. It's a simple mechanic, and I don't see why people are arguing against it.

Well, it isn't so much an XOR as it is a way to toggle a value whenever a switch is flipped. It's not actually useful for something like reading parity values. Anyway, what is the purpose of 1-only XOR?