It did, extended memory came about the same time we needed to show down the system

I give my players pretty wide latitude, after a few sessions they generally agree with me if their character isn’t working well. Too weak can be treated with better weapons; too powerful get bored and go home. One of the too powerful synergised two powers to become practically invulnerable

I’m not going to trust the rules given to me by a guard who might be the one who lies

https://xkcd.com/246/

Mobile: https://m.xkcd.com/246/

It doesn’t count if what they remember is that 6 business days ago you agreed to 5 business days

Though I usually succeed despite procrastination, I’m pretty sure in most cases things would have gone better with alacrity.

5 days seems pretty reasonable to design and build most stuff. It’s function and system/integrated test that takes time not to say there’s not random bits of work that take months before anything testable can be produced.

*My experience is in giant systems processing mainframe class data. The programmers in my team use COBOL

In money you can work in cents and round fractions to whole cents in someone’s favour depending on policy for example my home accounting program rounds divided amounts up in transfers to the various accounts. It’s pretty good right now with a can’t being such an insignificant value.

Sorry, typo. That was supposed to be “aren’t” I didn’t mean to wish obsolescence on you. Ed. No, I just phrased it confusing

It was the wondrous system “DOS 6.2”

My 3.5 AC 20 monk was on his last hit point but as one of the two most competent holder backers still moved to the front

I was looking forward to a dirt nap, but we won

Double post

I wouldn’t want to be in my character’s world, I’d want to be them here

Mine does magic that would be useful in the real world. Much sadness I’m not them

I recently had this explained to me, terminal velocity is falling versus the force of the air pushing back on you, right? In vacuum you just keep accelerating, in atmosphere the air pushes back against you falling, limiting your speed

That force follows the rule that force (of air pushing back) is equal to acceleration (9.8m/s/s) times mass

So different weights fall at different speeds.

Half of the replies to me when I said what you said were

Idiot, f=ma

Or similar

USB killers are a thing. The top three autocomplete for USB killer were …buy, …eBay, and …Amazon

Wikipedia: https://en.wikipedia.org/wiki/USB_killer

Paper on their effectiveness on different hardware: https://wrap.warwick.ac.uk/id/eprint/137908/1/WRAP-killing-your-device-via-USB-port-Angelopoulou-2020.pdf

These are moderately easy to make and cheap to buy

The first two returns from Google were sites selling USB killers

I think Bambu have their own solution and since they don’t want their users using other brand filament they would be nuts to support an open standard

You obviously need to ID the spools and store values for all, the different hub weights aren’t a big issue if the printer knows the length of its filament path, how much filament the spool started with, and how much filament has been consumed it can work out the hub weight

Regularly changing filament fixes the problem of the load cell drifting, by allowing it to zero occasionally

You could warn on low filament, or not enough for this print, but load cells aren’t accurate enough to be certain about the last few metres, along with errors from cosmetic trimmed before feeding, or some is damaged and cut off, so I would still use the normal no filament sensors for stopping

Not saying it’s worth it compared to a software solution in the slicer

The friends you met in the tavern in session zero

(because they were just a bronze age tribe in Palestine making up stories about take history in faraway places to big themselves up among the other tribes)