[Fixed] Lineblocking: BLOCK_EVERYTHING doesn't block ever...

Bugs that have been investigated and resolved somehow.

Moderator: GZDoom Developers

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
kn

Lineblocking: BLOCK_EVERYTHING doesn't block everything?

Post by kn »

I've got a problem with BLOCK_EVERYTHING on lines:

When I set up a line (e.g. creating a glass wall) to block everything, projectiles are blocked, but when standing close to this wall, the player still gets hurt and dies by rocket explosions or scratching enemys.

Bug?
User avatar
Ultraviolet
Posts: 1152
Joined: Tue Jul 15, 2003 9:08 pm
Location: PROJECT DETAILS CLASSIFIED.

Post by Ultraviolet »

You could put in a buffer-sector (will keep the player from getting close enough to get scratched, but the rocket explosions will still be an issue) as a temporary fix, if you'd like. If there's trouble tracking this one down you might want to just settle for a quick fix like that.
User avatar
HotWax
Posts: 10002
Joined: Fri Jul 18, 2003 6:18 pm
Location: Idaho Falls, ID

Post by HotWax »

Erm... All blocking lines, whatever they block, block ACTORS (Enemies, player, projectiles). They are NOT used when determining whether an enemy is close enough to scratch you, and are NOT used when calculating explosion radiuses. This is not a bug, it's a feature.
User avatar
Xaser
 
 
Posts: 10772
Joined: Sun Jul 20, 2003 12:15 pm

Post by Xaser »

Yeah, the 3 things that can go through Block Everything lines are:
1: Close range attacks
2: Rocket explosions
3: Arch-vile attack.
AFAIK, there's no real way to prevent this, except the buffer sector.
User avatar
Hirogen2
Posts: 2033
Joined: Sat Jul 19, 2003 6:15 am
Operating System Version (Optional): Tumbleweed x64
Graphics Processor: Intel with Vulkan/Metal Support
Location: Central Germany

Post by Hirogen2 »

Xaser wrote:Yeah, the 3 things that can go through Block Everything lines are:
1: Close range attacks
2: Rocket explosions
3: Arch-vile attack.
AFAIK, there's no real way to prevent this, except the buffer sector.
4. possibly BFG blasts (not the shot, but... you know)
Cyb
Posts: 912
Joined: Tue Jul 15, 2003 5:12 pm

Post by Cyb »

Xaser wrote:Yeah, the 3 things that can go through Block Everything lines are:
1: Close range attacks
2: Rocket explosions
3: Arch-vile attack.
AFAIK, there's no real way to prevent this, except the buffer sector.
yes, and the bfg cone, that's because those attacks are not actors but based on a radius or the position of another actor and in the case of melee attacks damage is applied directly to the target as long as it is within range.

actually now that I think about it, block_everything lines also don't block the railgun, which probably is a bug but I dunno?
User avatar
Xaser
 
 
Posts: 10772
Joined: Sun Jul 20, 2003 12:15 pm

Post by Xaser »

Cyb wrote:actually now that I think about it, block_everything lines also don't block the railgun, which probably is a bug but I dunno?
Okay, I think that's a bug. There's no way to prevent the other 4 (close attacks, explosions, vile attack, and bfg cone) from going through, but the railgun should be stopped. The Block_everything can stop bullets, why not railgun shots?
Guest

Post by Guest »

Ultraviolet wrote:You could put in a buffer-sector (will keep the player from getting close enough to get scratched, but the rocket explosions will still be an issue) as a temporary fix, if you'd like. If there's trouble tracking this one down you might want to just settle for a quick fix like that.
Yeah,already did that before, but to prevent DBCR (death by cyberdemon rocket :wink: ) the buffer sector has to be 128 units, which is too big :cry:
kn

Post by kn »

HotWax wrote:Erm... All blocking lines, whatever they block, block ACTORS (Enemies, player, projectiles). They are NOT used when determining whether an enemy is close enough to scratch you, and are NOT used when calculating explosion radiuses. This is not a bug, it's a feature.
If it is a feature, I don't like it. When standing behind a glass wall, logic provides that a player can't be scratched. Well, I guess I need a new
option:

SetLineBlocking(lineid,BLOCK_ABSOLUTELY_EVERYTHING);

<g>
User avatar
randi
Site Admin
Posts: 7746
Joined: Wed Jul 09, 2003 10:30 pm

Re: Lineblocking: BLOCK_EVERYTHING doesn't block everything?

Post by randi »

kn wrote:Bug?
Probably. I wasn't thinking of those cases when I added it, but it makes sense that they should be blocked.
User avatar
Xaser
 
 
Posts: 10772
Joined: Sun Jul 20, 2003 12:15 pm

Post by Xaser »

You could probably change it to make it behave just like it was a regular wall. This will stop the Railgun shots, archvile attack, close range attacks, and BFG cone, though the radius damage from pockets will still come through (I think).
User avatar
kn
Posts: 28
Joined: Wed Jul 30, 2003 4:45 pm
Location: NRW

Re: Lineblocking: BLOCK_EVERYTHING doesn't block everything?

Post by kn »

randy wrote:
kn wrote:Bug?
Probably. I wasn't thinking of those cases when I added it, but it makes sense that they should be blocked.
Hm, now I just added a few fences and now scratching / explosion damage make sense again. Guess we need both types. :?
User avatar
Ultraviolet
Posts: 1152
Joined: Tue Jul 15, 2003 9:08 pm
Location: PROJECT DETAILS CLASSIFIED.

Post by Ultraviolet »

To make it so that "block everything" blocks a monster's line of sight as well would fix all that because if they can't see you they can't attack you, but the player would still be able to see the monster... unfair advantage.
User avatar
HotWax
Posts: 10002
Joined: Fri Jul 18, 2003 6:18 pm
Location: Idaho Falls, ID

Post by HotWax »

Ultraviolet wrote:To make it so that "block everything" blocks a monster's line of sight as well would fix all that because if they can't see you they can't attack you, but the player would still be able to see the monster... unfair advantage.
Changing the way the line type works in this manner would break compatibility with older ZDoom wads. If you want linetypes that are similar but do different things, ask for a completely new type or an argument (OFF by default) that would modify the given type.

Also, you can already achieve invisible walls that block monster sight (as well as everything else), so there's really no need.
User avatar
Ultraviolet
Posts: 1152
Joined: Tue Jul 15, 2003 9:08 pm
Location: PROJECT DETAILS CLASSIFIED.

Post by Ultraviolet »

Well, what I was talking about is wanting a way to get an invisible wall that does NOT block monster sight, but can't be attacked through and blocks splash damage.

Return to “Closed Bugs [GZDoom]”