From what I understand, players were scored individually. So those players who convinced the others to take on the dangerous parts fared better.
I scanned through the 1e DMG and PHB, but I didn’t see anything about a base chance a trap does not trigger. These two traps, the needle and the pits, have their specifics listed in the module.
The needle trap is always found if the box is searched, and always triggers if precautions aren’t taken. It harkens back to skill play, where the player is meant to find alternate means instead of rolling dice. It’s like how the west false entrance specifically says there’s no saving throw.
The pit trap does have a percentage chance not to fall in, but it still triggers. Being as the pits are 10’ square I do enjoy the idea of catching multiple PCs at once. And that was possible back in the day with how turns were organized, which I’ll cover in my next post.
I definitely agree about the the HP and other resource management. I’ll be covering some of that in my next post.
Those late 80s, early 90s network sci-fi shows are a special kind of train wreck that I love.
One of the later seasons of Earth Final Conflict. They built up the female support role to be this tough brilliant independent woman who didn’t need no man. Then when the male lead left the show and she took the lead roll they immediately had her fall into a romance with some no name character that wrecked her confidence.
On the reverse, Sliders, the male lead and female support had this will they won’t they for a bit, but then in an awkward scene later between the two support roles she relates that off camera they had “the talk” and said they weren’t an item with no real feeling about it.
This is a great read. I’ve worked on software my whole career that wasn’t designed to kill someone, but could quite literally kill someone if it wasn’t correct. There’s a weight that comes with that kind of responsibility.
We were all cheated my friend. We were all cheated.
It was a good read, but holy fuck did vice’s website crash 20 times trying to read the last two pages.
How should a contributor gauge whether to make big changes to “do it right” or to do it a little hacky just to get the job done?
When you work in enough diverse codebases, with enough diverse contributors, you begin to understand there isn’t one objectively right way. There are many objectively wrong ways to do something. Picking a way to do a certain task is about picking from tradeoffs. A disturbingly common tradeoff is picking rapid development over long term maintainability, but that isn’t not the right way to do it in a competitive space.
Needs change over time and certain tradoffs may no longer apply. You’re likely to see better success making lots of little hacky fixes until it’s not a hack anymore because you’ve morphed it slowly over time.
Version control, git et al, allows you to make multiple commits in a single PR, so you could break the changes up to be more reviewable.
Hear, hear! I would add that it multiplies again, again when other people are actually using the product. Engineers famously build tools for engineers which can leave something to be desired for the layman.
My experience, ymmv, the most work went into configuring everything you need or want the first time. The right drivers for your graphics card, for your webcam, wifi, acpi multimedia keys, etc. Though I don’t use a gnome/kde/DE, so some of that may automagically work for you. After that though, updates don’t tend to break the things you’ve already fixed.
One time in 5 years the names of some acpi keys changed, and I had to update the script, and that wasn’t really arch’s fault. Also Google did a funny thing with their monospaced font that xft couldn’t handle, again not an arch specific thing.
And here’s a hot take for you, I only update about every 18 months. That’s usually how long it takes Discord to become binarily incompatible with installed libraries. Update the keyring first and never a problem.
I too have had idle thoughts about what lessons to pass on and what was lacking in my own formal education.
My elevator pitch is to have a semester long project broken down by feature. You get a couple weeks to develop, but after each one is complete you have to trade code bases with someone else in the class. It’d teach both how to work in an established code base, and how to be kind to some future maintainer (who might be yourself).
I’m not going to dig into the details because I can’t convince you your experienced reality isn’t real. Paranoia can stem from delusions, a key factor in your story is that most people, even those close to you, aren’t backing up your experiences.
I’m a stranger on the internet, so take what I say with a grain of salt. I was into your story up until you said planes and helicopters were flying low over your home. It sounds like you may suffering from some level of schizophrenia or other paranoia related condition. Get evaluated, or don’t, but I hope you find peace.
Now kiss 👉👈
Maybe this goes a bit deeper than the question intended, but I’ve made and shared two patches that I had to apply locally for years before they were merged into the base packages.
The first was a patch in 2015 for SDL2 to prevent the Sixaxis and other misbehaving controllers to not use uninitialized axes and overwrite initialized ones. Merged in 2018.
The second was a patch in the spring of 2021 for Xft to not assume all the glyphs in a monospaced font to be the same size. Some fonts have ligatures which are glyphs that represent multiple characters together, so they’re actually some multiple of the base glyph size. Merged in the fall of 2022.
Ah, the dichotomy of Dad groups vs Mom groups. You’re judging @[email protected] entirely on one tiny happy insight into their life. Maybe their kid has underweight struggles and calories are calories. Maybe by everyday they mean everyday they have them every other weekend, but that’s too painful to say. You don’t fucking know, and this isn’t a life advice thread. Celebrate they have a kid they want to be involved with.
I appreciate the reference. I do always want to credit the original artist. It’s unfortunate that a Meta login is required to see it.
Either I have a headache or some form of red/green blindness I wasn’t previously aware of.
The limiting factor in 1e, discouraging long resting in the dungeon and using spells to recover hp was random encounters. The Tomb unusually does not have random encounters, but you’re not supposed to tell your players that.