It might be your least favorite part of DnD, but there are plenty of people (myself included) who enjoy meeting a new group of characters and finding out about their particular ticks and specialties.
Was gonna say it. This perfectly describes the last few Assassins Creed titles. Not bad enough to put them away, but also not good enough to leave any kind of lasting impact.
Because of a simple yet very effective technique I call: "Asking them". I suggest safety tools for each new group I DM and to this date, all but one group have been open to the idea but after a quick discussion every single player told me that they see absolutely no use in having them and that they will let me know if they ever feel like the topics are getting too rough for them.
BTW, the one group that still has them active pretty much forgot about their existence. I'm a player there and as far as I can tell, the GM is the only one who really wants them.
It all comes down to group composition. If you're comfortable around the other players and the GM and know that you can just say "stop" whenever, then safety tools add nothing to your experience.
It's probably a target audience thing. People who need safety tools rarely like gritty realism because it tends to contain a lot of potential trigger points and people who lile gritty realism usually don't use safety tools because they either don't have triggers or dissociate fantasy rp enough that it doesn't trigger them.
So, it's more of a correlation vs causation thing.
I think you misunderstood. I have nothing against safety tools. I just stated that the majority of players neither use them nor need them and if your group doesn't include a single player who needs safety tools, then there really isn't a point in having them.
Im not carrying a spare tire while hiking. Doesn't mean I think that spare tires are a bad concept in general.
So, you're just disagreeing based on semantics? In that case sure. Safety tools are a group dynamic thing and not a style of play thing. No argument there.
Yes, they do. Believe it or not, but most groups I play in have no use for safety tools. They're great for people who need them, but absolutely unnecessary for others who don't have a problem speaking up when they dislike something and who don't carry around significant amounts of trauma.
Fun fact, in a Campaign I'm playing, my Fey Bard simply "stole" the Deadname of our Cleric and now she has a total of four names and it's awesome for everyone 😄
Pretty much everything you just noted is incorrect! The ecosystem is a giant cestpool of badly written annotation hell, there is no usable documentation whatsoever, The tooling makes the experience barely better than living hell and writing Java feels like doing things worse than any other programming language out there because the language devs have severe C++ PTSD and refuse any useful programming concept from that language outright!
Last of Us 1 was really good. But the second one was so bad, it kind of ruined the first one for me as well. And I wouldn't call it masterpiece. Because for me a masterpiece shines in gameplay, narrative and atmosphere. The Last of Us' gameplay serves its purpose, but there's really nothing special here compared to e.g. Elden Ring, were story, atmosphere and gameplay are all pretty much perfect.
WTF is everyone going on about proprietary? The entire thing is under Apache 2.0 license. Where the hell do you even get the idea that Typst is proprietary?
Yeah well, too bad. Even open source needs money. If you don't want to support the team, then don't. But quit whining. Typst is completely Open Source.
Their business model is providing a cloud hosted platform for your projects. But if you don't want that then you can just run it offline on your local machine.
I swear, some people here remind me every day why a significant portion of the population hates us leftists!
I would say the general design philosophy. It works pretty much perfectly for what it's supposed to do. But the strong suit of LuaTex is that it can execute pretty much any code you want. So, you could in theory execute a fluid simulation each time you compile your document and insert the result as an image. The Typst Scripting language obviously can't do that because it's locked into the typst sandbox.
My particular use case is that I have some data accessible via an open API and I would love to skip the step where I update the data CSV every day or week. So, not really a breaking feature, but nice to have nonetheless.
I've completely switched over to Typst and it's so much better. All of the typesetting capabilities of LaTex but without 99% of the headache. Now all it needs is all of the neat little edge case extensions that LaTeX has gathered over the years. And possibly a real scripting language interface like LuaTex.
It might be your least favorite part of DnD, but there are plenty of people (myself included) who enjoy meeting a new group of characters and finding out about their particular ticks and specialties.