Search results

I can see a few venues. My favorite is probably to make docked reactors part of the game proper. Add some sort of block or system to isolate volumes of a ship. Isolated volumes have their own softcaps, but power regen is the only stat to transfer to the rest of the ship. A few limitations, say...

Excellent. Another suggestion for semi-programming, where I can interject- Please do this, in addition to regular, good old-fashioned Lua scripting. Seriously. Everything we can do with logic, or drag-and-drop AI, or any other control mechanism can be done many times better if everything is in...

For the record, what makes KSP the game it is is not fuel. It's fuel with weight. If storage doesn't add much mass or resource usage, you won't get any of the same effect. As for the suggestion itself... it's certainly better than average. To some extent, it suffers from the same problem as...

While perhaps the system itself has merit, there's the inevitable fact of game design that you simply cannot restrict communication. Communication happens between people playing the game, it is not part of the game. There's plenty of services for communicating between people, the game just...

Hmm. On one hand, I like this. On the other, I think this is just one of many symptoms of too hard-coded interfaces and lacking integration between entities, and I'd like to see that issue tackled at it's roots rather than patched on a case-by-case basis. A more universal mechanic for connecting...

If I may abstain from the excessive capitalization that's thus far been practiced- Quite wonderful!

I'm slightly concerned about the way you describe these re-dockong rails. The concept itself is quite reasonable- remove the need for pathfinding by letting players pre-define paths. However, you describe these rails as not just navigational paths, but as actual rails the ships will move along...

I'm not inclined to support a solution that ultimately buffs docked reactors, even if it's pretty marginal. And really, this issue is a technical one, the solution shouldn't infringe on the game mechanics themselves. Making them clip until they're clear of the mothership seems like a more...

And a room with automated showers of astrotech beams isn't the most awesome med bay one can imagine? Crew systems wouldn't suffer from that, even in the absence of a specific med-bay block, players could designate the area themselves and have the NPCs take their word for it.

A minor point- The Lua home page specifically asks people not to spell it LUA, but Lua. It's a name, not an acronym. I agree it should be implemented in-game, though. If anything, because it would solve such a ridiculous amount of problems by allowing players to implement features themselves...

As I said, I'm so sure about the idea itself. Particularly, it somewhat requires gates to be as static as they are now, which I disagree with.

That could potentially be handled with abstraction, everything in the unloaded sectors being simplified as non-physical entities with certain amounts of shield, power and regen to send over, based on the last known stats. I'm not so sure about the idea itself, but the technicalities sound...

The McKay/Carter intergalactic bridge was, you'll notice, a creative use of an otherwise limited tool. I certainly like the idea more than most, far preferring it over the extended range most servers use as a cheap bypass, but it should certainly be the same as in Stargate- a potential use of...

Tracking how many projectiles have been fired in the last second or so shouldn't be difficult, nor should a ship-wide weapons power debuff scaling with that quantity be.

While sensible in the short term, that reasoning is very problematic. Arbitrary limits on the interface are not a sustainable means of balancing the game. It's specific to the way mechanics work at present, precludes any in-game moddability or programmablity to ship controls, and overall...

There's no significant difference between "Metadata" and block bits, it's all ram in the end. If anything, metadata should be far less efficient data storage when used for so many blocks at once. I have suggested a variation of this- one piece of metadata for every ship, which re-defines the...

C/V-ing a couple of factories to a shipyard block is complicated now? Really though, specific functionality is a bad thing. We can't go around fixing everything with a mechanic of it's own. This game is supposed to be a sandbox, not a list of specialized mechanics, each allowing one specific...

The primary suggestion, shipyards eating resources directly, I must oppose as automagical. Shipyards are for building, factories are for manufacturing. While it would be somewhat balanced resource-wise if there was some inefficiency, it would still blur the lines of functionality in the game...