Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Yes this is not referring to a specific part, and is not a bug xD

It's just referring to Makeshift parts in general, and in their opinion, as stated.

As visible in the attached screenshot, this Tinkerer says their makeshift parts are "pretty effective for their mass", which implies that the parts are of lower mass but still as/more effective than same-mass non-makeshift parts.
However, one of the parts here is a Mak. Transmission Jammer, which has a higher mass than its same-range counterpart.
The only way it can be considered more effective is with its energy cost, but it still has a higher mass than any other Transmission Jammer.


It's probably normal in some way, but unless i'm being annoying by posting so many of these bug reports i'll keep posting what feels wrong to avoid not reporting an actual bug.

Understandable, although as a part of the line-of-fire visualization rather than extra AOE visualization, it will remain for now.

I mean... explosion predictions are pretty obvious because they have a half-square outline delineating the maximum in each axis direction, which is the more fundamental part of that display--it uses lines in addition to the interior highlight area and not just relying on color like the rest of the targeting interface.

It might be intended to be the more fundamental part of that display, but what i automatically check to see if an explosion will occur is the far more obvious highlighted area. I wouldn't be surprised if that was also the case for a good chunk of players.
At some point, i even saw those explosion range line indicators and thought "wait, were those always there?". I might be good at noticing things generally, but apparently i can tunnel vision when i'm not in "parsing the entire screen for information" mode.

This is allowed. The precise edges of your range are a bit fungible, especially in cases like that because the object on the other side is a prop that occupies its entire cell position and is pushed right up against the edge of whatever's next to it, so if you penetrate you do still hit the side of it (now if it was something smaller that probably wouldn't occur, but there was no distance to travel following the penetration).

As visible in the attached screenshot, i shot the tile directly down-right of the upper Wall Chamber's lower right corner using my Imp. KE Penetrator, which was as far as i could shoot directly up-right diagonally.
This hit the barely out-of range Wall Chamber, which i think is normal? But the projectile penetrated the first tile, which made it travel to the next tile(?) and broke it, which i'm pretty sure breaks the rules of how weapon range works.

I later tried to see if you could hit a stationary hostile by extending the range using this method, but i'm not sure if it worked, as it might have been an Infiltrator i didn't recognize as friendly because of only have an Imp. Signal Interpreter (I hadn't seen Infiltrators yet), who didn't move when i shot them because they weren't 0b10?

Hm, I think this happened once before ages ago and that was fixed, looked like there might be some other source for it. I'll have to add this to the list to check later once I get back to look at Beta 13 stuff (can't load the save right now, working on Beta 14).

I mean... explosion predictions are pretty obvious because they have a half-square outline delineating the maximum in each axis direction, which is the more fundamental part of that display--it uses lines in addition to the interior highlight area and not just relying on color like the rest of the targeting interface.

As visible in the attached screenshot, i can see through it and i can inspect it. However, my shots pass through it, but i can't move into it.
That phase wall is just completely invincible (phase generator excluded).

This happened after i destroyed the Behemoth standing on the four visible phase walls by aiming at the same tile as the bugged phase wall.

I remembered to make a copy of the save file, so it's also attached in case it's useful.

Yeah I'm aware of this behavior, that's how it was built to show you the arc no matter what, since it's helpful to know even if it won't fire, which you'll generally know due to the other differences (in particular the lack of an explosion prediction showing AOE).

Maybe the arcs should be made less obvious, at least when combined with explosives, then? The explosion prediction does get hidden pretty well by the arc if you're not firing at close-range targets. (Though that might be due to my SHIFT_HUE... I'll have to check.)