thenobledrake's page

I really find this rule ridiculous. Most humans stay awake for more than 16 hours without being fatigued, sleeping 8 hours per night is far from a generality. Actually, many young humans can stay awake for 2 consecutive days and function normally.

Game rules don't need to match real life, they need only make a game-play condition that bears consequences that are relevant enough to create a choice point.

So it doesn't at all matter whether "you can't just adventure forever without penalty" is "realistic" or not.

However, I'd suggest that your assessment of "function normally" is a skewed one. Sleep deprivation is a serious thing, and even though people (especially when young) can operate in a way that it seems like they are functioning they absolutely are not at the same level of functionality they would be at if they were well-rested.

The game is not any harder to learn than most of the rest on the market. It's actually easier than a wide variety of them too.

Most of the "this game doesn't teach new players" rhetoric comes from people with something to un-learn rather than someone that doesn't have information and goes to the game material to learn it.

For example, the problems people have had with encounter design and spell casting both stem from someone (sadly an AP author in some cases, leading to "but the pros did it, so it's actually right, right?" thoughts) carrying forward the idea of how those things work from some other source such as a prior edition or different game. People learning this game as their first game having fewer issues in those avenues.

There's really no way to fix that because the thing that would solve it (writing the game material assuming the reader already knows a different thing and telling them explicitly to not do the things this book doesn't say to do) would complicate and clutter the language and leave anyone not needing to be told "what you know about games other than this one is not actually relevant to how to run this game" with more chances to misunderstand what the rules are saying.

One thing that PF2 could steal from D&D is weapons having secondary effects, with fighters being the masters of using those secondary effects. I know that PF2 has critical effects and that Fighters are the best at scoring critical hits. Still, a system where every attack has a minor effect attached to it would make "just" swinging a weapon each round feel more engaging without adding a lot of extra overhead or decision-making to the game.

It's funny how perspective colors the relationship of different game systems.

Because where you are saying that PF2 could take a particular thing from D&D I am seeing a thing which D&D just recently "we'll do that too"'d from PF2 because the it's-not-a-new-edition D&D "weapon mastery" details are basically just a take on PF2's weapon traits and critical specializations blended together (and then made artificially limited so that gaining more as you level up can be presented as if it were a meaningful benefit even though you already picked the most relevant and/or can swap out for the most relevant options at regular intervals).

The problem with fighter "lack of identity" is that it is artificially constructed.

It's only because people think of every martial as being a "weapon master" of some sort that the class which actually has that as its niche looks like it is missing something.

The cause of that is all those other martial classes tracing their lineage back to being "it's a fighter, but..." in design, so even though PF2 has more unique pieces of each class people look at fighter as the "vanilla" martial (with the context of vanilla in this case being treated as the absence of flavor rather than a flavor itself).

This is a really confusing claim to me.

In my experience, players more often than not limit themselves to a particular weapon even if there isn't a specific increase in stats for one. They also limit themselves to a particular weapon because of all of the other mechanical differences that can come up before a fighter has to pick a weapon group to be even better with.

So to lay the feeling of being limited on getting an increased proficiency strikes me as odd because most players were already locked-in on their weapon choice just because it had a particular trait they liked, and most that weren't locked-in at that point got locked in once runes started getting added to a weapon. Meaning that in practice there's no change in play happening at the time weapon mastery group is chosen.

I'm with Graystone on the interpretation that the words used seem specifically chosen to make the personal rune not actually a staff.

If it were meant to follow the standard rules of preparing a staff there is far more straightforward language that could be used to convey that point which would also allow different phrasing to be used on the portion about what happens when you have an actual staff merged with your personal rune polearm/spear because the "adding its charges" part would either be absent or else produce a different confusion point as we don't have anything telling us that we can't expend a slot for additional charges on the prepared staff if we already expended a slot for the (non-existent by the actual rules phrasing) additional charges on the personal rune.

thenobledrake wrote:

I see removing the rule that's easy to forget (the "yes, you crit and rolled awesome, but this creature type gets to ignore part of that" single-target damage clause).

Its also easy to forget because it almost never comes up. Maybe if you have a level 1 fighter or barb with runic weapon fighting a troop, but by higher levels HP inflates enough that I have yet to see it come up at a table.

That's also true.

The one time I've seen it come up in the past was a giant instinct barbarian landing a high-rolled crit on a shambler troop and the slashing weakness pushed the damage total over 60 which would have taken it from full HP to the 8 square threshold if not for the rule.

It seems to me like the changes can be summarized as:

Specific shaping and spacing instead of vaguely implying 16 spaces on the map could be occupied and effectively sharing stats.

Removal of the clause that damage from particular sources be treated differently.

Altered details for non-damaging effects so that there is not the extreme case of needing to affect every creature in the area and only a special clause for an effect that has a non-action/fleeing/non-participant kind of effect.

So I fail to see what "trickier" or "complicated" you're talking about. I see removing the rule that's easy to forget (the "yes, you crit and rolled awesome, but this creature type gets to ignore part of that" single-target damage clause), and covering a lot of the weirdness that Form Up used to imply was possible, which are both just improvements in ease of use. And alongside those is effects the players have being made more likely to be able to have some use since they no longer operate on an all-or-nothing basis, which makes facing a troop less onerous for the players.

Looks like improvements across the board to me.

Crawling through keyholes won't be allowed.

This is exactly why the allegedly confusing redundancy is necessary; players are definitely going to read the spell and think that which tiny creature they choose is going to matter because a spider and a rat are both "Tiny" even though they aren't the same specific dimensions (just like someone 6'3" and someone 5'2" are both Medium and don't have different rules interactions in this game despite one not being able to reach the top shelf in my actual kitchen) - and the spell is clarifying that not to be the case.

If that bit of text weren't there it'd just be another place where people argue about what is or isn't actually valid according to the wording of the rule, and it only presents as "confusing" when viewed from the perspective of already understanding the outcome of not being able to crawl through keyholes and the like.

For those of you insisting I'm wrong about how communication can still get turned into a bad thing; look at ElementalofCuteness's post and the way the phrasing suggests that being told an error hadn't happened has screwed up the situation.

I'm not talking slippery slope that might happen, I'm talking observation of historical fact on the matter and a "slope" we're already seeing people at the bottom end of.

Even the "It is true, but only in communities where there's trust that they really well get back to us." statement is doing the very things I was talking about in that it presumes the only explanation for things not going well is the designer-side of the scenario by putting the weight on the designer-side to make sure none of the fan-side feel like they have a reason to distrust them rather than putting any responsibility on the fan-side of the situation to not be unreasonable and distrust designers that are genuinely trying just because that effort doesn't match expectations the fan-side set in their own minds without any particular reason.

And that's why the only responses being made to my comments are vague (the good ones) and framing a near strawman out of the extreme end of the idea by implying the game is currently unplayable because of a lack of response (so bad it's basically admission of not having an actual counter point) instead of talking about any specifics on things I've argued; like how I say the fans will arbitrarily decide it's been too long without an update that isn't "working on it, more info later" and no one has even tried to offer up an idea of how long is objectively too long that isn't a hyperbolic "it's been 6 years."

This kind of thing goes the bad way so often and so consistently that even communities that win praise for how they behave become memes among people that aren't pleased with how what they wanted to happen didn't happen. So even as you have a case of the devs communicating with and listening to the fans you also have fans insistent that the devs don't know the first thing about what the fans want from the game and have no interest in finding out because they are detached from how the players actually play the game - and more communication isn't a thing that can actually change that. It can, however, make the devs even more stressed out by the fact that no matter what they do someone is going to insist it is proof that they are screwing up the game.

As has been demonstrated a billion times over across the internet, people are always way more welcoming and thankful for a “nothing to report, but we’re working on it/have seen it” report than silence.

That's not even remotely true.

The initial response to that kind of reply might seem favorable, but the attitude quickly turns when the time that passes before a response happens exceeds some random person's personal idea of what has been enough time, or when enough of those sort of responses have been made to go past some random person's personal idea of how many is a reasonable number.

You will literally see people complaining about someone taking the time to come say "nothing to report" instead of spending that time working on making something worth reporting if you go look for it. You'll also see any reasonable and transparent explanation of a delay being picked apart by people that were going to be pissed no matter what - but because of the communication now they have something to latch onto instead of just a vague, angry, "why won't they tell us what's going on?"

That's what has happened over and over throughout the entirety of this and many similar hobbies.

That's why so many companies try to keep communication down to specific forms at specific times or in specific ways and even the ones that do try to be open and constant with communication change that aspect over time. So it is better to hold communication until there is something with some meat to it to say or some dire circumstance that is necessitating what would otherwise be premature communication, because even though that too will have fans being unreasonable about it it at least minimizes the exposure and thus the fatigue that comes from dealing with agitated people.

... Which is why nonspecific defenses and "no one can really agree" arguemnts feel kind of toxic. They rely on abstracting reality away to present a position that can't be argued against because it's grounded in nothing.

The problem here is that you're doing the very thing that you're pointing at as being the problem with what I said.

In order for it to matter that someone has been waiting "six years" we have to in a non-subjective manner determine that the question you frame as being important is actually one of genuine importance... which I have to say doesn't seem like is likely in the case you're talking about because your framing suggests that it wouldn't be plausible that the vast majority of groups have already plugged in what they believe the thing "should" work if they even experienced an issue in the first place and have been playing the game just fine for the entire six year time period mentioned.

What you have done in your response is illustrated exactly what I was talking about; the issue, whatever it is, that you're talking about you are willing to frame as a thing the company is screwing up because they didn't answer the question you wanted answered with the kind of answer you wanted (lack of response, including lack of acknowledging the question has been asked, is it's own kind of answer) within what you felt was the reasonable time frame to give such an answer.

Companies that make games are basically damned if they do and damned if they don't on this kind of thing. If they stay out of the situation they get negative reactions for lack of communication. If they communicate they invariably get negative reactions to that communication. Fanbases suck at self-recognizing this kind of thing too, so people genuinely don't realize how/when they are being unreasonable with stuff like "they said X and it hasn't happened in Y time, so clearly they were lying" or even just "I asked a question and didn't get a response" and acknowledging that a reason besides the company sucking at what they do exists for that case. Y'know, like asking a question that puts the team in the position of having to carefully consider how to answer so as to provide understanding to a customer that doesn't have it yet isn't insulting to that customer's intelligence in the way that answering with a page reference for the location of the relevant rule that isn't even uncleanly written that the customer is misunderstanding (or even understanding, but not liking and asking about to try and get it changed) or saying the question doesn't need a response would be.

There is a very clear and easy middle ground to me between “random designer tweets out what they personally think is the answer to RAI without checking with others and then people run with” and “radio silence until an errata comes up and then if it doesn’t get answered then you have to roll the dice again”.

It’s “have someone come and tell us all in a public space that they’ve seen this and will talk about it, and then come and tell us the RAI and if things might change once they’ve had a group discussion and come to a real decision”. Preferably they can then go as far as to post a “questions we’re looking into” master list everyone can see so we know that even if it takes a few months they’ve seen and will get to it one way or another.

I’m disappointed that they’ve basically gone with radio silence unless you win the private email lottery, and then you can either get an answer or a “wait until errata maybe deals with it”. To be clear, I’m not blaming Maya because they didn’t give the impression this was their preferred route either and at the end of the day they’re not the one who can generate the answers.

The problem with your "easy middle ground" is that turn around time is not something people will ever agree about how much is actually on the table and or reasonable.

Just like we're already seeing from you being comfortable with the phrasing of "radio silence until an errata comes up", fans are prone to think a dev could just pop in for 5 minutes and answer a question and everything would be awesome - no matter how much said fan knows they don't know about what that dev's daily schedule is like.

So even with someone taking a genuine stab at spending some of their work hours checking through community questions to then provide "we are aware of this issue" messages and work the solutions and then come back with them, there's strong (like nearly assured) odds that the fans are going to feel like they've been told an issue is being checked on but that it actually isn't because it couldn't possibly take this long to sort it out. And then the end result of attempting to be more communicative with the community is that community getting even more convinced there's no meaningful communication happening, especially if any part of that communication involves telling people what they view as being an issue actually isn't or the official response being not the thing the person was hoping it would be (which I'll never understand why sets people off so badly; if you know you don't want a particular answer, you don't need to ask the question, just house-rule the thing you do want and get on with your day).

For D&D5 there were long years of Mike Mearls and Jeremy Crawford twittering rules clarifications, sometimes contradicting eachother or themselves, and even when the Sage Advice Compendium cleared up a lot of things, a lot remained unresolved.

It would be nice to have a more structured way of asking questions, like a scoring board where the community could upvote issues.

Let's not forget to mention the thing which happened that was even worse than Mike & Jeremy providing answers not in line with each other or even themselves; when Jeremy said something that wasn't even possible according to the language in the book and then changing the rules text so it matched his incorrect tweeted answer instead of admitting the answer was incorrect.

I've always had a problem with the idea of an official way for people to ask question and have a reasonable expectation that they would get an answer. It is one of those things which sounds like a great idea yet it seems to invariably arrive at misuse, mistreatment, or both.

I have dozens of times throughout the years where a rules discussion I was having with someone turned into me having wasted every moment I spent involved because no matter how much I could quote the book, explain the meaning of the sentences in the book based on their context and structure, and no matter how many other people would chime in to back up the points and evidence, the other person believed an "official answer" was needed and they were going to try and get one. Even when the language in question wasn't unclear, it just clearly said something that person wanted to not be the case. And yet an official answer would be sought and then when the answer was officially given - despite effectively having been a developer taking time to say "yes, the text in the book is correct." - many of those people that insisted on having an official answer were not actually pleased by receiving one. Some of them would even go the route of not just what they could have been doing the whole time and saying "I don't need an official answer, I can house-rule in a way that works for me and my group." but actually being angry at the team for the official answer not being what they wanted it to be.

And in that experience I've seen that if you can directly ask the team behind a game questions that the questions are going to be heavily laden with pointless ones where someone asks what is obvious to most readers or is asking the same question that has already been answered because they are hoping for a different answer. When doing what all it would take to actually prevent that misuse it basically just turns the system back into what we fundamentally already have; we can talk about what we think is wrong and the devs will eventually clarify or correct what they pick up on as important enough issues to be worth the effort.

Plus the direct nature of the call and response is basically how come way back when you could get on the official forum and find people arguing against what the person put in charge of the official rules said - again as a result of people for whom it's not just "official" that matters, it's that their own view of the rules has to be the thing which is "official" or even the official answer is "wrong" - or outright being abusive towards staff because of the interaction between fan and staff not having gone the way the fan was hoping that it would.

Basically the entire reason that we have so little contact with Paizo staff while on this message board is because of trying to let the community ask direct questions and add their voices to the conversation that resulted from doing so.

Didnt I write just that?

No, because your statement was backed with a meaning that supported your other statement "He has a point" where as what I was saying is there's no valid point to be found in the territory of treating lack of redundant mention of a general rule as being the same thing as presence of an explicit specific rule.

Considering that most other classes do state that the starting equipment from features has to be common...

Some authors choosing to be redundant does not mean that any that do not were actually writing statements that specifically counter the general rules established elsewhere in the book.

There's even a passage of text in the book, though I can't recall exactly where at this moment, that covers this kind of misplaced expectation that "it doesn't say I follow the general rule" is the same as "it says exactly what way in which I don't follow the general rule."

This is likely a significant part of the reason why Paizo chose to write this edition in the "to be read as casual language" style that they did; because it's absolutely a pain to make sure everything doesn't just convey the same meaning, it does it with the exact same phrasing, so no one thinks they caught a special exception just because one author picked not saying you get to do something special as their method of conveying they didn't say that while some other author used extra steps to reach the same result.

Pixel Popper has a good point about making sure not to indicate "no effect" when you mean "redundant effect" so that you don't misinform a player.

There were plenty of times in the campaigns I've played thus far in which a redundant effect happened to serve an important purpose, whether it was me using Snagging Strike despite that I was flanking the target so that my ranged attack using allies could also get the benefit of their target being off-guard, or someone moving into a flanking position even though the flanked target was currently prone so that when they stood up they would still be off-guard, or a sword critical hit causing off-guard with a timer on it and that serving a purpose even if the target was already grabbed at the time it happened.

Telling a player "that did nothing" would give the wrong impression, and if it were actually true would also mean having changed the rules of the game.

Yeah, all I'm seeing here is that you've had bad GMs*...

Yes, I have had bad GMs. Specifically of the variety that were bad GMs because they were following suggestions found in the rule-books in the spirit that it appeared those suggestions were made.

Or to phrase that differently; I had GMs that were bad because they believed meta-gaming was something that needed to be policed.

You are repeatedly displaying an inability to understand that tables can have different social contracts and implicit rules.

No, I'm not. I'm just not conflating "expectations and rules can vary" and "there's no such thing as being able to evaluate if a rule or expectation is internally inconsistent or not".

I understand that table variance exists, it's just not relevant to this discussion which is about whether or not a particular thing people mean when they say the phrase "meta-gaming" actually makes any sense. And it doesn't because it is internally inconsistent; literally every table that says "we try not to meta-game because meta-gaming is bad" can be demonstrated as selectively applying their own definition of "meta-gaming" because none exists that can be applied consistently outside of the definitions that are entirely incompatible with the "is bad" and "try not to" parts of the statement because they identify the process of meta-gaming (player knowledge impact character actions) as the unavoidable part of game-play that it is.

Yet even as they agree that players shouldn't be stuck in thought processes such as "my character doesn't know how many HP they have, so they can't try to run away because their HP are low" some people will still think "...your character doesn't know that will work well so it's unfair that you're trying to do it." and not restrict that to explicitly edge case moments where it's actually reasonable to say no one would ever take that action just to see what happens - also know as the things more accurately called "cheating" than "meta-gaming" because what is different about them is not player knowledge being involved, it's knowledge the player actually shouldn't have or the character would genuinely need in order to choose what they are choosing and definitely does not have it.

The act of defending meta-gaming as being a real and avoidable thing that has a negative impact while also insisting it is an entirely nebulous subjective thing that each table has their own definition of that are all valid (unless, apparently, used by someone you deem a "bad GM") does nothing for the hobby other than empower bad GMs to give terrible experiences to their players and players to also cause bad experiences for themselves and potentially others by using the idea of meta-gaming being a bad thing to lead themselves to disruptive actions they believe they "must" do.

That's why it was good when WotC tried to re-define the term to apply only to thinking of the game in game terms which might lead you to the wrong conclusions (such as the example provided in the relevant passage being a player believing a monster must be within the party's ability to fight because they think the GM is adhering to the encounter building guidelines, rather than potentially showing a powerful foe there is no intention of combat with). Unfortunately, that definition got no traction because a significant reason the old definition is a problem in the first place is the deeply-rooted assumption that the only reason anyone would disagree with the definition is because they are the very "bad player" that the idea is presented as stopping from doing the "bad thing" that helps justify immediate dismissal of incompatible ideas.

Slurping noodles is impolite, except at the dinnertables at which it is polite.

In both cases there is a clear and reasoned explanation which applies to the case and can be explained but then not have the explanation fall apart because it's not actually the slurping that matters, it's what you're thinking when you are doing the slurping that matters.

Which is to say, that's not even kind of a good analogy for meta-gaming.

Magus taking psychic archetype isn't metagaming,* except at the tables which it is.

It isn't a special case of meta-gaming at any table because it does not matter what a class feat gets spent on it was equally a choice made because of player-knows-rules-material reasons.

Which is the thing I am getting at. There is no magical "well, it's actually a whole other thing from just playing the game normally" that varies from table to table, even though you may find some table that uses the word "meta-gaming" when talking about why they don't allow the choice. What they actually mean to be saying is "I don't like how that works, so I don't allow it", and that's fine - and actually a case of something subjective which while I don't agree with is not actually something which I can say is objectively incorrect since unlike saying "that is meta-gaming" (and meaning that to mean it is a thing you're supposed to avoid doing) which is presenting something as an objective fact.

I don't really care what is the "correct" definition of meta-gaming, frankly.

Then why would you involve yourself in discussion of the definition of the concept?

It's not the thing people that want to watch out for it say it is, it's a natural and unavoidable part of game-play as a result of there not being any way for a person to play a game without knowing it is a game and - even if they try really hard to just never do so - picking up at least something about how the game functions.

You can even test for whether it is the actions and the character that are "a problem" by doing a thought experiment about when something is or isn't inappropriate.

For example, your character has had an enemy approach so that the character is within the enemy's reach. When, if ever, is it "meta-gaming that you should avoid because meta-gaming like that is bad" to move away? Does whether it is or isn't meta-gaming of that sort change depending on whether it is Step, or Stride? Does whether it is or isn't meta-gaming of that sort change depending on any other factors such as the character's build, 'usual combat pattern', the creature's actual abilities, how much the player genuinely knows about the creature in question, or how much the GM thinks (correctly or otherwise) the player knows? And if yes, why?

Because this is exactly the kind of thing which strikes the "Hey, you can't do that, that's meta-gaming" response - but somehow only when the GM is really hoping to smack a character with a creature's reaction and the player has picked some course of actions that doesn't trigger that reaction, and how reasonable it is to have done so from an in-character perspective gets drowned out entirely by "your character wouldn't know" even though knowing the outcome is not typically a requirement for trying something - like how I don't need to know that someone is going to read a post of mine and change their mind in order to make said post hoping that they realize "a player can have their character do something actually nonsensical but beneficial like triggering a demon's vulnerability to some situation based on their vice and that'd be weird" doesn't prove "it's not fair for a player to use a bludgeoning weapon instead of a sharp one when their character sees an ooze" to also be true no matter how much someone wants to pretend there's no meaningful difference between those examples.

That's why as a GM it's part of your job to translate the rules into things that are happening to bring immersion. Your character generally understands what most of the rules are via cause and effect, you can see those things happening.

Which is why some of the biggest problems that a GM can cause start with trying to obscure what the players are being told.

Often GMs make choices they think are doing one thing which are actually doing another. Like how a GM might view letting players know how many HP their enemies have left as a thing which they don't want to do in a specific matter because that is "unrealistic" and they will not consider that hearing the HP totals is like a very detailed and accurate description of what the character can see which has been translated into clear and concise language for the player that has next to zero risk of misunderstanding as a result. Yet the GM will also not realize that the reason a game like Monster Hunter can "not show health bars" is because the game actually does "show health bars" because that's exactly what seeing differing damage values depending on which parts of the creature you hit and seeing the visual changes in the creature's movements, posture, and even audio is doing - indicating how far along the gradual progression toward capturable or dead you currently are, and how fast you're traveling towards that state.

So some GMs will try to do like Monster Hunter does instead of being like various games that use an actual health bar, but will also not be detailed enough in their descriptions. The result being the players have almost no sense at all how a fight is going and have to hope that despite this they are not misjudging whether they are in over their heads or not. So by avoiding MMO health bars but missing the harder to hit target of Monster Hunter feedback on creature condition, they land at old school Final Fantasy equivalent where the creature's sprite on the screen still looks the same no matter how many turns you've taken and you've got no idea whether there are 200 HP left to go or 200,000 HP left to go - unless you've looked at information you wouldn't normally see in course of game-play (read the Monster stats) or you've used particular magic (though unlike Final Fantasy's Libra, I think PF2 mostly limits explicit HP knowledge to friendly targets outside of currently-in-playtest Necromancers).

And it's a topic that has amused me a bit over the years because at the tables which are trying to keep to a description alone and avoid "health bars" equivalents, many GMs seem not to consider it related that players constantly have to be reminded how things look as they say something like "it's looking pretty rough". In effect having "health bars" despite wanting to not, they are just something you "push a button" to see and then they fade away until you do it again. Meaning same end result but far more effort taken to get there.

I could be misreading this, but it sounds to me you're approaching most tables like you're expecting a purer wargame, and that's just not how a lot of TTRPG tables play.

You're highlighting what I was talking about when I mentioned that the way people that think meta-gaming is a real thing that is avoidable and negatively impacts the game come off as working backwards from the conclusion to prove that to be the case, because none of what I said has anything to do with "purer wargame" or any other particular play style.

And in fact the times that I have seen the most harsh takes and actions as a result of meta-game worrying, it has been in cases where a player was playing their character thinking entirely in terms of doing what seemed sensible in a scenario described to them - and the GM interjecting with "no, you can't do that." with the flawed presumption that "your character wouldn't know that it is a good idea" is the same thing as "your character would think it is a bad idea and try something else first" because the very idea that meta-gaming is avoidable and negative flags every case where the player might know about the game they are playing as "unfair".

I would also say that someone's inability to give a good, clear definition of metagaming for their table doesn't mean there is no such thing as "metagaming."

Okay. I wouldn't say that either. Which is why I said the proof that metagaming isn't the thing many people believe it to be is that no consistent definition that has been given can be applied.

It's not some tables saying "I know meta-gaming when I see it" but not being able to articulate what they think meta-gaming is. It's the description of the process of meta-gaming that people who strive to prevent it from happening can give being equally applicable to game-play that the same people take no issue with.

Whether or not what a character is doing in a given scenario is acceptable play or "bad" should not depend upon asking "is this a new player, or an experienced one?" if the intention is to have decisions be character-based rather than player-based. And the same is true of an experienced player and the outcomes they pick because "you can use what you know about the game to choose something that won't be beneficial" and "you can use what you know about the game to choose to try to have your character learn/remember something which gives you permission to do something other than choose something you know won't be beneficial" are just as much "you only did that because you know" as the action being disallowed by "you can't use what you know about the game to choose something that will be beneficial." is.

Personally, I think "no metagaming" edicts amount to a request that players prioritize a game's narrative cohesion over mechanically optimized play when the two conflict.

And literally all I have ever seen it do is serve as a limiter to experienced player's options and behaviors that less experienced and knowledgeable players are not beholden to and embolden the behavior in which a GM effectively plays in a "no fair, you're supposed to fall for my tricks!" kind of attitude where it seems clearly not to be whether the player was playing their character in a believable way within the narrative that seems to be the problem but that the scenario didn't play out the way the GM wanted to and to force it to have to the GM has declared not doing what they wanted you to do "cheating." and then has made up an impossible to actually not have done explanation for how they are certain you definitely are cheating to distract from the root of the situation being, in effect, "you must play 'dumb'"

You can look at it from the building/characterization direction instead, if it helps: "I want to make a character who's polite, even to their enemies. But I don't feel like optimizing with Intimidate lets me do that."

And there we go with the other classic activity that crops up in meta-gaming related discussions when someone is trying to show how meta-gaming is a real and avoidable negative thing; animated object: goal post.

You set the parameters of the example before I responded to it and said nothing at all to indicate the case was "this character is supposed to polite, even in combat, and the player isn't actually sticking to their statement of that intention" rather than entirely normal behavior for a character with the presumption the "inconsistency" was inherently a problem because it coincided with a mechanical benefit. And now that you've changed the parameters you're glossing over that the parameters you've moved to are not inherently superior to any other set of possible parameters so using them to imply a problem in play is spurious at best. "Someone could play a character that should behave differently" is not proof that a player is behaving inappropriately with their character.

And in closing; I urge you to deeply consider that something which entirely depends on the table being something which entirely depends on the table is proof that it's not a "real" thing. If it's bad faith play, it should be bad faith play at any table not explicitly saying the equivalent of "We like street ball. It's only a foul if you need a hospital visit afterwards." about what they agree is bad faith play but would like to incorporate any ways.

Because treating it as variable and elusive and personal to a group is trying to have it both ways and make it a parallel argument to "There's no one right way to play the game. Except for my way, it'd be perfect for everyone." by saying that whatever a particular person thinks is meta-gaming is definitely meta-gaming, no matter who else might say "no, it's not."

To be honest, calling "metagaming" is usually a way to try to bludgeon disruptive players back into line

In my experience, both in the hobby itself and talking about it in various spaces both on- and off-line over the years, it's not "disruptive players" which are bludgeoned with it in most cases - it's players the GM is incorrectly identifying as disruptive because the inherently-antagonistic presentation of the concepts of meta-gaming results in fair and reasonable play marked as "disruptive."

Like how you can have a DM literally tell the players they are looking at a troll by saying "You see a troll barreling toward you" rather than some description of the shape, size, and coloration of whatever mysterious creature the character sees and yet the player is expected to either spend actions having their character figure out what they are looking at or pick an action the player specifically knows is a poorer choice so that they can be proven to not have "meta-gamed".

I don't think there's a consensus view on what is and isn't metagaming

This is the direct and obvious result of the "meta-gaming is bad and must be avoided" side of the discussion deliberately refusing to accept any coherent definition for the term that can be consistently checked and isn't effectively altered the moment the GM decides what a player did has to have been unfair and their proof is because it was a good thing to do and nothing more.

While the "meta-gaming is actually a fairly useless thing to call out because the bulk of game-play is itself reliant upon meta-gaming and cannot possibly be anything else, so we should really just focus on whether what happened in game was allowed to happen or was cheating" side of things can provide a very clear and consistent definition of the term.

When what the player knows about the game materials is incorporated into the decision made for what a character will do. I.e. the thing which is happening when you choose your method of attack, no matter what you know, no matter what you choose. The other side, however, will insist that it's only actually meta-gaming if the choice you make is one you know is beneficial and it isn't previously established in a specific way that the character also knows that, and if you are actually ignorant of the benefits of your choice or are choosing something because you know that it's not the best choice then that is a completely different thing despite the identical process both in and out of your head.

As to all of your "Fair to ask" questions; nope, those are all stupid and pointless questions to which the answer is "we're playing a game, just shut up and play the game" because you may as well be asking "why do you keep using a melee weapon? Ranged weapons exist and are much safer to use because you can be so far away from your enemies" with how you are presuming that "the fact that this is mechanical advantageous should be over-ruled unless a personality trait I've decided is relevant is present in the character" is a valid stance when the reality is that the mechanics of the character and how they behave are allowed to be the same thing even if it seems like that makes someone a little more inconsistent or unpredictable as a character.

And I mean, seriously. "You're so nice out of combat."? That's a joke, right? I'm a generally nice person. I'll make small talk, smile and wave at neighbors walking their dogs. I tip well. And I don't start any trouble without a good reason... but it's not even a bet, it's a sure thing, that if you put me in a situation anything like combat I am going to do anything and everything to dismantle my opponent physically and mentally so that I can minimize the harm that comes to myself, maximize my chance of survival, and maybe even manage to develop a reputation that reduces the chances that someone that knows that reputation is willing to take a disagreement with me to the level of combat. Behaving in different ways related to the context of a situation isn't just entirely normal, it's also actually reasonable. Which this just highlights what I bring up when the topic of meta-gaming comes around; you didn't even consider explanations outside of "the player chose this for an advantage, and that's unfair" for the situation that happens in play - and if you follow the general process these conversations tend to have had over the decades I've been having, your response to my suggestion that actually everything is totally fine and normal is likely to be along the lines of "well of course someone trying to get an unfair advantage would say that, you're just making excuses for your bad play behavior." because "meta-gaming is bad and should be avoided" is heavily prone to people working backwards from that conclusion instead of actually questioning if it might not be entirely true.

The transfer rule mentioning extra runes a weapon couldn't normally have go dormant is there to shut down the problematic conclusions of A) you can't transfer runes between items that are currently full so instead of being able to swap the +2 potency and +3 potency of two different fully-runed weapons you would have to include a rune stone in the process and transfer the +3 potency off the weapon onto the rune stone no, wait, that's also against the rules because now the weapon has property runes and no potency rune to allow them... which makes the process of transferring be something that can be as simple as it should be instead of nickel-and-diming the player as they take every rune off a weapon onto rune stones to then put them back on to weapons in a different configuration.

And B) if you "transfer" a 4th rune onto an item it works just fine because you didn't "etch" it there, you only "etched" the first 3 and this one is just there because you totally intend to (you promise) come back soon and take one of the runes off.

It's not at all something that we should look at and treat as a reason why when Blessed Armament doesn't stipulate that the weapon you choose have a potency rune and space for another property rune that isn't proof that Blessed Armament is making an exemption.

Basically, the way the rules are meant to be read and understood is that we read the thing we are actually trying to figure out - in this case Blessed Armament - and we read any specifically referenced rules - in this case there are none - and we read any general rules for that aspect of the game - in this case, that is actually the rune limiting rules.

Where some people are failing this process is that we only apply the parts of whatever general rules are relevant that aren't contradicted by the thing we are actually trying to figure out. Which is why the context of not stating limitations counts not as "so those limits apply" but as an exception to those limits - because if this feature requires a weapon to have a potency rune and it doesn't say so then it isn't just "using the normal rules" it is [i]non-functional and misleading[/b].

The feature says, to put it simply, "you get a rune." If the general rules then elaborate upon that as "you don't get a rune" that's clearly a contradiction and thus proof of exception being necessary. And that's just obvious when you ask "what happens if you pick a weapon with no potency rune?" that the answer isn't "you can't do that." because the feature says you can.

I always assumed characters new how their mechanics work so s rogue knows that they are good at taking advantage of an enemy bring distracted by an ally.

This is one of the things which I think shows how what the hobby treats as the traditional view on what meta-gaming is and what should be done about it are rooted in inherently GM-versus-players mentality.

To the most concerned about meta-gaming, the mechanics of the game are genuinely off limits to base any decision upon.

To everyone else the mechanics of the game are simply out-of-game representations of in-game details that would be genuinely absurd for a person not to have any sense of about themselves.

Like a rogue having no idea why they want to grab a shorter, lighter weapon than their burly ally prefers to use because "characters don't possess any knowledge of the game's mechanics."

As to why the change leads folks to thinking we lost an extra property rune. Its the difference between getting a rune (which would follow rules for runes on weapons) and gaining the 'effect' of a rune which doesn't actually give a rune but only the benefit of it.

The explanation for the thinking doesn't make any actual sense as a result of being inconsistent, though.

You state that people were able to parse the difference between gaining "effect of a rune" and having the actual rune, which implies a degree of ability to understand how things can be implied by the words chosen rather than needing to be explicitly stated because what actually is the effect of a rune is not a fully defined parameter the book provides to us. Then that ability is entirely absent when instead parsing what the text which says both "Select one weapon or handwrap..." without a limit that the selected weapon must have a potency rune (thus making it an explicit statement which disagrees with the rules that would limit how many runes a weapon can have, so a "specific trumps general" case) and "...you grant the armament a property rune..." which is just as much of a distinction as "it says "effect" not the actual rune" because it says you not the weapon.

So I persist in my belief that it is not the current wording itself which is cause for the belief that the rule is any different than it was, it is a comparison of the current text to the previous text matched with presumption the reason for altered wording has to be altered meaning. Synonymous phrases are allowed to exist in the game, though, so that need not be the case.

"If it is genuinely what your character would do, and it's still disruptive or not beneficial to you... create a better character."

No matter what it is that a character would do, the character is still entirely up to the player to devise, so there isn't actually any "it's not within my control" element like the claim is implying to be the case.

It is circular reasoning of this being what you have chosen because it is what you have chosen being presented as if it were some kind of point of integrity.

Well correct me if I’m wrong but it looks like the next step is for Maya to confirm for us how this works and if it’s intentional.

And this would be why when I saw that Maya had responded to someone's inquiry with a definitive answer as was done, my only thought was "oh no... here we go again."

This is what always happens when someone presents the potential for a "truly official" answer; some people will argue against anything and everything else no matter the quality of the reasoning behind it or the clarity of cited evidence so that literally only "official comment" counts for anything.

And after "official comment" is made, what happens then? Somebody says the official stance is bad, if not also continuing to insist it is actually wrong.

I think it’s pretty clear cut that it takes a slot and is worthless...

Then you have two questions to answer;

What positive evidence leads you to the conclusion? For clarity, I mean which words that are present in the feature itself indicate to you that your conclusion is the clear one, and why.

And why would it be worthless on purpose with the game including guidance telling us to make stuff work with our group instead of sticking to strict wording in the book? By which I mean to question you're entire ability to believe that you are correct when you actually want to be incorrect.

The most likely reason why Disable Device wasn't written as a general skill action is because of what NorrKnekten mentions; the variability written in about difference of traits or requirements for the action.

By which I mean that if you look at things which are general skill actions they are following a pattern in which everything except one variable is constant so that you are at most dealing with one trait that fits the associated trait involved and the blank that is which skill to check being filled with a new skill name.

So Disable Device would have necessitated a lot more word count to cover how and why the variables might change and would end up in a position of either literally every possibility is explicitly covered (and any hazard that falls outside the pre-defined action parameters has to be errata'd to fit inside them) or some hazard still manages to fall outside of the rules covered in the description and cause confusion.

Why change the words, and then change them back in Battle Harbinger, if not to change the meaning?

You're presuming that a difference in wording was a planned thing. That's rarely the case when more than one writer is involved in writing something and no one is explicitly doing the job of checking every wording to make sure any time something is said it is with the exact same phrasing.

The game includes a mention that sometimes a rule will be referenced by a rule that interacts with it and sometimes it won't, yet the generally established case still applies even if it isn't referenced specifically because the writers don't want the readers to assume a difference in words used must be interpreted as a difference in meaning.

No restrictions are mentioned here, but a lack of restrictions is also not mentioned here. That means the only things we have to go on are the existing rules for Runes, and the fact that the wording was changed.

We also have the game convention guidance on ambiguous rules that tells us, to paraphrase, not to stick to a wording's strict outcome if it makes for an unusable ruling.

Which not having any coverage of what happens should a champion attempt to use their blessed armament feature on a weapon that the general rules would not allow a rune to be added to unquestionably is.

The rune rules aren't vague and have restrictions. These rules don't have anything in them to suggest they ignore those rules anymore, whereas they used to.

At this point, the main thing I have to go on to suggest the intent didn't change is that the new feature is "too bad to be true".

It is true that the rune rules aren't vague and that they have restrictions.

It's also true that the effects of blessed armament aren't vague. What's not true is the part about suggesting an exemption to the rune rules. The new text does suggest the normal rules don't apply because it says "select one weapon or handwraps..." rather than saying "select one weapon or handwraps... which has a potency rune", and by not re-stating the limit.

What it is that the wording no longer does that it use to is explicitly state not to follow the normal rules. And the only reason for any confusion is comparison between the two phrasings as there is literally no room in the new wording for rune rules to not be excepted by the wording used.

Truthfully, I think the rewording was done to reduce word count and the rune count confusion is an unintended consequence.

The rule is you can only etch a number of runes onto a weapon equal to its potency rune value. But this is not etching a rune, it is being granted by the spirit.

That's what I was meaning when I said that if we didn't have that original version of the text I don't think we'd have people expecting that the limit would apply.

For me I feel like if we'd have never had the first wording we'd have two groups of understanding of the current wording:

Group A being the people that are sure that it doesn't count against rune limits because that feels like a feature that you could end up feeling is useless if the GM happens to hand out a bit of treasure that you end up using that is already rune-filled, and find extra confidence in their conclusion from the lack of mentioning the details of how an already-full-runed weapon and this feature interact (pick a rune to have be "turned off", the whole item shuts off, you choose between what the item actually has or what you can effectively provide it, etc.). As there is effectively a lack of information explaining how besides "it just works" to handle the situation.

And Group B being the people that are either feeling sure about that it counts as a rune but might confront problems from the mentioned lack of information later on if the situation even comes up, or are already in a state of thinking they know how it is supposed to work yet are also aware the text doesn't cover that functionality explicitly.

So mostly the reason why we could use a clarification in the FAQ is to make sure that people aren't having a bad experience as the result of making up some of that missing information in a way that their group isn't actually a fan of. And until then we should all stick to the advice given for when rules seem to cause problematic or nonfunctional outcomes and not stick strictly to "it doesn't say it does let you have an extra rune" and instead stick strictly to "it does not explain what happens if you do the thing you theoretically aren't supposed to do, so it just works."

I like it for flavor, but in terms of power I'm a little torn.

Because of the level the feat is available and how treasure guidelines work it is behind the level at which a party might already have found the equivalent item as treasure, including at each of the levels that it upgrades.

That means that the altering what the weapon is and the unlimited mundane ammunition factors of the feat are meant to carry the difference and I'm not entirely certain that is enough for the opportunity cost of a class feat since use of weapons is not something the class otherwise shines at. And much of the point of the feat can be covered in a limited fashion by using the runic weapon spell.

I don't really have a clear idea of how I think it could be changed to be definitely worth the investment though, since most of the basic ways in which a character would be more encouraged to use the weapon could easily over-shoot the mark.

Guntermench wrote:

They want to avoid you being able to put all your eggs in one basket and outperform the people that didn't.

This has been a running theme of this edition.

I don't think DMurnett is asking to outperform others. It's more like asking to have enough eggs to choose from that you can fill your basket with all brown eggs, all white eggs, or a combination of the two

The tricky part comes when you have three, four, or perhaps even more varieties of eggs, and you may not have enough page space room on the egg selection table to support all those options.

The issue with specialization becomes that if you gain something for choosing not to have a broader range of stuff you do, you pretty much must outperform someone that chose a broader spectrum. Because if it's not "better this in exchange for worse that" it is just going to be the current case of not having an upside to restricting your selections.

That's the nature of the very concept of specialization in games, and is actually the whole reason why Paizo really doesn't steer most classes into being specialists - and especially not in the "I picked what I wanted to and I could have chosen differently" style where-in the player specializes in the thing they intend on doing at the expense of the thing(s) they aren't interested in and the game makes that "the good choice" instead of causing yourself problems.

Personally I'm perfectly fine with invisibility eliminating every "you can see" option.

So am I.

I feel it's inconsistent to not treat concealed as "kinda can't see" if you're going to have the observation-interfering conditions apply in any case though, since as another poster linked to the game actually means "perceive with a precise sense" when it says "see" so there already exist in-game examples where something invisible is actually something you can "see" through another sense.

Context found everywhere other than people's presuppositions as to what a "magic missile" does indicates the game treats concealment as a chance that you can't "see" well enough for it to count.

Specific only trumps general when it is being specific about doing so.

Which means that not explicitly stating concealment does not apply is not specific enough to change the general rule that you make a flat check if your target is concealed from you.

The part of this debate which I always find interesting is that people are willing to bend the heck out of what "automatically hits" means in order to bypass concealment, but if the target is hidden/invisible they jump right on to twisting words so that "you can see" isn't take as literally as they want "automatically hits" to be.

Mmkay. Yeah, "everything's concealed" doesn't mean you're blind.

Ah yes... because the GM needing to change how they describe things (the thing I said) is the same as your character being blind (the thing you're putting in my mouth).

Nuance really is dead on the internet.

My point is that the GM, especially if running an AP, has a way they intended to describe an area. That description can end up providing information different than what a character would reasonably have, whether it's "there's a green hand painted on the white flag" that should actually be "there's a hand painted on the flag" because darkvision isn't in color (except for when it is), or it's providing details that should be less certain to have been noticed because the flames oracle is cursed to perceive the world differently.

And since the curse is such an integral part of the identity of the class, it seems weird to me if anyone was satisfied with not having it impact the game in every way the mechanics implied that it would. Especially if those people are complaining about the impact of curses being reduced with the remaster version.

>without the whole of the campaign being skewed to account for it, at least

Yeah, I'm gonna have to call citation needed on this statement you keep making. Who hurt you? My curse literally never disrupted the campaign nor required anyone to cater to me. Has anyone else experienced this?

Flames curse in a campaign that isn't hard-locked to close quarters.

Sure, I'm being mildly hyperbolic, but it's just like the old "we have to rest because the caster is out of slots" in that the old curses required special consideration outside the standard for a campaign. I bring up the flames curse because it's one that requires the GM to constantly be altering the descriptions from what they would normally say to what is actually visible to the flames oracle - like the "I have darvision" meme, but in reverse because the GM probably told you something you actually don't see.

Idk, if monster stats are made with the assumption that the item bonuses are there then I don't think numerical bonuses from gear should be a thing. No power from items, just options. The rest of PF2e's entire paradigm is predicated on the chargen build math being out of your hands so item potency seems like a vestigial sacred cow....and I'm always down for tasty burgers

It literally is vestigial.

Its inclusion in PF2 is the result of Paizo asking (the wrong) questions during the playtest and acting on the feedback that they received. The problem is that they asked something along the lines of if people liked magic items being powerful and they received feedback saying yes - but they didn't also ask the important part as to whether people still wanted powerful items with the knowledge that they would not be outside the balance math.

Which is why we get potency runes that you can't do without in the long-term and even more can't get by without striking runes even though even the people that wanted powerful magic items would rather skip them if they're actually required to hit the expected baseline.

Old curses were having strong impact but were coming with strong bonuses.

That's the problem, though.

The bonuses you were supposed to want came alongside the penalties that prevented the class from actually being functional - without the whole of the campaign being skewed to account for it, at least.

A perfectly played remaster Oracle should never engage with their curse

That's just actually wrong because, unlike the prior curse mechanics that were always more bad than good for you despite having really strong benefits, the new cursebound stuff is actually mostly upside given the new curses are actually rather tame.

Plus it's just asinine that we're in a conversation in which someone else is telling me "well then you really didn't want to play oracle in the first place" and you're talking about being dissuaded from using your unique class options because of the minor penalties that come along with it.

Also, equating a rather general backlash to a case of No True Scottsman sounds like an oversimplification, don't you agree?

The oversimplification here is that you've taken my specific response to the specific case of me being told that where I thought I was talking about people that want to play oracle but couldn't because the old mechanics got in their way, I was actually talking about peopel that weren't interested in playing oracle, and decided to pretend that I'm saying that's the only form of people liking the old oracle better.

...but like a third of the curses are so bad you'll rarely want to risk them.

This is exactly where people insisting former oracle was "better" lose me.

All of the new curses are far easier to tolerate in practical campaign scenarios than the former curses are, but there's some kind of mental block making it so that where new curses can be bad because they're hard to deal with old curses are good because they're hard to deal with and that doesn't register as nonsense.

Turning the whole discussion into a kind of No True Scottsman because anybody that had a problem with old oracle's mechanical implementation, and apparently also anyone that thinks the new oracle actually does have the same lore despite mechanical differences, isn't a real oracle fan.

In other words, someone who doesn't want to play the oracle. Like I said.

Now you're arguing semantics, if giving you the benefit of the doubt that you're not actually trying to just be deliberately obtuse.

The old version of the class caused hurdles that had to be dealt with in order for anyone to play it and it not be objectively worse than any other available option - so it's basically just gate-keeping to say that only people that went through with playing it anyway "want to play the oracle".

It's not "I'd like to play this class if its mechanics were completely different". It's "I'd like to play this class but it kind of just doesn't really work without being given special treatment" and the fix for that which Paizo came up with was incidentally significantly different mechanics.

...the remaster was clearly aimed at appeasing people who never wanted to touch the class in the first place.

That's kind of an unfair statement.

You're downplaying the people that absolutely did want to touch the oracle, but found it too complicated in terms of making the character actually function within the scope of a campaign that is not catered specifically to them.

The idea can be appealing while the mechanics do more to get in the way - especially once the change in refocus rules made what used to be an advantage of being an oracle no longer applicable.

Just like how many people had issues with the superstition instinct of barbarian because it put a larger degree of burden on the rest of the game around that player's character to make the character fully functional, the pre-remaster oracle was an "I wish that weren't such a pain to make feel good in play" option for many people.

So even if the design was aimed at people that didn't play oracles previously, that doesn't mean it wasn't aimed at making oracle appealing for people that like the idea of the class.

So, by your own admission, the HP of monsters increases proportionately to the damage increase brought about by property runes at those levels?

No. The opposite.

The increase in HP of monsters appears to occur at a steady rate despite that player damage increases occur at particular level ranges.

There is no evidence of an increase design to counter-balance acquisition of a property rune.

If damage runes were part of the baseline there would be an extra increase in creature HP at the levels that they become available, not a steady rate of increase, and especially not a steady rate which trends toward smaller and smaller increases at every level.

Damage runes are absolutely not factored into the assumed baseline.

You can look at the creature building guidelines and see the HP values at various levels and then details like moderate column at level 7 to 8 the maximum of the range goes up by about 20% and then from 8 to 9 goes up by about 20%, but the leaning of those "abouts" switches direction because it goes from slightly more than 20% to slightly less than 20%, where the opposite would be true if the higher damage capability of using property runes that do damage rather than any other property rune available (because you can't actually have both) were influencing HP values.

ABP is in a position where it is both under- and over-stated.

First, it never even remotely claims to be a replacement for all of the magic items in the game, just for the ones that it says it is a replacement for (and tells you not to include if you're using it)

But then it also gives out more than magic items would ever actually give in a standard-rules game because the skill bonuses are more numerous that a player would likely actually choose to have, more potent in at least a few cases because some skills don't have an item in the books that goes up to a +3 bonus, and broader in their application as most items add to a particular skill for particular uses rather than a blanket bonus to every use of the skill. Same goes for Perception bonuses, which ABP presents as a blanket bonus for all Perception checks for all characters where in a standard rules game most characters wouldn't end up with a bonus to Perception at all, and most that do have one would have it be limited to vision-based Perception checks.

So people shouldn't treat the chart as being a list of "must haves", nor as a exhaustive list of what you get if you choose to use the variant rule.

With D&D 5e all the reasons a campaign can fade before reaching higher levels exist.

With PF2e all the reasons a campaign can fade before reaching higher level except for the game mechanically collapsing exist.

As a result, there's a touch more "we made it to high level" moments to be found in the PF2e sphere. It still takes finding a group of people that can keep their schedule well enough to keep their interest and make progress toward that point - a thing I personally struggle with because I'll have a campaign running fine and then be suddenly struck by an unshakeable desire for a complete unrelated thing (often a completely different game) that starts competing for all my mental attention and I usually end up starting out planning it on the side as a "when we're done with our current thing" but it often ends up being that I mention the new thing to the players and they say "let's just do that."

Or I get to a point where I can't figure out what comes next because the new idea won't get out of the way and I have to call the end of a campaign so that I don't run poor quality sessions trying to force it to continue.

...I'm not sure what character would be excited to use a karambit.

A finesse-based rapid attack build that either specifically wants bleed damage (great in campaigns that feature mostly living creatures as opponents) or doesn't have any critical specialization access.

The weapon is a pretty specific intersection of things being a 2-damage type "crit build" knife that is both agile and finesse. So it has a noticeable niche that it fits into, it's just down to whether a player wants to play in that niche or not.

If you're using a d4 weapon, it should be because it's got traits that you are frequently making use of - or if it is a backup weapon for a just-in-case scenario that happens to have come up.

Which is to say that I am not in the position of having never seen someone make the choice to use a d4 weapon. Many players pack a dagger "just in case" but something like a whip can easily be a focal-point of a build.

And I think it's pretty amusing that most of what's being said against treating d4 weapons as viable is basically "if it's not the best, it's useless" false tiering.

Giving the Wizard a 5th slot and doing nothing else wouldn’t fix any of the problems with the class.

It would successfully make them unique. But I would rather have a class more with more mechanical depth and interesting mechanics than just a pile of spell slots.

The Wizard should be so much more than just Generic Spell Slot Man.

While I am mostly of the opinion that there's not a significant problem with the wizard class that needs fixing...

I agree that just throwing more spell slots at it wouldn't really change the situation much. It's not actually the spell slots that are making other classes appealing in ways that makes people question "why play a wizard?", and even if it would make the class more likely for someone to play it I think it falls in the same "yeah, they'd probably jump to the class if you gave it double HP too" boat of stuff that isn't really a good idea even if it does accomplish the goal you're looking for on a surface level.

Where there is currently room to expand the wizard and make it a unique and interesting class... technically wouldn't be entirely unique because a significantly high-level other class could use multi-classing to get it too; feats.

Player Core started us down the road toward wizard being a unique sort of "master of the arcane" by adding in a couple of spellshape feats that do nifty things - but we could certainly use more, and it wouldn't be a horrible change if the wizard class were actually given some interaction with them by default rather than only if you pick a particular thesis.

At least that's my opinion, as spellshape feats tend to have that "I know magic better than you do" kind of feel to them.

On side note can somebody explain why Wizard still get less basic trained skills than other intelligence casters even after Remastered.I fail to see any reason behind that

It's one of the weirdest legacy elements left in the game since it was one of the various creations of the D&D 3rd edition team that has just stuck to the game since for some reason.

I've always been a bit confused by it since it clearly wasn't a "well, there should be some downside to casters since we've given them so many other massive buffs" from the design team at the time since it only affected wizards at the time. So it seems like there was some thought that high-intelligence characters should be skilled, but not so skilled that they look more skilled than the "skill focused" classes.

Which is how anything with a heavy focus on having a high intelligence score ended up stuck with a base of 2 skill points so their likely-to-be 4 more from intelligence didn't overshadow a bard's 6 point base or easily match up to a rogue's 8 point base.

I think the only reason that legacy has survived is because the optical illusion that they have a comparable numbers of skills that happens when building an int-based character with a +4 intelligence and any other characters with a +0 intelligence.