The Alexandrian

I was recently linked to this story on Facebook: U.S. Government Bans Native American Tribe From Protesting On Their Own Land – Send In Police To Remove Protesters.

As far as I can tell, the linked story is bullshit. First, it’s unclear which judicial action it’s reporting on. The article was written on September 7th, but the only judicial action on that day was actually a victory for Native American protestors.

Digging a little deeper, however, it appears that this is actually just a spam site that’s repackaging a story that got a lot of clicks on Facebook so that it can harvest some of that proven clickbait. It was most likely posted by an algorithm that noticed an uptick in Native American-related or pipeline-related stories on social media, and decided to copy-paste an earlier story on those topics which was a known success at attracting likes and shares.

The story it was copying, however, was actually just a spammy repackaging of actual reporting that had taken place several days earlier by Telesur.

Telesur’s story, however, wasn’t accurate. And their headline (“Native Americans Banned from Protesting Pipeline on Own Land”) was total bullshit. As Native News Online accurately reported, the judge’s order only prohibited them from physically interfering with construction. It didn’t ban them from protesting. Furthermore, the site covered by the judge’s order wasn’t actually on a Native American reservation, so it never banned them from ANYTHING “on their own land”.

So, to sum up: Inaccurate reporting tied to a completely inaccurate headline caused a bunch of fringe websites to post mock-outrage stories about something that wasn’t actually happening. One of those mock-outrage stories remixed the headline into a mostly fact-free rant masquerading as a news story and paired it to a really great photograph that caused people to click it and share it. Then some trashy sites noticed that the post was popular and duped it in order to harvest the advertising revenue.

The photograph, by the way, is actually of a Brazilian man from 2012: “An indigenous man stands as riot police stand guard during the UN Conference on Sustainable Development, or Rio+20, in Rio de Janeiro, Brazil, Wednesday, June 20, 2012. Brazil’s indigenous are protesting the government’s plan to construct the large Belo Monte hydroelectric dam in the Amazon.”

And that’s how most Americans are getting their news in 2016.

Which is a problem. Because, as we’ve just demonstrated, what the algorithms, systems, and mob psychology of social media select for is not the dissemination of truth. It is the dissemination of outrage. When you unthinkingly allow yourself to take in that outrage, you’re doing a disservice to yourself. And when you unthinkingly allow that outrage to drive your actions — even the simple action of hitting a Like or Share or Retweet or Up Vote button — you’re doing a disservice to everyone around you.

A Very Brief Review of Chobits

September 2nd, 2016

Chobits - CLAMPChobits is the story of a young boy who discovers a robotic girl (a chobit) in a garbage pile, takes it home, and turns her on. It quickly becomes apparent that this is no ordinary chobit, and a great deal of mystery builds up around the chobit’s true identity and the strange abilities she appears to possess. Along the way, CLAMP kind of flirts with commenting on the objectification of women (but seems to mostly just use that as an excuse to objectify them). The central enigma and the flirtation with deeper commentary on the “fan service” of modern manga kept me reading until the end and then… Well, let me just tell you.

REALLY SERIOUS SPOILERS

This is the truth behind the great engima of Chobits:

We discover that Chi — the chobit discovered by our protagonist — was created by a pair of computer scientists who wanted to create a fully sentient AI, and they think of her as their daughter. One day, however, Chi realizes that she wants to experience true love. So she comes up with a foolproof plan to do that:

“I will give myself amnesia and enter a comatose state. I want you to throw my comatose body on a trash pile and hope that my one true love finds my unconscious body there.”

I… umm… Wow. Okay. That’s really stupid.

Not done yet, though, because then her mother says: “We wanted our daughter to find true love, so after she went into a coma and couldn’t consent, we reprogrammed her so that if her first boyfriend didn’t marry her she would not only commit suicide but murder every other android on the planet.”

Guys, that’s not really a great plan, I think–

“Also, we specifically made our daughter so that she could fall in love with someone. But then we designed her body with an off switch in her vagina so that if she did fall in love with someone and then they had sex, it would delete her entire brain and functionally murder her.”

What. The. Fuck. Is. Wrong. With. You?

And just as you’re reeling from the big reveal that this entire story is about the secrets kept by some phenomenally fucked up people, they follow it up with: “Why did you call them chobits? Why not just call them robots?”

“Oh, because we didn’t want them to be bound by the Three Laws of Robotics.”

Because, obviously, that’s how the Three Laws of Robotics work: You just name something a robot and the Holy Spirit of Asimov fills their corporeal form and binds them forevermore by the Three Laws.

Fuck off, CLAMP.

GRADE: D

A guide to grades here at the Alexandrian.

Go to Eternal Lies: The Alexandrian Remix

Eternal Lies - German Translation

Tim Höregott is providing a German translation of both the Alexandrian Remix of Eternal Lies and the system cheat sheet I designed for Trail of Cthulhu. He will not be translating the handouts (he intends to use the originals), but will be translating all the various guides and cheat sheets. (If anyone else is interested in translating the handouts, please feel free to contact me.)

Tim is also the author of the Listen to the Gods blog (which is not in German), so make sure you check that out.

ETERNAL LIES REMIX (GERMAN)

1.0 Kampagnenübersicht
1.1 New York
1.2 Savannah
1.3 Los Angeles

TRAIL OF CTHULHU CHEAT SHEET (GERMAN)

Trail of Cthulhu - System Cheat Sheet (GERMAN)

(click here for PDF)

Warcraft

Something I like to occasionally do during a session is to speak in tongues. It can be a nice touch of flavor to have one of the orcs the party is talking to turn to their comrade and whisper something in unintelligible orcish. Or to have an elf lord curse at them with silken invectives. Or have the strange, angelic being woken from an elder age quiz them in the stilted tones of a forgotten common tongue.

When I do this, of course, it’s not actually important that what I’m saying actually means anything. (If you actually know a fantasy tongue like Tolkien’s Quenya, that’s fantastic, but not required for this technique to be effective. And sprinkling in established words from a fantasy language as a sort of slang is a different thing, albeit also cool.) What is important is that the content flows, varies, and has a consistent tone. In other words, it needs to sound like someone actually speaking.

However, this can be difficult to smoothly achieve. To assist with this effect, I’ve created a tool I refer to as a Fantasy Lorem Ipsum: For each fantasy language, I have two pages of pre-generated text (which can be printed on both sides of a single sheet of paper). When I want to “speak” in that language, I can simply choose a location on the sheet and begin performing from it. You can also use these sheets to quickly generate handouts by copying and pasting a chunk of text. (You can then provide the “translation” separately if one of the PCs knows the language.)

Ancient Common
Dwarvish
Elvish
Halfling
Orc

Go to Part 1

The key element in organizing your open table is figuring out how you want to schedule sessions. For an open table, events tend to break down in two categories.

OPEN CALLS: For an open call, the GM simply announces the date and time of the game. Players then RSVP.

Cloak and DaggerAn easy variant of the open call is the regular session: Maybe you play every Tuesday night, for example.

SPONSORED SESSIONS: Alternatively, specific players (or groups of players) can “sponsor” a session by approaching the GM and requesting it. I generally tell players that they should offer me a range of dates and then I can figure out which one works for me. It’s up to them whether they want the sponsored session to also include an open call to fill any empty seats or if it’s an “exclusive” event just for them.

The reasons for sponsored sessions can arise from either the game world or the metagame. For example, I’ve run sponsored sessions in order to “explore the Temple of Elemental Evil”, “retrieve Varla’s corpse”, or “to go back for the rest of that treasure before anybody else snatches it”. I’ve also run sponsored sessions because Steve was in town, for a bachelor party, because we all happened to be drunk at the time, and because somebody was bored and wanted something to do on a Tuesday night.

COMMUNICATION AND COMMUNITY

Mass e-mails are perhaps the most straightforward method of making open calls and otherwise communicating with your pool of players. But they can also be something of a blunt instrument.

My group experimented with a wiki for awhile, but the participation rate was low and it was ill-suited for event announcements. (I’ll probably experiment with supplemental wiki support for open tables again in the future, but for the moment I’ve lain them aside.)

What I have found effective is a Facebook group. (Why Facebook instead of G+? Primarily because too many people from my player pool aren’t on G+. If yours are, then G+ groups have a lot of advantages.) Everybody can sign up. Everyone can talk to each other. Creating a new event is as easy as pressing a button, and it’s easy to track people’s RSVPs. You can also use the group to host basic information and orientation material.

TABLE CAPS AND WAITING LISTS

My first forays with an open table featured a simple, “We’ll play with whoever shows up!” ethos. As the popularity of the open table grew, however, this quickly became non-viable: I had one session in which I GMed for ten players running something like twenty-two total PCs and hirelings.

Then I imposed table caps.

The system is pretty simple: I cap the number of players at a certain number. These slots are filled on a first-come, first-serve basis. Once the cap is hit, that’s it for that session.

To prevent highly active players from monopolizing the slots at ever session, I also instituted the concept of the Waiting List: If you signed up for a session, but couldn’t play because of the session cap, then you were given preferential placement for the next session.

The Waiting List also helps cope with the problem of last minute cancellations (because you can call up the next person on the waiting list).

The size of your table cap is almost entirely up to you (and possibly the comfortable limits of your playing space). For example, I know that I can run 5 players comfortably, 6 players are usually manageable, and with 7+ players the quality of the session will usually begin to decline. So I set my table cap at 5 and occasionally have a sixth player join (usually the significant other of the fifth player).

CAMPAIGN TIME MANAGEMENT

“YOU CANNOT HAVE A MEANINGFUL CAMPAIGN IF STRICT TIME RECORDS ARE NOT KEPT.” – Gary Gygax, Dungeon Master’s Guide

You’re going to have a lot of different characters doing a lot of different things in the setting, and a couple primary questions will arise:

  • What happens if I go to Dungeon X while Character A (who isn’t playing tonight) is still there?
  • If Character A and Character B go on an adventure together, and then Character A goes on five more adventures, and then Player A and Player B sit down for a session together… what do we do? Character A is weeks ahead of Character B!

Easiest solution: “I don’t care.” Just handwave these things away and don’t worry about it.

But there are reasons why Gygax said what he said. It was an attitude shared by a lot of the early pioneers (including Dave Arneson, M.A.R. Barker, and Bob Bledsaw among others). ClockworksAnd you’ll quickly discover for yourself that without a more concrete handling of the passage of time, there’s a lot of potential activities and consequences and fun things that won’t be possible.

Here’s my basic suggestion: Have campaign time match time in the real world. For each day that passes in the real world, a day also passes in the campaign world. If a player can’t play for a couple of months, that means that their character was just idly passing the time. (Alternatively, you could start developing mechanics for handling the passage of time: What were their upkeep costs? How are their investments doing? Did they succeed at any arcane research? Did they join a Thieves’ Guild? Or, if you’ve got the time and your players are interested, you could engage with players through weekly e-mails to see what their characters have been up to.)

Within the appearance of this simplicity, however, you’ll discover that there are some potential problems. I’ll discuss my own experience with keeping time in my original open table campaign as an example of how you might deal with some of those problems.

IN THE DUNGEON: The early days of the campaign featured a single megadungeon. The solution of using the real passage of time was largely flawless here: The amount of time that passed in any given session was usually shorter than the amount of time that passed between sessions in the real world (and the few exceptions could be easily fudged).

IN THE WILDERNESS: When the campaign expanded into a full-blown hexcrawl, however, we began running into our first serious time management problems. Crossing unexplored wilderness could chew up days or weeks of time in the game world while using up mere minutes of table time.

The first solution I attempted was to have the clock always move forwards: If Expedition A ended 18 days in the future, then when Expedition B started the next day in the real world we’d still be 17 days in the future. The problem with this approach was that it radically pushed campaign time into the future: If you missed just a handful of sessions (which is, of course, common in an open table), you could find that months had passed for your character.

LOCKDOWN: What I ended up doing instead was to adhere to real time for the start of each expedition. Expedition A was played on March 17th in the real world and Expedition B was played on March 18th, then Expedition B started one day later in the campaign world, too.

This meant, of course, that Expedition A was still happening. This meant that any characters in Expedition A were locked down – they couldn’t be played in Expedition B. I would also lock down any locations that had been visited by Expedition A: You couldn’t break continuity by going to the same dungeon as Expedition A because we already knew that hadn’t happened (since we had seen those events play out with Expedition A).

CHARACTER STABLES: With that being said, I didn’t want players to be prevented from playing just because their character was currently locked down. This led to the practice of each player having multiple characters in the campaign world.

Having this stable of characters proved useful in other ways: For example, players could choose the character which was closest in level to the other players on a particular expedition. (Or, alternatively, choose to play a high-level patron whose expertise the entire group could benefit from.)

TRACKING TIME: In order to track all of this information, I simply kept a list of all the player characters currently active in the campaign on my campaign status sheet. If they were in lockdown, I listed that. I also listed any outstanding expeditions (i.e., expeditions from previous sessions whose end date had not yet been passed) and the locations locked down in association with them. In practice, this requires virtually no effort.

END OF SESSION STATUS

The other thing to consider in an open table is the end of session status for player characters. In general, for the open table to work at the end of a session the player characters need to return to their home base (or whatever position they need to be in to participate in open group formation at the beginning of the next session).

To facilitate this for a traditional D&D campaign, I created tools like the Escaping the Dungeon! table.

SEQUEL SESSIONS: I did, however, also offer an alternative: If the evening was coming to a close and the group was in the middle of something important to them, then we could continue that session if (and only if!) everyone at the table could immediately agree on a time within the next 10 days to continue the scenario. (If they couldn’t, tough luck: They’ve got get out and they’ve got to get home.)

The reason for the strict limitation on this is that, in the interim, all of these characters (and the location they’re in) would be locked down. This creates all sorts of complications for the open table. There was one time when I set up a sequel session and several of the players had to cancel on it. Trying to reschedule proved challenging and we ended up bouncing it around for two or three months before I finally wrote it off and released the lockdowns. In the interim, however, all of the momentum in that section of the campaign had been lost: I would have been far better off immediately writing off the sequel session and allowing subsequent expedition to be scheduled to pursue the loose ends which had been left.

CHARACTER CREATION GUIDELINES

A final thing to consider, if you’re planning on using some form of away-from-the-table character generation to resolve the lack of quick character generation in your system of choice, are the character creation guidelines you want to use.

As a tip: If your system of choice features organized play, looking at the character creation guidelines for that can often be useful. Their needs will be similar to your own, although you can often relax many of their strictures.

Archives

Twitter

Recent Posts


Recent Comments