• 0 Posts
  • 9 Comments
Joined 3 years ago
cake
Cake day: August 6th, 2023

help-circle
  • I know you kid, but rolling without the DM asking you to is a dick move and a faux pas at a table. You really shouldn’t do that. Same thing happened with Critical Role and the “roll for scry” moment. It puts the DM in a position where they might have to confront you, deny you the roll and sour a moment. It puts pressure on them to allow you to do something, which players often abuse - someone spins a tale of doing a quadruple backflip, landing on someone’s head, attacking and bumping the dude into lava, rolls before the DM can say “there is no lava nearby but…” and puts them in a really awkward situation, especially with high rolls.



  • The shitty part about that system is people want to be powerful so they make characters that usually fit within their class. Meaning dump stats. And suddenly the barbarian, with an int of a sapient rock, has an idea but cannot voice it in character because their char is “stupid”. The exact opposite for mages or bards - the bard is a “face” that talks to everyone for the checks. Worse yet with charisma checks - a dude that doesn’t know how to be as charismatic as a 20 stat bard, suddenly needs to be a smoothtalker (since charisma is treated differently in many tables, it’s not just “I try to distract the guard by talking at him”, it’s “I tell him XYZ”)


  • This was a complaint I heard from friends about D&D. Them going “Dude this game sucks. You as a bard get a cool spell that lets you roleplay and I only get shit like magic missile”. To which I went “What shape are your magic missiles? Why doesn’t the cleric’s summon a folding chair? Why is the warlock’s pact just some random devil, and even then you don’t roleplay anything with it?” like the insults don’t come out of nowhere most of the time. Don’t get me wrong, I am insanely quick on the draw. But prepping a database of insults when it’s needed is part of the fun for me.


  • Ye, that’s the difference between pen and paper and a game. Unless it’s a singleplayer experience, gating stuff behind story progress doesn’t bode well with players and ends up generating less repeatable gameplay. But for pen and paper, you have a DM that can adjust on the fly. They can give out a level for a daring escape, they can give inspiration based on player behavior, they can have a talk with players and hear their expectations on how their character should perform at this stage (i.e. “we have slain a dragon, and my dude is a paladin that isn’t strong enough to wear a damned shield!”). They can give magic items that introduce novel ways to play a character. A game isn’t advanced enough to do that yet.




  • Who tests the useless survey? Everyone with regression tests. Like dude, everything you talk about has been written “in blood” from years of hosting production systems. If the useless survey is needed, then write a test for it, or a testcase to manually try it. Don’t just upgrade, see that the app is up and push to prod, that’s not testing, that’s asking for trouble.


  • Okay, let’s be angry at the company and frown a lot at what happened. Gurr, bad company, evil.

    And now think of what you’d rather have - a working system, or a reason to be angry? If you have something that integrated with something else, lock it down at a specific version so you control the upgrade and know those versions work 100% of the time together. “Latest” is just asking for trouble - be it in a docker image, in dependencies or elsewhere. It’s absolutely not a “best practice” if it isn’t even a code smell or an outright bug. You could’ve had a slightly outdated version, which won’t be “exploitable” - you wouldn’t have enough time to exploit anything in that time, especially with smaller companies and obscure exploits.

    Instead of putting out the fire, you could’ve been now looking into the upgrade, seeing on UAT or Test or whatever that forms aren’t supported, chilling till they are supported or complaining that they aren’t.

    Upgrades breaking shit is like programming / devops 101, and a huge reason for technical debt in very old projects. Leaving all that to chance is just irressponsible.