Search results

Oh, thought you were referring to the second one.

No, you can't. All the module groups have to be the same exact size and shape. So that won't work.

[ADD] and [REPLACEFIRST] use the stored string data, too, last time I checked, not the output string rendered on the display block.

Basically, the way the game works, the actual ship metadata just stores [sector] or [powerAux] or [docked] or whatever; there is a separate part of the code that replaces those tags with whatever quantity (or string-from-boolean) they reference on the server. Sensors compare the metadata text.

You cannot do it, period. What gets compared is, for instance, "[sector]" and "2, 2, 2", not "5, 4, 2" and "2, 2, 2".

There IS no unloaded mining. Wherever did it say that was possible, especially when unloaded combat is still unimplemented, and Schema explicitly stated that unloaded combat/mining/etc. are the next stage of fleet mechanics - presumably coming next update.

Forgot to mention, though, that I LOVE the look of the new doors, logic, and ingots. Much better.

Hm, to be honest, the more I look at these textures, the more I prefer the old ones. The improvements to lackluster textures are great, but the rounded, almost toylike aesthetic on things like computers, pipes, decorative server racks, and the other decorative 'tech' blocks... feel like a step...

As the Aethi are now a member of the Union of Intergalactic States, we are allies by default.

A sphere might actually create less CPU strain. All you have to do is keep track of how far the bullet is from the player, and if it comes within a certain distance it would be absorbed by the shield.

Not sure about this (the calculations involved would be strange) but the larger the boarding ship is compared to the ship it's grappling to, the easier it should be to shake it off.

The telephone poles could backfire, if someone manages to stick their ship on top of them. Anyone trying to hop out the airlock and shoot at the boarders would find himself rather... deprived of good firing angles.

For basic functions, you don't really need to know much regex. For instance, if you want a docking status thing: [REPLACEALL]Docking Port 1: Open[WITH]Docking Port 1: Closed Second display module: [REPLACEALL]Docking Port 1: Closed[WITH]Docking Port 1: Open

The code for +/- nojumpthrough would be the same code needed for the extension to warp inhibitor functionality that people are asking for... It'd be nice.

I agree with the sentiment, if not the idea... Shields right now are annoying, though IDK how to fix that, because using shields as a primary defense should be a viable option but right now they're just... ugh. I guess a bleedthrough mechanic might work?

Yes, because usually the other party doesn't believe them.

Added a bunch of stuff that needed to be in the original post. As for all this talk about requirements for the station to actually drain points in the first place, some sort of "command module" system that would have to be put on stations might work. It'd have to be fairly expensive, and...

Added tons of new display block variables: [name], [sector], [system], [mass], block count, structure/armor HP, and more - not functional as of yesterday(Oct 10 '16)'s dev build Added regex features for the logic/display block interaction; see the help window in the display block edit dialog for...

Ah, right... Stockpiling faction points is already a balance issue; I don't really know how to solve that one, but it can throw a monkey wrench into all but the most intrusive and annoying proposals to try and make faction points work. That'll take some more thinking and figuring-out.