Search results

The Assailant-class is a fighter-sized design patched together from spare components obtained during raids on fighter construction facilities. It has two dual missile turrets and one small onboard lock-on missile launcher, as well as a very small jump drive, a radar jamming module, and a...

Hoooly crap.

This will indeed take up too much space, and if you use invisible blocks, everyone will ask, "why didn't you just use metadata?" I wouldn't mind this general approach, but virtualized and made into a flowchart-like system within a UI.

Nope, this would break things. Putting light blocks next to logic is done fairly often for status checks, and the logic sometimes goes to other lights...

Just remove velocity dependence, and make it depend strictly on whether or not you are actually firing your thrusters. That way it at least won't look silly.

If swarmers only go for systems, that needs to be fixed. If there are no systems, they should go for other blocks, and if there are none of those they should go for armor.

Music! As for what music... well, depends on what I'm building. Anything from epic/fantasy-type music, to EvE Online's soundtrack.

What's so wrong with letting it run through a few pulses? You could even use that bit of spool-up time to create a cool jump sequence with rails and lights and stuff.

Just use 90% or so, and have the system run a few pulses to jump. 100-1000 activation modules for that system is a bit insane. Remember, all the system has to do is keep charging until it hits around 90%, 95%, or 99%, then stop until someone hits a button, then keep charging until it reaches...

Changing sectors also refreshes the effect checking, IIRC... Not certain, though.

NOR is just NOT(OR); NAND is just NOT(AND)... right? in which case, that wouldn't save much space... XOR would be useful, though.

AHP and SHP can be read, IIRC. I heard somewhere that you link to an AND-gate or an OR-gate... I forget which is which, though. If it's true, this should be changed to linking to an armor block for AHP and to the core for SHP, but oh well. Also, schema , considering the potential for automation...

Shift-V seems a bit bugged in general... I was having issues with randomizers earlier.

Awwww yeah. Awesome update yet again, Schema. Now let's see how fast we break it...

That rule doesn't apply to everything... in a game like this, sometimes changes have to be by small amounts. Especially when what's needed is for the thrusters to just feel a bit more worth it, not to have titans zooming around like frigates or frigates doing aerobatics like fighters... Or, for...

Ew, mud wall.

50% will be way too much. I think the sweet spot will be around 15-20%. If that's not enough, you can continue buffing, but I doubt it'll be necessary.