Search results

TL:DR Shields bad. They turn complex destruction system into dumb HP bar. So far nobody presented a shield idea that would be any better (and we had quite a few of them). IMO good way to make large ship slightly more viable overall would be change to ship drag equation. Basically allow bigger...

Yes. Kind of sensor that tells whom you're looking at. But just for identyfikator, rather than detection, as you need to point a beam at the ship. But! It would still work with transponders, even when they're turned off. If there is no transponder at all, your incognito (and probably considered...

To be more precise: thruster attached to hardpoint attached to valid frame (at least 3 beams welded together) allows you to use thrusters. But for being a valid ship, with ownership, spawning/despawning rights, hosting and longevity it needs to be either bought from SSC or from ship shops. I.e...

No, it's completely optional (at least for now). And even if you have it, you can just turn it off. There were some hints that they may be connected to ship ownership in the future. But nothing certain

To ad onto that, transponders could use some simple IFF colouring. Green-group Blue-company Pink-devs Just like player characters

Endo "armour" is, and will probably remain, purely cosmetic.

Yes, you can build as large as you want. But the moment you go over limits, thrusters will refuse to work, so your ship will become stationary. This applies to all the part/voxel limits, but not to dimension limits. So 1km long stick can be a valid ship

Nit much. But we're in alpha, so they focus on bugs and new features, not balance.

Lag happens, but last two events were surprisingly smooth for me. Only people jumping around were those with really bad connection. Those were ~50 people ffa battles, with over 500 wrecked ships on the battlefield. And Im playing on shitty mobile data connection via my phone tethering hotspot...

There is quite noticeable splash when you hit someone, and sound when you get hit. But yolol can't hear any of that. There is a way to check if module has been destroyed. If you try to access it's device field when it's cut off, it'll skip the rest of the line. I.e. :Thruster1Status=0...

Part is i.e. 96x96x12cm square plate. Or 144x288x12cm. Thruster is made of 5 parts each, ect. Current system: Each part has "armour" value, which is equal to volume x material property. When part get hit, projectile energy is compared with armour. If it's higher, it deals voxel damage. Either...

Maybe I phrased that wrong. "All or nothing" as in armouring just the important bits, and leaving everything else much less protected will always work. I meant "there should be more valid in-between choices than frontal main battle tank armour and thin aluminium sheet" Thrusters would be weak...

@Musclethorpe By Okim:

Current armour system is indeed broken. Mostly because it works with per-part hp, rather than per-voxel. It makes big plates much better than small ones, which naturally encourage building flying bricks. IMO we need simple per-voxel armour model. With each weapon removing always the same amount...

Afaik it's not "better takes over worse", but more "potato connection can't just lag-teleport all over the place" So if your connection is "good enough", nobody will steal hosting your ship, even if they live in a basement under FB server room.

There's at least one project started doing that, that I know about. And yes, it's punching. But those punches can break weaker objects in a single hit. I.e. active fuel rods...

Carriers (single pilot for multiple ships and people) + ship-based SSC. And no travel is too long! Also ability to transport offline people (bodies should stay in universe outside stations!) And switching bodies at will (i.e. between different stations). Those would remove wait, at least for...

I agree with non-chippable armour idea. But not through some magic shields. Instead bullets should make small holes in armour, and leave rest of the plate intact and functional. So you'd want to either take slow-firing weapon that will penetrate it, or high rof and aim for unarmoured ships or...

And here's a code that saves or loads up to 9x4 field values (GPS coords). You switch between "slots" with prev/next buttons. Save button saves clipboard values to storage (or device). Load button loads values from storage/device. :Nn+=(:Next-:Prev) :Nn+=:NMax*((:Nn<1)-(:Nn>:NMax)) goto...

IMO there's no chance we'll ever get faster than 150m/s and still being able to collide into anything. Due to performance and latency reasons. So either being close to belt/station/other ships will drop out of warp automatically, or there simply won't be any warp drive.