Chunky procedural generation

When making a procedural generator, instead of letting a parameter vary across the entire range of possible values, considering breaking that range into sectors.

EDIT: I used to call these limited ranges “chunks” instead of “sectors” but procedural generation in chunks makes people think of Minecraft, so I changed the name to avoid ambiguity.

Sectors

Not overlapping isn’t enough. Sectors should have space between them. This reduces the total number of possibilities, which seems bad, but each value will have greater meaning.

A number line from 0-4, labeled "height (meters)" Four ranges are marked. tiny: 0 to 0.5 meters. small: 0.75 to 1.25 meters. medium: 1.5 to 2 meters. Large: 2.5 to 4 meters.
Figure 1. Height parameter separated into four chunks

If the Small and Medium height sectors met at 1.5m, artifacts could be generated whose height is ambiguous. I can’t tell the difference between 148cm and 151cm at a glance, so if I see creatures with those heights, I won’t know if they are Small creatures or Medium creatures. Stopping Small at 1.25m means there’s 25cm between the tallest Small Creature and the shortest Medium creature, enough to remove ambiguity.

A number line from 0 to 12, labeled number of legs. four chunks are marked. Orb: 0 legs. Biped 2 legs. Beast 4 to 6 legs. Bug: 8 to 12 legs.
Figure 2. Number of legs parameter separated into 4 chunks.

Sectors don’t have to be the same size. They need to be different enough that observers can tell them apart. Counting 10 or 12 legs will take a while, but I immediately know they are both “a lot” and thus bug-like. The range for biped has no variation at all, but that’s valid too.

Limited sectors promote identity

For example, Hunter clothes come in desaturated earth tones to help Hunters blend in with natural surroundings.  If all clothing was available in all colors, Hunters would have less of an identity. Choice of clothing tells viewers something about the person wearing the clothing.

A grid of 21 stars on a black background. The stars vary widely in size, color, thickness, and number of points.
Figure 3. Stars generated with maximum randomness
A grid of 21 stars on a black background. The stars are roughly the same size, with 5 to 7 points, and red to yellow coloration.
Figure 4. Stars generated from sectors of parameter ranges.

Figure 3 the output of a star generator with the ranges on size, color, spikiness, and number of points opened up. It’s easy to associate to the two green spiky stars at top right as being kind of the same thing, but why would I think the red diamond on the left edge is the same kind of thing as those other two? The class of “stars” is so diverse that it loses cohesion.

In Figure 4, I tightened the colors to warm, autumnal colors, and reduced the amount of variance in size, number of points, and spikiness. These stars seem more related to each other. It’s easy to mentally group them as the same kind of thing, but there’s still quite a bit of variance between each star.

Perceptual differentiation

A grid of 21 stars on a black background. Half the stars are grey, very spiky, with many points. The other half look like the stars in Figure 4: red to yellow, 5 to 7 points.
Figure 5. Autumnal stars and grey spiky stars

Perceptual differentiation is the ability to tell two things apart.

In Figure 5, I’ve mixed the autumn stars with spiky grey stars. Even though each star is different from all the others, it’s easy to see that there are two different kinds of stars, and to sort each particular star into one of those two groups.

Individually unique objects that are easily sorted into groups are a nice way to ensure perceptual differentiation. If the two classes uses disjoint chucks of the parameter spaces, two objects from different classes are sure to look different from each other.

Even if you end up with 10,000 bowls of oatmeal, if you also offer 10,000 slices of toast, 10,000 waffles, and 10,000 cups of yogurt, you have a better breakfast buffet.

“Perceptual differentiation” and “10,000 bowls of oatmeal” are both terms from Kate Compton’s excellent blog post So you want to build a generator…

The sector becomes information

If a certain feature of an object is not completely random, it can tell us something about that object. In ARPGs like Diablo, a potion with blue liquid will restore my energy, no matter the size or shape of the bottle.  blue potion = mana. if a tree has a conical crown and needles instead of leaves, I know those leaves won’t fall off in winter, because conifers are evergreen. Live oaks are also evergreen, but their leaves and crown are shaped closer to deciduous trees than conifers, so it’s easy to mistake them for deciduous trees.

The next section shows how one class of object can have multiple parameters that each have some meaning, so an observer can quickly recognize many features of

Layers of differentiation

Every object will have multiple parameters, and each parameter can be divided into multiple sectors. By giving different objects the same or different sectors, you can create a hierarchy of relationships between objects. I’ll use Starcraft as an example.

Races:

  • Protoss:
    • colors: pale yellow, glowing blue
    • shapes: smooth curves
  • Terran:
    • colors: shades of grey
    • shapes: rectangles & circles
  • Zerg:
    • colors: reddish to purple
    • shapes: tubes, sacs, claws, and teeth

Unit types:

  • Buildings
    • size: huge
    • number: solitary
    • features: immobile, grounded
  • basic units
    • size: small
    • number: large groups
    • features: mobile
  • elite units
    • size: large
    • number: small groups
    • features: mobile

Terran Infantry:

  • All infantry:
    • small
    • humanoid
  • Marine
    • big shoulders
    • long gun
  • Firebat
    • backpack
    • twin weapons
  • Medic
    • white armor
    • shield

Seeing these patterns helps me recognize objects quickly, and make good guesses about new objects I haven’t seen before.

If I see a mass of Terran Infantry (small, humanoid, grey, large numbers) I can pick the Firebats out from the Marines by looking for the backpacks, because that’s the feature they DON’T share.

If I see a weird purple creature with big teeth, I know it’s Zerg, because that’s what Zerg look like. Protoss and Terrans don’t make things like that.

If I see a huge, immobile, radially symmetrical object, it’s probably a key building, like a Town Hall, because that’s what all the other Town Hall buildings look like.

Notice that the relationships can be hierarchical (Terran Infantry is a subset of Terran) or cut across groups (buildings share characteristics across races)

Use an interlocking system of similarities (objects that share the same parameter sector) and differences (objects use disjoint sectors of a parameter) to create objects that are all unique, but are easily sorted by an observer into multiple overlapping groups.

Summary

  • Consider if you really need the full range of a certain parameter for a class of artifacts
  • Divide a parameter range into sectors that:
    • are thematically appropriate for the artifacts that use them
    • are disjoint from other sectors of the same parameter range
    • allow enough variation between artifacts that use the sector
  • Use those sectors to:
    • allow observers to remember features of the artifacts
    • relate artifacts to artifacts that share that sector
    • separate artifacts from artifacts that use different sectors

Data-driven item generation for Equipment Explained

Equipment Explained is mostly practice for clear, accessible UI, but I still made an overly-complicated system to generate items.

The parts of an item

  • base item
    • item quality
    • (optional) prefix
      • prefix quality
    • (optional) suffix
      • suffix quality
    • (optional) requirements

The base item is either armor or a weapon.

  • weapon
    • type (axe, sword, hammer, etc.)
      • which stats the item boosts
    • slot (main hand, off hand)
      • where the item can be equipped
    • tier (0-3)
      • magnitude of bonuses
  • armor
    • slot (feet, body, head, etc.)
      • where the item can be equipped
      • magnitude of bonuses (a breastplate provides more armor than gloves)
    • tier (cloth, leather, plate, etc)
      • which stats the item boosts (leather boosts DEX, plate boosts HP)
  • item quality
    • probability of prefix
    • probability of rare prefix
    • probability of suffix
    • probability of rare suffix
    • probability of requirements
    • multiplier for magnitude of
      • item bonuses
      • prefix bonuses
      • suffix bonuses
      • requirements

Common affixes only boost a single stat, but rare affixes boost several stats

  • prefix
      • quality
        • multiplier for bonuses of prefix only
      • stat bonus
  • sufffix
    • quality
      • multiplier for bonuses of suffix only
    • stat bonus
  • requirements
    • lower limits for a set of thematically linked stats that must be met for an item to be equipped.

Simplifications

Because I’m not making a whole game, I was able to skip some constraints that most RPGs use.

Thematic Affixes

Some games limit certain affixes to certain types of items, such as

  • “of Fleeted-footedness” only appears on boots
  • there are no poison resistance rings
  • helmets tend to boost INT.

The base items in Equipment Explained specialize with only a few stats, but affixes can affect any stat, and any item can have any affix. So a sword is sure to boost Slashing Damage, but sometimes cloth gloves will boost Slashing Damage even more!

Balanced Requirements

Most RPGs will give more powerful items higher requirements, and thematically appropriate ones. So a magic staff may require a lot of INT or MP to equip, while a small hammer would instead require a bit of Strength. In Equipment Explained, higher quality items are more likely to have requirements, but those requirements are chosen randomly and aren’t associated with the bonuses the item provides.

Playtesting/Balance

Equipment Explained doesn’t have combat, experience, loot drops, or an economy.  I don’t have to worry about items being fair. Is it reasonable to scale Health from a base value of 100 to 2700, or to 125? I don’t care. I do care that it’s very obvious how much those boots will increase your Health, how much you need to increase your Magic Resistance to equip those boots, and which items will help you reach that goal.

Implementation

I created an LibreOffice spreadsheet with a sheet for each type of data. The first row in each sheet is human-readable labels for each column, which the game engine has no use for, so I don’t use LibreOffice’s built-in CSV exporter, which will export every cell in a sheet.  Instead I drag-select the sheet (except for the header row) copy and paste into a text document.

So the 10 sheets of one LibreOffice spreadsheet become 10 .txt files, which I place in the resource directory of my Godot project.  I write a custom function to read each file, and save all the information about items, affixes, requirements, probabilities, etc. into data structures.    affix.txt contains information for both prefixes and suffixes, since they are so similar. The function that reads affixes.txt can also read affixes_rare.txt, which uses a similar format. Weapons are armor are defined by a two-dimensional array of type and tier, and CSV files are good for one-dimensional lists, so armor and weapons need two CSV files each to completely define the space.

When I create an item, I pick from the list of items & the list of qualities. The quality specifies the probability of requirements, prefix, and suffix, so based on those odds I may pick from those lists as well. Pretty basic stuff once all the data is loaded from the files.

Manually copying data from spreadsheet to text file is error-prone busywork, so if I continue developing this, I’ll need to automate that step.

Checking for link rot

My collection of photo galleries from events I like has been growing for years, with close to 10,000 links. But the Internet is ever-changing, and some of those links from years ago may no longer be valid. I’ve designed a system to check for this “link rot” and save users of this collection from the frustrating of clicking dead links.

Goals

  • Test each link weekly
    • not working one week, maybe it’s a hiccup. Probation
    • not working for two weeks. It’s dead. Hide it.
  • Don’t spam image hosts with unnecessary requests
  • Minimize the amount of manual work I have to do

Implementation

The gallery aggregator is written in PHP, with a MySQL database. I plan to run an automated job each day that will check everything in the DB over the course of each week. So each day, I check every seventh gallery, and move the offset based on the day of the week.

I added two columns to the DB.

  • last checked: timestamp of the last time I tried to access this URL
  • last accessed: timestamp of the last time this URL returned HTTP 200 OK

I skip any gallery with a “last checked” value within the past day. Then I try to fopen() each gallery. I don’t need to download these webpages (which contain many large images) I just want to know if they exist. If the URL returns HTTP 200 OK, I add that gallery ID to a list of “fresh” galleries.  When I’ve tried to visit all the URLs, I go through the list of “fresh” galleries and set their “last accessed” time to now.  The “last accessed” time for URLs that return errors will stay the same, and time will march away from it. The ‘last checked’ time is always updated to now regardless of the HTTP response code.

Even dividing the task up across the week leaves more than 1000 URLs to check per day. I don’t want my PHP job to time out, and I don’t want to trigger DOS protections on the image hosts I’m pinging. So I paginate the job with MySQL’s LIMIT keyword. Each time I process a batch of URLs, I update the “last checked” field, which means those URLs won’t be selected in the next batch. Eventually there won’t be any URLs left to check, so running the script too many times does nothing instead of performing unnecessary DB updates or HTTP requests. I know to stop when I don’t have any more input to process.

The webpage that displays galleries to the public now takes the “last accessed” time into account. If that time is more than 2 weeks in the past, the gallery is hidden. If “last accessed” is between 1 and 2 weeks in the past, an icon and tooltip appears next to the link to that gallery:

  • 🚧 This gallery might be offline.

Galleries that are “fresher” than 1 week are displayed normally.

Results

Since I give each gallery a few chances, this first week of automatic testing won’t remove any galleries from the list.  You may see some 🚧 icons appear over the next week, and in the new year, dead links will start to disappear. It’s a long-term project, but I intend to maintain this list for years, so I don’t mind waiting.

PROCJAM 2019, Day 1

Background

PROCJAM is a fun, relaxed game jam with the goal to “make something that makes something.” It doesn’t even have to be a game.  (itch.io jam page) (twitter hashtag)  This will be my third year participating.

Goal

This year, I’m making a tool to assist Chasing The Sunset, a sprawling, persistent exploration-based TTRPG based on West Marches and Fellowship. Explorers need locations to explore, and Fellowship has lists and instructions for creating new locations with pencil and paper. My goals for the online, procgen implementation of this tool are:

  • Automatically generate legal, well-formed locations
  • Teach the generator that some combinations make more sense than others.
  • Allow the user to adjust any choice the generator makes
  • Compress the output into a “random seed” that can be plugged back into the generator to reliably create the same output.
  • be slick, non-hacky, and user-friendly. (I want to take a level in Artificer)

Progress

I’ve been fiddling with project setup and workflow for a few days. I’m using react.js and it requires a different mindset than jQuery, or component-based systems I might use in a game engine. I think I have the hang of sending data down the heirarchy through properties & automatic render() updates, and sending data back up through callback functions.

Here’s a screenshot of the current state of the project.

  • Multiple lists that have the same code, but different data sources.
  • Lists can toggled between read-only and editable modes.
  • It displays checkboxes if multiple options can be chosen, or radio buttons if only one option can be chosen.
  • List items have optional descriptions
  • “Affinities” are a first pass at creating cohesive locations. Asterisks on options indicate how much they match with what’s already selected.
  • The each list creates a number that uniquely represents its options, and the top-level generator concatenates them into a single seed, which is displayed a emoji because emoji are fun!

What’s next?

  • Lots of data entry. Lists and lists of creatures, terrain descriptions, location moves, and relationships.
    • Low priority because code may require changes in data format, and I want to minimize re-work.
  • Random seed needs more thought. There are plenty of edge cases where the current system fails.
  • Randomly select from a list, but with influence from other lists
  • Affinities need more work. Right now I only have positive affinity: like attracts like, not negative affinity, where opposites repel.
  • Export as text file.

Reasonably secure contact card

This weekend, I will photograph the Fremont Solstice Parade and the Solstice Cyclists from the 12th year in a row.  These two related but separate events are glorious local tradition of joy, creativity, and public nudity.  In years past, I’d upload all my Solstice photos to a public gallery. Other users could comment on the photos and add them to collections.  Wow, did I see a lot of disgusting, disrespectful comments and photo collections!  Alas, creeps & voyeurs use this glorious event, which should be about freedom & joy & self-expression, to make the nude cyclists uncomfortable.

Privacy for nudists

Thus my quest to make my photos invisible to the general public, but easily accessible to people I photograph in passing.  One year, I put all my photos on my own website and only posted the link on the private e-mail list for the Solstice Cyclists.  Someone on that list made a publicly-accessible page of links that included my private link. Apparently I can’t share things in confidence, even on that private e-mail list.  Another year I put all my photos on my own website, but this time the only place the address appeared was on contact cards that I gave out at the event.  My website’s logs indicated a lot of traffic to certain images, so someone probably shared links to them. I could guarantee that no one could publicize someone else’s photo by delivering all photos via e-mail, but many Solstice Cyclists prefer to remain anonymous and don’t want to give out their e-mail addresses to photographers they’ve just met.

So how can I deliver photos only to the people in the photos without getting contact information from those people? My solution this year is to pass out unique contact cards to each person I photograph. Each card will have a different URL printed on it.  When I hand out a card, I’ll take a picture of the card and its recipient.  When I process photos later, this will tell me which photos to upload to which URL.  The URLs are generated from a large list of English words, so they will be easy to remember and type. The word list is large enough that it won’t be easy to guess someone else’s word from looking at your own.  The words aren’t all colors, or names of birds, or adjectives.  If people lose their cards, they won’t be able to find their photos, but previous solutions had the same problem. Nude people rarely have pockets, but people in previous years have stuffed cards into socks, bags, helmets,etc.  If they have phones, but no pockets, they can photograph the card & keep a virtual copy.

Generating the cards

I obtained a list of 1000 words from a site for crossword puzzle enthusiasts. I read through the list and removed any words with possible negative connotations, like “bizarre”, “murderer”, “chunk”, and so on.  That left me with about 730 words.

In a word processor, I made a mockup of the contact card, using the longest possible word in the URL to make sure it would fit on one line. Once I had one card, I copied-and-pasted dozens of times to make sure it would fill up one page and wrap to the text properly. I had to adjust spacing and font size a few times, but I ended up with a card that would print 16 to a page.

I wrote a python script that would pick a word from the word list, insert it into the text of the card, and write that to a file.  One loop for 10 pages and another loop for 16 cards per page, and I had a text file with 160 unique URLs. I copy-and-paste that into the word processor with my carefully tuned formatting, and everything lines up. It’s so nice to see rows and rows of identical text, except it’s not quite identical. Every card has a slightly different URL.  Print and cut and I’m ready for the parade!

#7DRL 2019, NiceRL

7DRL Challenge is a game jam with the goal of making a roguelike in seven days. Last year, I made Obliteration, which is fan-fiction for the movie Annihilation.

This year’s entry, NiceRL, has several goals.

  • Save a lot of work and get more practice with Python by using the libtcod library.
  • Flip the dungeon crawler on its head. Use the items in the dungeon to help its inhabitants, instead of killing them and haording their wealth.

I used a helpful tutorial from rogueliketutorials.com.  The code is available on GitHub, but I typed it most of it in myself, because that forced me to understand it. Do I use an underscore or a dot here? Does this function return a list or a dictionary? Those distinctions are easy to miss when copying-and-pasting, but when I type them in myself and have to solve the resulting syntax errors and crashes, I’m training myself to have good habits.

My goal of a helpful player improving the dungeon as he goes through it is inspired by Max Kreminski‘s Gardening Games Zine.  I don’t hit all the points in that zine. The player is still central because creatures can’t solve their problems alone. The space gets less interesting as t he player acts on it because once a creature is happy, there’s no more interaction available. Mechanically, using cookies to reduce a creature’s hunger to zero is identical to using arrows to reduce a monster’s HP to zero. Is changing the theme without changing the mechanics enough?

Once I had the tutorial code up and running, I started modifying it to fit my specific game. I built one emotion and one item that relieved it, then duplicated that code for two more emotions. After all that was working, I realized it was a bad idea. All the emotions behaved similarly. I collapsed them into one and added an enum to specify the emotion. A creature with with 15 units of sadness, who can be cheered by a toy is similar to a creature with 6 unit of anger, who can be soothed by a stress ball. Just make sure the type of the item matches the type of the creature. Any time I copy and paste a significant chunk of code, I have to stop and question it, because I’m probably making a mistake.

I think that systems are hard and content is easy. A flexible expressive system can handle any content one cares to throw at it, but a restrictive, clunky system will need constant tweaks and work-arounds as content exceeds its limitations. I’ve built several systems like this before, but in each case, I had a vast pool of existing content to pull in. For example, costumes at Dragon Con, or photo galleries from conventions.  Once I built the system for helping creatures with their emotional needs, I realized I needed to name all those items and all those creatures. I needed adjectives that showed escalating intensity of various emotions, and items that similarly escalated. It was much harder than I anticipated.

My content-generation worksheet

I had ideas for other kinds of improvements the player could make to the dungeon, but they were cut for time.  As you can see on the worksheet, I thought of lighting candles, arranging furniture, or repairing broken items. I actually wrote an AI for a table that looked to see if chairs were properly arranged around it. When the last chair was placed, the table became happy and threw food on the floor for the player to retrieve. Obviously not how dinner tables behave in real life, but it felt right to me. When the table is prepared, you can eat, not before.

Conveying information to the player is always vital, but especially when the game is doing something unexpected. In a standard dungeon crawler, a player may see something labeled “goblin” and know, from decades of games and novels and movies, that a goblin is hostile yet weak. But how should I deal with “peckish Sam” or “fuming Jaunita”?  Does a toy make someone less scared or less sad? A big part of roguelike tradition is not knowing how things work and learning by (painful or fatal) experimentation. I decided to err on the side of clarity. Not only will a person who is searching for a lost item will tell you what they are searching for, but if you find that item before meeting the person, the item itself will tell you who it belongs to.

A screenshot of NiceRL

Here’s what the final game looks like. Most of the screen shows an overhead view of the space. Below that, a scrolling message log details each thing that happens. On the right are stats about the player, the item the player is holding, and whatever the player hovers over with the mouse. You can see what each item does. I also have a README file listing all the inputs and explaining what each character on the map means.

So seven days after starting this project, I have a complete, playable game. It saves, loads, exits, ends when you are exhausted or when you finish all the levels. But you can’t play it. I mean, I can play it. It works, But you can’t, because you don’t have access to it. Despite all that I learned about Python and the libtcod library, I neglected to learn how to publish a Python program. The goal of 7DRL is to create and release a playable game in seven days, and I completely failed the “release” part. I forgot to even try.

So, was my 7DRL a success? Hard to say. I made a game, and it’s mostly the game I wanted to make. I learned more about Python and project management. But the game isn’t really fun to play. It’s not much to look at. It’s not challenging or deep. My verdict: the process was valuable, but the artifact is not. It’s good practice, like pages of an artist’s sketchbook that will never see the light of day. Not everything has to be glorious, and not everything has to have an audience. The important thing about this jam, to me, is that I keep working, keep trying, and keep improving.

Curation, or How Do We Actually Know Things About Video Games?

Steam has a “Curator” feature that allows users to make lists of games. Many are “Games I play on my YouTube channel” or “Popular games that I hope will drive traffic to my curator page” but there are also very specialized curators that I love.

I started a few lists of my own, just for fun. Little did I know this classification project would get out of hand! (See also, Atlanta Fashion Police, convention galleries, Solstice Cyclists, basically all my classification projects get out of hand)

I like to see all the new games that are coming out, and adding to these lists was another fun thing I could do while going through Steam’s new releases.  Before I knew it, these lists had hundreds of games each.  They are a significant collection of knowledge! But all my work is in the Steam eco-system, making Steam a more attractive place to go and to buy games.  Why should I improve someone else’s website with my labor? Especially a functional monopoly whose business practices I dislike. So I resolved to move my curation onto my own website.

Yes, I was gong to build another database, with back-end pages that partially automate creation & editing of information, as well has public-facing search and view features.  I’ve done the PHP/SQL thing several times, so for this project, I chose to learn Django and Python.

Two of my lists, and several of the other curators I like, are variations of “Games that contain this particular thing”  If my DB had a list of playable species and non-playable species, it would cover both Non-Human Protagonists and Arachnophobia, games w/ spiders, as well as Spike Covered Kittens, Elf Girl Respect Patrol, Satan Enthusiasts, You are a Ghost, THAT’S A GOOD ASS DOG, Mecha Galore, Does It Have Robots?, Dwarves of Gaming, Games Featuring Dogs, Skeletons & Videogames, Games With Cats In Them, Anthro / Furry Tag, and probably a few others. Easy win, right!  Generic data models are great!

I defined “species” rather loosely as “a group of creatures of the same type” and let species have parent-child  relationships with each other. So “humanoid” includes “human” and “elf” and “Klingon”. Since “drider” and “scorpion” both inherit from “spider-like”, they show up in the list for Arachnophobia, but I can also offer more precise lists for only scorpions or only driders.

But the presence of a particular type of creature isn’t the only relevant information. Some arachnophobes hate cobwebs, others are OK with spiders as long as the spiders don’t leap at them.  “Cobweb” isn’t a species, and “leap” is a capability, not a sub-species. Likewise, people who care about dogs in game might want to know if they can pet the dogs, or if the dogs do tricks. They don’t care if they can pet the spiders, and dogs never shoot webs, so adding “is pettable” or “shoots webs” as attributes of a species doesn’t make sense.  Any species may have extra attributes that only apply to it.  I could easily represent this with object-oriented subclasses, but databases don’t work that way.

Look how hard it is to answer a simple question: “Can I play as a skeleton?”

  1. In Grim Fandango, you control one character: Manny Calavera, a skeleton. Yes, always.
  2. In DOTA 2, you pick one hero from a large roster to control. You may choose Skeleton King, or a non-skeleton hero.  Yes, sometimes.
  3. In Din’s Curse, you control one human hero. You can choose from a list, or create your own by combining parts of pre-made heros.  If you have the Necromancer skill tree from the Conjurer class, you can summon skeletons which fight for you. You order them to move and attack, but your human hero is more important. Yes, sometimes, indirectly.
  4. In WarCraft III, you choose one of several armies to control.  The Undead Necromancers can raise Skeletons from corpses. Heroes who find a certain item can also summon skeletons. Your control of these skeletons is as detailed as your control over any other unit. There is no main character.  Yes, sometimes, as much as anything. But, wait! During the singleplayer game, you guide various heroes through story missions. These heroes are the main characters, so they are more important than any skeletons who may or may not join your army. The mechanical controls do not change, only the context provided to those mechanics by the story. Not really, I’m Arthas right now.
  5. In Dragon Age: Inquisition, the player can directly control any character in combat, but only the Inquisitor’s appearance and personality can be controlled by the player. The player IS the Inquisitor. The other characters are their own people.

So we can get more useful answers by replacing the question “Can you play as Character X?” with the following questions:

  • Can you control Character X?
    • Always
    • Never
    • Sometimes. Arthas from WarCraft III is controllable in some story missions and is an NPC antagonist in others
    • Optional. Players can add Polar Bears to their armies in King’s Bounty, or not.
    • Partially. Cassandra from Dragon Age: Inquisition can be controlled in combat but not in conversation
    • Indirectly. Players have basic control over Fallout: New Vegas‘s Boone in combat, but none in conversation. Control over the Courier is more direct.
  • Can you identify with Character X?”
    • Always
    • Never
    • Sometimes Commander Shepard is the player avatar in Mass Effect 3‘s singleplayer, but the player has a separate set of characters in multiplayer.)
    • Optional. Players can choose to be Cammy in Street Fighter V or some other character.

According to League of Legends lore, players always and only play Summoners, human magicians who in turn control Champions. But that’s not how people experience League of Legends.  People say, “I’m going to play Miss Fortune” or “I’m an Urgot main”. They identify with and directly control a Champion. On the other hand, Princess Maker Refine, has a similar invisible protagonist, but players don’t identify with the princess because ordering a girl around is part of the fantasy.

So simple questions like, “Is there spider stuff in this game?” and “Can I play as a robot?” can be answered in a short English sentence, but creating data structures to codify all the shades of meaning contained in that sentence is very difficult.

PROCJAM / 7DFPS 2018, Photo Copy: final push

PROCJAM, 7DFPS

Day 1, Day 2, Day 3, Day 4, Day 5, Day 6]

Play Photo Copy in your browser!

 

Time was almost up, so I concentrated on getting the game into a playable state.  After breaking the AI photographer the day before, I needed a quick way to make it functional again. I added an invisible box around the extents of each landmark and had the AI photographer point at that.  Alas, no understanding of symmetry, or lining up multiple landmarks in one image, or any other things I was hoping to implement at the start of the project.

I also cleaned up the menus and functionality to start and end the game.  The introduction used to be a separate scene, but I pulled it into the main scene.  Less to keep track of, and it let the player look at the instructions while playing by hitting Escape.  Alas, walking through the exit portal, then canceling the exit UI was causing trouble, and it was faster to cut the portal than to debug it.  RIP Exit Portal. I still believe in diagetic UI.

At this point the player could start the game, enter the world, see photos from the AI photographer, take photos, have them scored, then leave the game.  I exported a copy and uploaded it to itch.io, just so I’d have a working version to fall back on.  I still wanted to add features.

The inspiration for this entire Black Rock City generator was a camp name generator written in Tracery. Since Unity supports JavaScript, I tried just putting the Tracery files in my Unity project, but there were some errors.  Fortunately, Max Kreminski had ported Tracery to C# specifically for use in Unity. (TracerySharp on github) Once I could generate camp names in Unity, I assigned each city block a name.  When the user “looked” at a camp (when a ray from the center of the screen intersected the block’s collider) the name would appear on screen.

This added a lot of character to the city.  Just running from camp to camp, reading the amusing names was fun.  This technique was easily extended to the street signs as well, so the player could actually read the street signs by looking at the them, which really makes the city feel like a real place.

My mind raced.  Photos from the AI photographer could be annotated with hints, like, “Found this cool art piece on Echidna street”, “took this picture while chilling at the Undetectable Capitalism Dome”, “some guy told me this thing is called Normie Zone”  Before I started that sub-project, I wanted to be sure that looking at things still worked when two cameras shared the same viewport.  it seemed to work as expected in the editor, but I built an EXE to be sure.  IT worked differently in the EXE.  I built to WebGL, since most people would play it in the browser on itch.io, and it worked a third way!  I did not have time to debug that and add all those new features, so stopped there.

The first version that I uploaded to itch.io would be the final version.  Rushing and stressing were against the spirit of PROCJAM, so I practiced the  skill of knowing when to leave well enough alone.  After I made peace with ending in a stable state instead of working up to the deadline, 7DFPS extended the deadline! Self-control was required to avoid diving in once more.

Play Photo Copy in your browser!

PROCJAM / 7DFPS 2018: Day 6

PROCJAM, 7DFPS

Day 1, Day 2, Day 3, Day 4, Day 5

I’m approaching the end, so I need to wrap things up.  Here are some relatively quick fixes.

Pressing Escape will exit the game, but there’s also a diagetic exit at the end of the 6:00 road.

Also visible in that image is the trash fence. Burning Man is surrrounded by a pentagonal fence meant to catch anything form the city that blows away in the desert wind.  I added a circular fence to keep players from wandering off the edge of the world. The real fence has a square lattice pattern, but I made the width of the fence segments adjustable and I didn’t want to deal with the texture stretching, so my fence has only horizontal bands.

One of the last things I added to my Burning Man simulation was the Man himself.  He’s another low-poly mesh built in Milkshape, although the base is generated with the same Lathe that creates the Temple.

Camp structures will now fill long blocks.  I just re-run the structure placement algorithm with several starting locations along the long axis of the camp.

There are some weird things visible in the above image that aren’t normal camp structures.  Those are landmarks! Yes, I’ve finally added some landmarks to a game ostensibly about photographing landmarks.  There’s a two level-generator that lays out several paths, then puts objects along those paths. It can create.

Balloons (1 thin, irregular path with a large sphere at the end)

Towers ( a line of vertical lines)

Abstract art (irregular paths of irregular shapes)

An unfortunate side effect of these wonderful new landmarks: the AI Photographer doesn’t know how to look at them.  The Burning Man sim has overtaken the photography sim so much that the original goal of the project no longer works.  Whoops!  There’s still a bit of time to re-write the photographer, though.

PROCJAM / 7DFPS 2018, Day 5

PROCJAM, 7DFPS

Day 1, Day 2, Day 3, Day 4

Unity uses two programming languages:  C# and JavaScript.  I use C# because I like strongly-typed languages.  I want to see as many mistakes at compile-time as possible. But Tracery (which I used to generate Burning Man Camp names) is written in JavaScript. Can I just copy the files in to my project’s directory structure? No! Unity finds several errors in files that work just fine in a web browser.  Searching online reveals two people that ported Tracery to C# specifically for use in Unity.  Both authors caution that these ports are completely unsupported, but that’s good enough for me.  I assign a name to each city block, but displaying that name to the user requires learning how to use Unity’s UI features.  I don’t want to deal with that hassle, so I switch tasks!

The Temple was a giant blank cylinder, and the Man was standing on a similarly boring box. I create a Lathe algorithm to replace both.  The Lathe draws some line segments from bottom to top, then rotates that outline around the Y-axis, kinda like a vase.  This is quite-low-level compared to most of what I’ve built.  I’m not using built-in primitives or importing meshes I built in a 3D editor.  I’m creating the object one piece at a time while the game is running. Not only do I have to write nested loops to place each vertex, I have to remember what order I created them, because the triangles are one giant list of references to the one giant list of vertices.  Speed is important at this level, so I don’t get the luxury of a big tree structure of objects. After writing some triangles backwards, and forgetting a few numbers, I get a shape!

What is this? The light acts like it’s completely flat!  I had missed two things.

  1. Unity stores only one normal per vertex, so if two triangles share a vertex, Unity will smooth the join between those triangles.  I want the angular, low-poly look, so I don’t want any triangles to share vertexes.  A quick sketch shows that each vertex borders six triangles, so I have to edit my vertex generation loop so it creates six times as many verticex!  Now the triangle creation loop needs to use each of those vertices exactly once.  Yikes!
  2. The second step is to call the RecalculateNormals() function.  Much easier!

So much better!  You’ll notice that this temple is spikier than a vase.  That’s “star mode.”  I bring a piece of code over from my bodypaint generator that reduces  the radius of every other vertical row of vertices.

After finishing this project, I am ready to tackle some UI work. People won’t enjoy even the coolest game if they don’t know how to play, so I need to explain myself.  I add a title screen with a list of controls and a bit of story.  This is a game about copying photo.s. The original code name was “Art Fraud” But now i’m having second thoughts.  Taking photos in a magical, beautiful place seems so joyful and positive. Do I really want to flavor it as theft and subterfuge? As a compromise, I let the user select Light or Dark stories. There’s no mechanical difference, but the little paragraph re-contextualizes why one has these photos, and why one wants to re-create them.