• 6 Posts
  • 51 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle












  • In my utopia, Google would be forced to continue to pay out the current annual contract sum, at a decreasing percentage every year, for some number of years, to all affected companies, giving them the opportunity to divest and pivot.

    The root problem doesn’t get fixed if the company with enough money to be a monopolist still has the money when this is “resolved.”



  • FearfulSalad@ttrpg.networktoMicroblog Memes@lemmy.worldFight me.
    link
    fedilink
    English
    arrow-up
    29
    ·
    edit-2
    5 months ago

    I find that system inconvenient, as it does not inform me of how I should eat any given item. Classification for the purpose of classification is insufficient. However, an alternative that allows me to prepare my ustensils based on the classification is useful, and therefore I propose…

    Soup, salad, and sandwich are the three states of food, and they can go through phase transitions. They are closely accompanied by spoon, fork, and knife, respectively.

    • A soup is any food that requires a spoon, and thus includes soups, drinks, cereal with milk, etc. Tipping a container is merely the use of the container as a large and unwieldy spoon, a straw is similarly a spoon when its topology is combined with suction.

    • A salad then is anything bite sized that can be forked, and one’s hands are little more than fleshy forks, the fingers prehensile tines. Popcorn, salads, cut up steak bites, a handful of cheerios, etc.

    • A sandwich is anything that requires it to be cut in order to be consumed, and one’s incisors are merely built-in knives. A sandwich is thus the vast majority of the cube rule’s content, and only because the cube rule focuses on the physical location of the starch. This is, of course, entirely irrelevant when it comes to the consumption of food.

    • To observe a phase transition, one can cut up a sandwich without consuming it, thereby turning it into a salad; can drown a salad to turn it into a soup; can freeze a soup to turn it into a sandwich, etc.

    Shredded cheese is a salad.



  • The modules I like have:

    • A DM map with a bunch of numbers on it, and text sections corresponding to the numbers detailing an encounter in a certain area. I personally skim these ahead of time, to know which parts to read out to the players when/if they get there. These should be traps (with exposition hints), puzzles, and combats.
    • A hook, escalation with two options, and resolution, all encompassing a possible plot. TBH, this should be something that a DM can discard and replace with their own plot, if they have the inspiration and energy to do so. But if they don’t, then your prewritten plot is there for their use. This is required reading either way, to know what’s important (or what to replace).
    • Some NPCs that have basic goals and motivations, for the DM to RP if the players find them (or need a push.} You don’t want more than a paragraph or two for each, because all the extra details should be ad-libbed anyway. Motivation is key tho–why are they there, what do they want, and where their lines lie. Two one-liners from a Background table along with an alignment can usually cover most of that, TBH. Limit the required reading to 3-ish named NPCs per session, or less, with fewer introduced in subsequent areas of the module.