In formal English, the comma is just wrong. Informally, I agree it does a very effective job of making the message get across that way.

No, they have nothing to do with the style of play. They have to do with group dynamics, which is an entirely separate thing.

I actually haven’t ever used them myself. I’ve only played with people I already know or people that those people are vouching for, and I do a solid session zero to establish campaign content and tone. But it’s who I’m playing with and the fact that we’ve discussed it that’s relevant there, not whether we’re playing heroic fantasy romance or dark gritty realism.

Because they’re valuable whether you’re doing sexy romance or gritty realism or something else entirely. They don’t factor in with the “various styles of play are all equally valid” conversation.

Safety tools shouldn’t be lumped under style of play, IMO.

What did it say?

fyi you can put alt text on an image by putting it between the square brackets

![alt text here](url here)

Might not be a great option for long and detailed alt texts describing all the text in a comic, but for something simple like this it’s much more convenient for people with screen readers.

That’s definitely at least a 2nd rank spell.

In Australia we call them “seppos”. Short for “septics”, which comes via rhyming slang from “yank” -> “tank” -> “septic tank”.

Reread the comment you replied to. Not one word of it was in there accidentally.

The lack of dnd-style multiclassing in Pathfinder was something I struggled with at first, but honestly now (especially with the “free archetype” optional rule) it’s one of my favourite underrated things about having switched. It’s not as flashy as the 4 degrees of success or three action system, but it’s a really great system.

Oh yes, that’s a very good point, actually. That actually seems such a fundamental use case that you could almost justify it being available without a permission.

What, like this?

Oireland (pronounced that way)

Is that meant to be making fun of Trump’s accent? Cos I gotta be honest, it comes across to me more like a representation of how Irish people pronounce Ireland. At least, the way I pronounce “oireland” when I see it sounds to my ear much closer to how Irish people say Ireland than to how I say it.

They already have radio and a fairly sophisticated local network. They could definitely do that if they wanted.

Maybe, but I’d like to see a concrete example of how they are “designed to talk to each other” that couldn’t be achieved by the extension just reading the DOM.

I agree with you about dropdown menus being something that could/should be natively available to HTML, but I’m less convinced about form submission. Sure, if we assume everything is happy path it’s a great idea, but a system needs to be robust enough to handle a variety of cases. Maybe you want to redirect a user to a log-on page if they get back a 401, or present an explanation if they get a 403. A 5XX should usually display some sort of error message to the user. A 201 probably needs to add an element into the page, while a 200 might do nothing, or might alter something on the page.

With the huge range of possible paths and desired effects, it pretty quickly becomes apparent that designing an HTML & CSS–only spec that can meet the needs is infeasible. There’s definitely a case to be made that JavaScript has become too powerful and can do too many potentially dangerous or privacy-invading things. And maybe a new range of permissions could be considered to limit a lot of that at a more fundamental level. But what we’re talking about here with the form submission stuff is the real bare-bones basic stuff JavaScript was designed to make easier—alter the contents of web pages on the fly in response to user actions. And it’s really, really good at that.

• Your operating system
• Your CPU architecture

Agree. No reason they should have this.

• Your JS interpreter’s version and build ID

I can see a reasonable argument for this being allowed. Feature detection should make this unnecessary, but it doesn’t seem to be fully supported yet.

• Plugins & Extensions

This is clearly a break of the browser sandbox and should require explicit permission at the very least (if not be blocked outright…I’m curious what the legitimate uses for these would be).

• Accelerometer and gyroscope & magnetic field sensor

Should probably be tied to location permission, for the sake of a simple UX.

• Proximity sensor

Definitely potential legitimate reasons for this, but it shouldn’t be by default.

• Keyboard layout

As someone who uses a non-QWERTY (and non-QWERTY-based) layout, this is one I have quite a stake in. The bottom line is that even without directly being able to obtain this, a site can very easily indirectly obtain it anyway, thanks to the difference between event.code and event.key. And that difference is important, because there are some cases where it’s better to use one or the other. A browser-based game, for example, probably wants to use event.code so the user can move around based on where WASD would be on a QWERTY keyboard, even though as a Dvorak user, for me that would be <AOE. But keyboard shortcuts like J and K for “next”/“previous” item should usually use event.key.

There could/should be a browser setting somewhere, or an extension, that can hide this from sites. But it is far too useful, relative to its fingerprinting value, to restrict for ordinary users.

how sensors are used to fingerprint you, I think it has to do with manufacturing imperfections that skew their readings in unique ways

It’s also simple presence detection. “You have a proximity sensor” is a result not every browser will have, so it helps narrow down a specific browser.

Though for area damage spells, it’s much, much more complicated.

That’s an optional variant rule described in Xanathar’s Guide. The default rule for grids is simpler: just do Chebyshev.

Ah right, so “diamond” (depicted as a square rotated 45 degrees) is Manhattan, circle is Euclidean, and square is Chebyshev, then?

As it happens I’ve just looked up the 5e rules for this for the sake of another comment, and their rules are that, like PF1e, if you go vertical, you follow the same rules (i.e., Chebyshev by default, optional alternating) as on a flat plain.

I’ve not looked up the PF2e rules, but I feel safe in assuming it’s the same in this regard as 1e.