A few months ago as I was planning out the rest of the year, naturally it was about time to start asking myself what kinds of special events we might have for Cogmind. The major Beta 10 was released in September, so there was once again an opportunity to spend some time playing with different ideas, and players have certainly come to expect some kind of event around various holidays given Cogmind's history (see: Launchers, Pay2Buy, Holiday Mode, Abominations, RPGLIKE, Player 2...).

The next upcoming holiday was Halloween, but none of the specifically Halloween-themed gameplay concepts I had were particularly compelling, then one day I suddenly came up with the idea to do an ARG. I'm not really sure where this thought came from--it just popped in there xD

ARG refers to "alternate reality game," which as a genre has a growing variety of possible forms and definitions, but among the primary uniting factors is that ARGs are created by mixing multiple types of interactive media, ideally with social aspects. (Wikipedia has lots more background info on ARGs.)

So what exactly would something of this nature work with Cogmind, and how would I build it? Having never done anything like this before, I had a ton of questions--well that's what every special event planning session starts with, but this time it was especially acute. It really shows in my early notes, several pages of ideas bouncing all over the place, some of which aren't even close to what the event became.

Early on I was clearly wrestling with trying to get myself into the ARG spirit by steering the concept outside the game itself as much as possible, against the grain of what I'm used to designing. I started out with REXPaint UI mockups (most Cogmind special events come with a special interactive UI component that appears in the bottom left corner, serving both as a useful reference and tool, and also providing extra info for screenshots), but in this case it didn't seem necessary, and kinda worked against the ARG idea by concentrating more of the event inside Cogmind. Instead it would make more sense to move the primary form of interaction with this event outside the game itself.

So I built a little website.

Forbidden Lore!

The event banner for Cogmind's ARG, more or less a screenshot of the website home page.

Players start from that page, on which there's a single link to reach the next page, or "level," but doing so requires a password. Getting a password is a multistep process:

So the goal for each level is to solve a pair of puzzles to get the password to continue advancing to subsequent levels. (If you're wondering about more details and examples, there will be plenty of those in the walkthrough I'll be sharing later.)

Each new level provides not only the next hint, but also comes with a reward: lore! This perhaps makes the Cogmind ARG more unique than some, helping keep players interested by offering an explicit reward at every step, rather than making the solving of puzzles the only reward in itself, with maybe a single reward at the end.

A lot of Cogmind players enjoy the lore behind the game world, and there's plenty of unwritten pieces to that lore worth introducing or expanding upon. Some pieces are already hinted at in the game's current lore, while others are just my own additional concepts behind some of the content that the game doesn't (or hasn't yet!) directly addressed.

At first I had no idea at all even what theme to use for the ARG (it is "Halloween" in color only :P), but I'm glad I settled on lore since this was a fun opportunity to share more information about potential future expansions. In most cases they're not guaranteed, but are at least fun to read and think about--I've reread all the entries many times myself, just thinking about the possibilities :D

Design Options

Even with a theme nailed down, there were still some important general questions to answer, like whether the event should focus on individual participation or be more of a community event.

I did want it to bring the community together in solving a set of puzzles which would be relatively difficult for any one person to complete on their own, even planning to explicitly dub it a "Community ARG," but decided that wasn't really necessary and it could simply be a suggestion included as part of the announcement.

I also considered offering cash prizes, but changed my mind at the last minute since that might work against the idea of encouraging general cooperation across the community. Plus time zones, the fact that this event wasn't pre-announced at all (I wanted to surprise everyone :D) nor designed with hardcore competition in mind meant it would be hard for a cash reward to be fair to everyone. And of course there's already lore rewards at every level, anyway!

Another big question was whether to allow for multiple paths through the ARG, completing puzzles out of order (this was especially relevant to how the website would be built). It turns out there really wouldn't be so much content that such an approach might become very desirable, and designing for a more controlled, linear progression would make it more enjoyable overall. In the rare cases when players might discover an in-game clue before they need it, they could simply write it down for later reference.

Time to Solve

I targeted 1~2 weeks for a decent individual player working hard at it, or a month if relatively slow, but based on the amount of ARG content I figured that a group of players working together could probably do it in just a day or two.

Sure enough the first team to assemble as soon as the event started managed to reach the end in about 22 hours.

The puzzles are ordered mostly by depth, thus the first clues are found early on, and so on, making it easier to find multiple clues in the same run without having to start over. Of course with branching and a lack of backtracking in Cogmind exploration, it'd be impossible to solve the entire ARG in a single run. Theoretically one could acquire every single clue in a minimum of two runs if they happen to have the right branches spawn in the proper order and choose to do certain things in each, although it's highly unlikely someone would both get that opportunity and make the choices required, in some cases because the choices could be more dangerous and jeopardize some other clue they were aiming for at the time. More realistically it would at least take about 4~5 runs to complete (not counting potential deaths along the way).

Participation

70.5% of ARG release version (Beta 10.2) players were playing in ARG mode.

Note that Cogmind stat uploading is opt-in, so data only includes a subset of the community, and this event in particular had a higher run requirement threshold than previous events, at 10 runs instead of 3. What that means is that the event only auto-activates once a player has logged at least 10 prior Cogmind runs. Events normally exclude beginners like this in order to avoid confusing them (alternative rulesets and content are basically being added for experienced players to try out, or at least those already somewhat familiar with the base game). Players who hadn't yet met that threshold could still manually activate it, but according to the data only one player chose to do that.

This event in particular, with its deep lore rewards and requirement that one already be pretty familiar with the world in order to make good progress, was very much aimed at long-time players, and the median historical run count among participants was 40.

9.7% of players who met the threshold to automatically activate ARG mode decided not to and forced the mode off in order to play the regular game. (Some other players and runs were also excluded from the 10.2 ARG because they had manually activated some different past special event.)

The median number of ARG runs per participant was 3, which isn't really enough to solve it to the end, although in some cases where people were working together they might only do one run for the team.

Honestly the overall data here is not incredibly useful because it doesn't offer a way to know who was actively playing the mode with the intent to participate, because again it activates automatically for most players. Unlike how I've handled most previous events, I didn't include any mode-specific scoresheet data for analysis this time around.

But! We do happen to have another metric which will be somewhat more accurate, and also include anonymous players who didn't opt in to data uploading. It just so happens that anyone who gets the first hint and is on their way to completing the first level of the ARG has to visit a particular Pastebin paste, and that page has a unique hit counter. The paste itself is unlisted, so it's mostly going to be visited by players who are participating. Looking there (and subtracting my own test visits to that page with various browsers :P) I can see that we've got 185 unique hits. Still not likely 100% accurate, but it's a decent gauge of participation.

Apparently several dozen people also visited the account page I set up to make that post, from a special someone in the game ;)

Note the data for the above section was recorded a couple days before the end of the official ARG period (one month), so would be missing the last bit, plus some will still be playing past the end.

Architecture

The website part of the project is quite simple, a good thing because I ain't no web dev.

Like the front page, the content of each additional page/level is simply an image containing the entire page's text and graphics (so I can work where I'm more comfortable, in Photoshop :P), plus a hint linking to the next page.

Each new level is protected by htpasswd authentication, where as the first page indicates the user name for each level is simply "cogmind" (for simplicity), while the password is what players have to discover, as described above.

While building the site I tested all the content and links numerous times in multiple browsers to make sure there were absolutely no mistakes, since I didn't have anyone else helping me with prerelease testing this time as I wanted the nature of the event to be a surprise for everyone (even patrons). I did another complete round of testing once again shortly before launch, just in case.

On the game side there were a few new things to build, all of it pretty simple, though.

Naturally there's new content included with this release, basically messages in various forms, and those needed to be stored somewhere. My inclination with this sort of thing is to store all related data in a single external file, for ease of editing and organization. Doing this for an ARG, however, would make it quite easy to identify and hack, so I decided to avoid centralizing the data and instead spread it around within the executable itself.

Even there I didn't want the text to be that easy to scrape, so I also added a new system to encrypt strings within the executable. Despite these precautions I'm sure a dedicated individual could still hack it in less than a day, but that's fine, and could be a challenge in itself if anyone with the appropriate skills wanted to take that route to "solving" the ARG :)

The other main game-side work involved display methods for clues. This was fairly easy since sharing clues in most cases just piggybacked on the existing message systems, although in some cases it was necessary to make it a bit more obvious that something was a clue, for example the on-map alert/notice pop-up system got a new Halloween color theme option I could use for messages prefixed with "FORBIDDEN NOTICE:". There'll be plenty of examples of this in the later walkthrough.

Early in development I considered going the usual special event route with a dedicated interface for recording hints, listing clues and whatnot, but decided it wasn't necessary, and would even get in the way given how the event ended up being designed.

Mockup for an unused hint and clue interface.

Like raising levels during the RPGLIKE event in 2019, the mockup suggested there would a flashing popup whenever a clue was obtained, to make it extra obvious.

Puzzle Ideas

To come up with ideas for the puzzles, I first came up with two lists: one representing potential sources of clues within Cogmind, and another suggesting where I might want to hide passwords outside the game.

Most of the in-game options ended up being used, since an event like this should aim for maximum variety: