Does just the corner of a border provide cover?


Rules Questions

51 to 78 of 78 << first < prev | 1 | 2 | next > last >>

Yeah, he was looking to see if cover was applied for a caster. But I see the confusion.


Komoda wrote:


As a line has no thickness, it cannot overlap. It can only cross or not cross. It cannot do both. It is impossible.

Your own quote contradicts the graphs you created. A line has no thickness yet you're trying to use the thickness of the pixels to try and prove your point.

If the pixels were infinitesimally thin like they should be, then you still get the contradiction between the 2 situations. A thick line such as dental floss used to draw the line on an actual battle map will definitely cross a wall or corner since it "spreads" on both sides of the line it is supposed to represent, not just one side as in your graph.


Komoda wrote:
As a line has no thickness, it cannot overlap. It can only cross or not cross. It cannot do both. It is impossible.

I would disagree. Imagine a cartesian coordinate system, and two line segments:

(0,0)-(0,1)
(0,0)-(0,2)

The first line is on exactly the same points as the first half of the second, and they overlap.

As to your grid graphic: I think you have a really good idea here, which I quite like, which is that we draw the lines, but instead of looking at whether the lines themselves intersect things which would block you, we look at the space described by those lines. That is a really excellent solution to the problem -- it gets the right results in all the obvious cases.

I don't think it is the rules as-written, but I think it achieves what they almost certainly intend.


Pathfinder Roleplaying Game Superscriber; Pathfinder Starfinder Roleplaying Game Subscriber

Just figured out what happened. I meant to put my diagram in THIS THREAD.


seebs wrote:
I don't think it is the rules as-written, but I think it achieves what they almost certainly intend.

It does seem to solve some issues, but I think the following one might still be iffy.

A0
WF

A=Archer, 0=Open, W=Wall, F=Fighter

If we go by enclosed area, then the archer has cover relative to the fighter, but fighter would have no cover relative to the archer!

I don't think this would pass the smell test for me personally at least.


Celanian wrote:
seebs wrote:
I don't think it is the rules as-written, but I think it achieves what they almost certainly intend.

It does seem to solve some issues, but I think the following one might still be iffy.

A0
WF

A=Archer, 0=Open, W=Wall, F=Fighter

If we go by enclosed area, then the archer has cover relative to the fighter, but fighter would have no cover relative to the archer!

I don't think this would pass the smell test for me personally at least.

It's far easier to lean around a corner and fire an arrow than it is to swing your sword through a wall. I'd say that situation seems pretty alright to me.


Xenrac wrote:
Celanian wrote:
seebs wrote:
I don't think it is the rules as-written, but I think it achieves what they almost certainly intend.

It does seem to solve some issues, but I think the following one might still be iffy.

A0
WF

A=Archer, 0=Open, W=Wall, F=Fighter

If we go by enclosed area, then the archer has cover relative to the fighter, but fighter would have no cover relative to the archer!

I don't think this would pass the smell test for me personally at least.

It's far easier to lean around a corner and fire an arrow than it is to swing your sword through a wall. I'd say that situation seems pretty alright to me.

Heh, not with the fighter in your face. This one is actually very easy to test. Get a buddy and have one of you use a fake sword and the other use a fake bow and stand at a corner. I guarantee that the guy with the sword will have a much easier time hitting the bow user than the other way around.

Sczarni

Not in Pathfinder, though. Actually, the fighter wouldn't even get an attack of opportunity because the bow user has cover from him.

Liberty's Edge

Celanian wrote:
seebs wrote:
I don't think it is the rules as-written, but I think it achieves what they almost certainly intend.

It does seem to solve some issues, but I think the following one might still be iffy.

A0
WF

A=Archer, 0=Open, W=Wall, F=Fighter

If we go by enclosed area, then the archer has cover relative to the fighter, but fighter would have no cover relative to the archer!

Yep. And not only by the enclosed area diagram (nice too, btw), but also by the written text, unless you see tracing a ranged cover line down the wall itself to be something that provides cover.

I don't think this would pass the smell test for me personally at least.

Ranged combat and melee combat don't use the same standard. Arrow slits come to mind.

Liberty's Edge

Celanian wrote:
seebs wrote:
I don't think it is the rules as-written, but I think it achieves what they almost certainly intend.

It does seem to solve some issues, but I think the following one might still be iffy.

A0
WF

A=Archer, 0=Open, W=Wall, F=Fighter

If we go by enclosed area, then the archer has cover relative to the fighter, but fighter would have no cover relative to the archer!

I don't think this would pass the smell test for me personally at least.

What Celanian said makes sense to me. In real life, I would much rather be the fighter swinging the sword at the adjacent guy around the corner instead of the archer firing at the adjacent guy around the corner. The archer is just asking to loose an arm.

Paizo decided to determine cover for adjacent melee attackers and adjacent range attackers differently, but I don't think they took into account adjacent ranged attackers.

In my mind, it would make more sense that ranged attackers that are adjacent to their target would determine cover in the same was as melee attackers that are adjacent to their target.


It makes sense to me in that the Archer is able to shoot around the corner. Due to the corner to target sighting (which makes sense to me) that negates the fighter's cover. However, when it is the fighter's turn the Fighter has to try to hit the Archer while he is taking cover.

- Gauss

Liberty's Edge

Yeah, but as you know, the fighter and the archer are really trying to kill each other at the same time. There is actually a lot more going on than you swing, I swing, you swing, etc.


1 person marked this as a favorite.

RedDogMT, you are correct they are trying to 'kill each other at the same time'. But at the same time that might still involve a lot of dodging, thrusts, parries, and all the stuff the game only halfway mentions if at all.

I can easily see the fighter swinging and the archer dodging behind the corner then popping out to shoot.

However, Pathfinder is not really a simulation and trying to interpret it as one invariably shows why it is not. Making sense of the rules in real life terms will often cause them to fail to make sense.

Thus, I deal with the rules as a set of rules and not an attempt to model reality in the form of a game.

- Gauss

Liberty's Edge

Hey Gauss. You have one of the more grounded voices on these boards and I respect that. I think we have differing opinions.

I do agree that the rules of the game cannot mimic reality, but they do try to represent reality to a certain extent.

I just think that the archer would be at more of a disadvantage than the sword-wielding fighter in this situation, but the game rules do not currently reflect that.

Sczarni

For 6 seconds the archer has the advantage. Then the Fighter 5 foot steps around the corner, sunders the archer's bow, and starts collecting the ingredients for a meat pie.


seebs wrote:
Komoda wrote:
As a line has no thickness, it cannot overlap. It can only cross or not cross. It cannot do both. It is impossible.

I would disagree. Imagine a cartesian coordinate system, and two line segments:

(0,0)-(0,1)
(0,0)-(0,2)

The first line is on exactly the same points as the first half of the second, and they overlap.

As to your grid graphic: I think you have a really good idea here, which I quite like, which is that we draw the lines, but instead of looking at whether the lines themselves intersect things which would block you, we look at the space described by those lines. That is a really excellent solution to the problem -- it gets the right results in all the obvious cases.

I don't think it is the rules as-written, but I think it achieves what they almost certainly intend.

For something to overlap it must have surface area. A line has no second dimension. It has no surface area. It cannot overlap.

The lines in your example cross at (0,0). This fits with my statement that lines cannot overlap only cross or not cross.

And before it comes up, the line segments (0,2)-(0,3) and (0,1)-(0,4) also do not overlap, they are from the same line.

The shaded are doesn't count as RAW, and isn't really need to check for cover. My point of showing it was to show how the same line can show cover or no cover, as in grid two.

There is not a yellow line and a blue line, there is an invisible line between them. One side provides cover, the other does not.

It only matters because we are getting into the nitty picky area of the game. This level of precision is not required. But I assure you, the math proves that the original situation does not provide cover.


Celanian wrote:
Komoda wrote:


As a line has no thickness, it cannot overlap. It can only cross or not cross. It cannot do both. It is impossible.

Your own quote contradicts the graphs you created. A line has no thickness yet you're trying to use the thickness of the pixels to try and prove your point.

If the pixels were infinitesimally thin like they should be, then you still get the contradiction between the 2 situations. A thick line such as dental floss used to draw the line on an actual battle map will definitely cross a wall or corner since it "spreads" on both sides of the line it is supposed to represent, not just one side as in your graph.

You do know that it impossible to draw a one dimensional line, right? It can only be depicted as an edge. If you look at the black pixels in the zoomed in section of grid-1, the left/lower edge of those pixels is the only way to "see" the line.

The line is between the yellow shaded area and the non-shaded area in grid 1
In grid 2 it is between the yellow shaded area and the blue shaded area.

In the 3D depiction that you describe, you are correct about the dental floss. On a battlemat, that would represent about 1/4" in the game world. Do you really think that the limits of the 3D representation that only shows a 1/4" pebble that does not exist in the actual 1D theory used, should really provide a 20% penalty to the attack roll?


Komoda wrote:
Celanian wrote:
Komoda wrote:


As a line has no thickness, it cannot overlap. It can only cross or not cross. It cannot do both. It is impossible.

Your own quote contradicts the graphs you created. A line has no thickness yet you're trying to use the thickness of the pixels to try and prove your point.

If the pixels were infinitesimally thin like they should be, then you still get the contradiction between the 2 situations. A thick line such as dental floss used to draw the line on an actual battle map will definitely cross a wall or corner since it "spreads" on both sides of the line it is supposed to represent, not just one side as in your graph.

You do know that it impossible to draw a one dimensional line, right? It can only be depicted as an edge. If you look at the black pixels in the zoomed in section of grid-1, the left/lower edge of those pixels is the only way to "see" the line.

The line is between the yellow shaded area and the non-shaded area in grid 1
In grid 2 it is between the yellow shaded area and the blue shaded area.

In the 3D depiction that you describe, you are correct about the dental floss. On a battlemat, that would represent about 1/4" in the game world. Do you really think that the limits of the 3D representation that only shows a 1/4" pebble that does not exist in the actual 1D theory used, should really provide a 20% penalty to the attack roll?

You know that if 2 infinitesimal lines are drawn with the exact same start point and the exact same end point that they are in fact identical and would share the exact same blocked/clear status don't you?

In both diagrams, the start point and the end point are the exact same. It's only if you use some thickness on the lines that one would be blocked and the other wouldn't.

2 cases:

1) If the line is infinitesimally thin, both lines are the exact same and share the exact same status.

2) If the line has thickness (perhaps a pixel thick), it should spread so that 1/2 pixel is above the centerline and 1/2 pixel is below (and both lines should be drawn exactly the same). The only way that 2 lines would have different block/clear status is if you 'cheat' and have line 1 with a full pixel above the centerline and nothing below, and line 2 with a full pixel below the centerline and nothing above.

What you're doing is using situation 2, and 2 different lines and declaring that they are the same line for drawing purposes but different line for block/clear status.

I think you're much better off going with seeb's approach and declaring the area is what counts since trying to use the exact same line and declaring that they are different statuses is nonsensical. Of course you still get the utterly ridiculous situation where the archer at a corner has a massive advantage over the swordsman.


Komoda wrote:
For something to overlap it must have surface area.

Not really. It just has to have points. Lines consist of an (uncountably infinite) set of points. If there are many points in common between two lines, they overlap. If there's exactly one point in common between them, they intersect.

Quote:

A line has no second dimension. It has no surface area. It cannot overlap.

The lines in your example cross at (0,0). This fits with my statement that lines cannot overlap only cross or not cross.

What about (0,0.0001)? It's on both lines. (0,0.1)? On both lines. (0,0.9998)? On both lines. There are an infinite number of points which are on both of those line segmants.

Quote:
It only matters because we are getting into the nitty picky area of the game. This level of precision is not required. But I assure you, the math proves that the original situation does not provide cover.

I am not going to accept math advice from someone who insists that two parallel lines, one of which does not have a single point in it that isn't in the other, are not overlapping.


seebs wrote:
I am not going to accept math advice from someone who insists that two parallel lines, one of which does not have a single point in it that isn't in the other, are not overlapping.

No, you're just going to be petty and illogical and cling to a single point in which he was a little incorrect so that you can ignore the weight of his logic.

Liberty's Edge

You guys are funny. Obviously you don't count lines that follow the face of the wall as going through the wall. If you did, it would mean that two guys facing each other in a straight 5 foot wide hallway would have cover from each other.


1 person marked this as a favorite.
RedDogMT wrote:
You guys are funny. Obviously you don't count lines that follow the face of the wall as going through the wall. If you did, it would mean that two guys facing each other in a straight 5 foot wide hallway would have cover from each other.

What has their panties in a twist is that if you take the same logic and put a square wall between the two characters, suddenly those characters don't have total cover from each other, just regular cover. And so seebs and company are taking that back to mean that the logic of geometry isn't the final word here, and they are going off the rails on that crazy train, to say that any argument involving geometry, is invalid with regards to the RAW, and only applies to RAI (Maybe) and GM Fiat.

Basically, if you try to apply the rules of geometry to the rules of cover (dear god, totally grounds for a Homebrew), a fringe "contradiction" pops up and everyone is getting upset over it.


You know, I never even considered lines sharing more than one point in this argument other than being the same exact line.

By line, I mean one that goes on forever and is completely straight. Curved lines have no place in this debate, wouldn't you agree? And if we are only discussing straight lines, if they share more than one point, it is actually the same line, isn't it? (line, not line segment)

RedDog, that seems logical, and common sense would state that you are correct. But it can't be factual. If a wall only sticks out 2' from the edge of the square, it may not be crossed by any of the other lines used to check for cover. But I am sure we agree it would count as cover. Grid-3.

I get the argument that counters mine. It is the same problem with the terms midnight and noon. Neither of these concepts is actually a measureable amount of time. Midnight is the time after PM and before AM. Noon is the time after AM and before PM. They are both an exact instant that cannot be measured in length.

And how can a line cross a boundary and not cross a boundary if it has no thickness? I get it. But even though it has no thickness, the only practical way to use it to prove/disprove cover is to use a side of the line.

And by the strictest reading of RAW, the yellow shaded area of Grid-3 offers no cover unless you count the lower edge as crossing the boundary.

And the blue area is only clear of color if you do not count it as crossing the boundary.

So I guess at this point we are to choose from the following options:

1) House rule that my shaded area is what should be checked.
2) House rule that we have to use a side of a line, not the line itself.
3) Follow RAW and in addition decide that passing through the vertex counts as a barrier.
4) Follow RAW and in addition decide that passing through the vertex does not count as a barrier.

While it was never my intent when I drew the examples, I think I am going to go with option 1.

Do you see any other options besides these 4?

And these are not fail proof either. In option 1, a 1' diameter tree would count as cover. So would a 1" diameter tree. So you would have to decide what type of object is actually strong enough to provide said cover.

If you used any other option, the exact placement of the tree would decide if it counted as cover (still if you decided it was strong enough). If it missed any of the 4 lines used to check for cover, it would not count.

Just move the wall from Grid-3 up 1/16" and it won't count as cover using options 2, 3 or 4 as none of the lines would cross it.

But again, I think our precision is getting far to exact for any benefit of the game.

Great debate though. I find it very interesting.


Assuming euclidean geometry, yes, either two lines are the same line, or they cross, or they are parallel. I'd been using "overlap" for "lines" which were really just "line segments", and thus not infinite in length.

The problem, I think is this:

-#-
A-B
C#D

(- for empty space, # for solid wall).

The lines (in the sense of "infinite lines containing these line segments) from the top right of C to the top left and right of D are clearly the same line, and are also the same line as the lines from the bottom right of A to the bottom left and right of B.

But we want those lines to be clearly "open" for AB, and "blocked" for CD.

A friend of mine says that she thinks she remembers that in 3.5 or D&D Miniatures, they clarified by basically saying "pick a point somewhere INSIDE the square, but near a corner". And that actually solves it perfectly well.

The other option I like is to ignore the lines and look instead at the areas bounded by them. So, take Komoda's excellent drawing, and instead of looking at the lines, look at the shaded yellow area.

If there are no obstructions in the shaded area, there's no cover.
If there are obstructions, there is at least some cover.

If there is at least some cover:
If you can draw a line from the starting point to one of the four target corners which doesn't touch any obstructions, then it's partial cover. Otherwise it's total cover.

This is probably still a little oversimplified, but it should cover everything.

I think the "shaded area contains any obstructions" answer is the easiest to do intuitively just by looking. Then that two things share a boundary (say, the shaded area and an obstruction) doesn't matter, because we're looking at the areas, not the boundaries. But the "just inside the corner" answer works.

The other option, I think, is:

(1) Even touching a wall counts.
(2) Pick any point inside your square, and draw lines to just inside the four corners of the target.

The "inside" solves the corridor problem.


AA|00
AA|00
00|00
00|00
00|00
00000
00000
00|00
00|00
00|00
00|00
00|B0

I also find it weird that in the above situation, any of the 4 archers can shoot at B with just regular cover since they can all designate their common corner as their firing point and specify B as being in the upper right or lower right of his square.

In practice, if B stays against the wall or even in the center of the square, there should be no way that any of the archers can shoot him. Certainly not the 2 archers that are 2 squares away from the wall.


Celanian, while you diagram is correct I disagree with it being regular cover. They can only see a tiny fraction of the target. As a GM I would rule that this is Improved Cover.

- Gauss


00|B000
00|000C
00|0000
00|000D
0A|000E
0000000
0000000

Back to this subject. I find it interesting that A has total cover from B, C, D, and E, but can freely shoot any of them with no penalties. He simply draws his line from his lower right corner. Even if B-E readies an action to attack him as he shoots, he never loses the total cover status while he's shooting and thus has immunity from attack.


Strict RAW doesn't work, usually never does. We proved it. You have to make an educated decision based on the situation and what you can gather what the rules intend.

In this case, they intend full cover for all parties.

51 to 78 of 78 << first < prev | 1 | 2 | next > last >>
Community / Forums / Pathfinder / Pathfinder First Edition / Rules Questions / Does just the corner of a border provide cover? All Messageboards

Want to post a reply? Sign in.