Erioch Ourevest

HastyMantis's page

Organized Play Member. 91 posts. No reviews. No lists. No wishlists. 6 Organized Play characters.



2 people marked this as a favorite.

I see we have an errata section with the FAQ now, which is awesome. Is there an appropriate place or method to submit things we're pretty sure are typos/errors (and not just rules we don't like)?

The sticky in the rules forum indicates that's not it, but I'm not sure where else to go with it.


1 person marked this as FAQ candidate. 1 person marked this as a favorite.

Part of the issue may be that there are questions buried deep within these discussion threads, so different phrasings of a question might each get a few FAQ clicks.

But anyway:
https://paizo.com/threads/rzs42a8m?Rail-cannon-vs-cover


2 people marked this as a favorite.
Xoshak4545 wrote:
no wait, I guess you would want to do the duster first ..duh.... so halved is 43 -20 = 23 and it would cut threw .. hum ...yea I don't think I want something ignoring the maxed out hardness of a 20th level weapon

But I want to cut through a starship...


1 person marked this as a favorite.

A baton or survival knife would be less elegant than other operative attacks, and so would get the -2 from bludgeoning or slashing bayonets.

What you really want to do is put a sword cane on your sniper rifle.


1 person marked this as a favorite.
Steve Geddes wrote:
HastyMantis wrote:
Right, I more meant to ask if there was a publicly stated policy about errata. Some insight would be great.

The policy Dark Midian was referring to was that of not releasing PDF errata for a book until the printed copy receives a revision. That’s been affirmed many times during Pathfinder’s lifetime.

It seems to me they are following a similar approach with Starfinder,but I don’t know that they’ve every explicitly stated as much.

Thanks. Starfinder is my first Paizo game, so that's new to me. It kind of explains why several of the "FAQ" entries are answered with what appear to be complete changes in wording...


1 person marked this as a favorite.
CRB p.380 wrote:
The type of object thrown doesn’t change the damage type or any other properties of the attack.

Pretty straightforward rule.


2 people marked this as a favorite.
BigNorseWolf wrote:

That the line weapon stops when it hits cover or a creature it can't damage from hardness does not mean that that's the only way it stops.

True. It also stops at the end of its range.


1 person marked this as a favorite.
Dracomicron wrote:
Hilary Moon Murphy wrote:
But.... but... the RP is the best part! Aeon Throne is too delicious to rush.

Oh we RP.

Dr. Zorkfeld commits surgery as if he were a real doctor, for example.

We just do it shorthand.

"We can't steal that, it belongs to Astral Extractions!"

If this forum allowed images...


7 people marked this as FAQ candidate. 1 person marked this as a favorite.

The book does not appear to be very clear about gloves. The example in "HOLDING AND WIELDING WEAPONS" (CRB P. 168) talks about holding a longarm while wearing a battleglove: you can do it, but can't attack while holding the longarm in that hand.

Does that mean the same rule generally applies for other hand-suits?

This is a list of every melee weapon that seems like it might be something one wears on a hand. The format is: {name of item} - {word from description that qualifies it as a hand-worn article} - {what that description says about holding stuff}


  • Battleglove - "glove" - Can Hold Objects
  • Shell Knuckles - "glove" - Unspecified
  • Bone Cestus - "gauntlet" - Unspecified
  • Injection Glove - "glove" - Unspecified
  • Painclaw - "gauntlet" - Cannot Hold Objects (or be disarmed, also a full action to put on)
  • Heat-Amp Gauntlet - "gauntlet" - Unspecified
  • Searing Grip - "glove" - Unspecified
  • Electrovore Glove - "gauntlet," oddly - Unspecified
  • Pulse Gauntlet - "gauntlet" - Unspecified
  • Resonant Gauntlet - "gauntlet" & "glove" - Unspecified
  • Polarity Gauntlets - "gauntlet" - Unspecified

Battleglove has a specific note that you can hold objects, as in the example. Painclaw specifically says you cannot. The others say nothing at all.
What say y'all?


1 person marked this as a favorite.
Ravingdork wrote:
Why is it that I seem to be the only one who perfectly understands what BigNorseWolf is trying to say...?

I assumed it was because you were a sock puppet.

You and BNW are using a weakly stated general rule, that a wall blocks line of effect for "most effects" and deciding that it overrules a specific rule that give a method to determine what can stop its effect.


2 people marked this as a favorite.
Pantshandshake wrote:

I know that for damage, a double double is a triple. I believe that's called out in the critical hit rule section. But I can't recall seeing it for non-damage things.

And, correct, I don't believe they're enhancement bonuses, I believe they are insight bonuses. Which also don't stack with each other.

If we're saying the doubling is itself a bonus, it has no type listed. The operative's edge bonus itself is certainly insight, but clearly it can be modified.

Good idea looking for the critical hit section. That used the word "multiplying" which got me to try searching that.

CRB p.242: OTHER RULE TERMS wrote:

Multiplying More Than Once:

When you are asked to multiply a value or roll more than once, the multipliers (×2, ×3, and so on) are not multiplied by one another. Instead, you combine them into a single multiplier, with each extra
multiple adding 1 less than its value to the first multiple.

For example, if you apply a ×2 multiplier twice, the result is equivalent to multiplying the value by 3 (or rolling the damage three times), not multiplying it by 4.

So that actually seems pretty definitive at +6 (double twice is triple)

I guess the movement costs are the specific beating general, since they do compound.


1 person marked this as a favorite.
Ravingdork wrote:
Line weapons do not say they ignore cover bonuses to AC, so logic would dictate that you follow the standard rules for cover and apply the bonuses.

The cover rules also address targeted attacks, which line weapons are not. They don't even say "make an attack against each target." They say "make a single attack roll and compare it to the relevant Armor Class of all creatures and objects in a line extending to the weapon’s listed range increment."


1 person marked this as a favorite.
BigNorseWolf wrote:
HastyMantis wrote:


Some think you need to read the rule in a way that will avoid very silly and improbable results and are willing to accept frequent pretty silly results,
Please name any silly result I'm getting. At all.

Weapons that can expressly shoot through obstacles can't shoot through walls, because they can't see the other side.


1 person marked this as a favorite.
BigNorseWolf wrote:
Pantshandshake wrote:

As far as the rules of this non-simulation are concerned, it doesn’t matter what the weapon is. The line weapon rules are basically “This is a gun. It fires a munition. The munition behaves in this specific way.” I get that you want a flamethrower to not fire through a thing.

Its not a matter of want. The words simply do not say what you think they do without affirming the consequent. The line stops if it hits something it hits but doesn't damage does NOT mean that the line ONLY stops if it hits something it doesn't damage.

I am more than willing to point out where raw has gone borked. This is not such an instance. The thing causing the problem is something that people area reading into the doughnut hole.

You're right: the line also stops at the end of its first range increment.


1 person marked this as a favorite.
BigNorseWolf wrote:


...
And how are you ordering them? ...
General rules of the game: you need line of effect to make attack rolls

Line rules: Lines are straight lines between you and point B and you affect everything in the line

Line weapon rules: line weapons are not stopped by hitting one creature (the way a single attack would be), the line isn't stopped by hitting cover. Line weapons are also stopped if they hit something that they can't overcome the DR to (normal lines aren't)

Your interpretation is not the same thing as the raw. If your interpretation winds up at abject sillyness (and we are at abject silliness) or brokeness re think it, it doesn't have to be right just because you interpreted it.

Single attacks aren't stopped by hitting one creature, nor are they stopped by hitting cover. They only target a single... erm, target, which may get an AC bonus from cover.

Not gonna shock you here, but I think your reading is the one that results in silliness. (Hope we're all still enjoying the debate, though!)

Let's talk about a wooden table. By your reading, if Iseph is crouched behind an overturned butcher's-block table (6 inch thick) when the advanced-rail-cannon-wielding security robot shoots down that line, that rail cannon will do 3d12+12(-5 for hardness) to that table and then deal 3d12+12 to Iseph, assuming the attack roll hit their KAC.

If we expand that table to make a wooden wall (6 inch think, hardness 5, 60HP, just like the table), by your reading, the rail cannon shot does 3d12+12 damage to the wall (again, minus 5 for hardness), but stops there. Because the wood is wider, the shot can't penetrate it.

To me, that's a much sillier reading.


1 person marked this as a favorite.
BigNorseWolf wrote:
So which part of the rules are you going to insist is absolutely right at the exclusion of the other?

Glad you asked!

Specific. Beats. General.

Generally walls stop line of effect (though even that part suggests they don't always). The line rule says exactly how far they go and exactly under what circumstances they stop.

Whether targets along that line get cover bonuses or concealment are good points for debate, but whether or not walls stop the line is clear: only if it can't beat hardness.


1 person marked this as a favorite.
Ravingdork wrote:
Vexies wrote:
so.. apparently these shots do indeed penetrate objects after all and walls are indeed objects by the rules.
Got a rules citation for that? Insofar as I'm aware, walls are not objects. They are structures.

That's some fine Aristotelian chicanery you've got there. ;)


1 person marked this as a favorite.
Ravingdork wrote:

I honestly can't believe the game developers intended "obstacles" to include walls 50+ feet thick.

I wholeheartedly agree with BigNorseWolf. This is Aristotelian rules chicanery at its finest. Allowing it would only end in everyone carrying line weapons and the vast majority of encounters ending without the PCs ever seeing their foes. There's no way that was the developers' intent. Starfinder has been too well fine tuned to suggest that they would even consider something so unbalancing.

But by all means, prove my assertion wrong. Hit the FAQ button in the post linked here and perhaps we'll get a response. If I turn out to be wrong, guess I'll be in the market for a line weapon. >:D

Button hit. If you want to gm fiat reasonable things like "can't go through a mountain" go right ahead, but don't act like that's the same thing as asking if they can go through obstacles, which they clearly can: it says so right in the book.

Also, line weapons are still pretty bad, so I think your fear is unfounded. I sure do like being able to take multiple shots per turn, sometimes our of the first range increment, often through my allies' spaces without having to damage them.


1 person marked this as a favorite.
Xenocrat wrote:
Yes it does.

It does explicitly that. This weapon fires a projectile in a straight line that pierces through multiple creatures or obstacles.


1 person marked this as a favorite.
Magyar5 wrote:
I actually had a similar problem with my Vesk Soldier. ... I then dumped the new skill points in to Piloting just to make it possible to hit enemy ships as the Gunner.

But if he's a soldier, doesn't he have full BAB anyway? Max ranks of piloting would match what you already had...


1 person marked this as a favorite.

Have:
Gen Con 2012 #15: Student of Runes
PaizoCon 2013 Player Boon #4: Expedition Manager
PaizoCon 2013 Player Boon #14: Varisian Caravaner
PaizoCon 2013 Player boon #18: Xenophobia

Want:
Starfinder boons