That’s right.

Intro

I think there are enough people around here still playing Dwarf Fortress to take another shot at running a succession game, so I’d like to kick off Hexbear Plays Dwarf Fortress: Chapter 2. Last time around, things were a little disorganized, with the duty of organizing the game passing along with the save file. I think we made it about five turns. This time we will try a different approach. I will assume the role of dictator, and as long as I don’t allow my kingdom to fall to ruin, or neglect to reign in my scheming courtiers, every Friday will be Fortress Friday, where we advance the game, put files into the hands of the next player, and recount the events of the past year for our eager spectators and awaiting players.

On this inaugural Fortress Friday (today), we will discuss the scenario, rules, guidelines, and logistics of running the game, as well as putting together an initial roster of players. Based on feedback in this thread, I will generate a world, select a site, perform my duties as Expedition Leader for one year, and next Friday, the initial Fortress Friday post of this chapter will be made.

World Generation

There are a few world generation parameters we probably want to tune. We should also discuss this in this thread (if anyone cares).

Embark

The most consequential decision here is size, with 4x4 being standard. For performance reasons we could do a 3x3. Smaller would be quite caustrophobic. Larger would likely cause performance problems. Another very consequential decision is neighbors. Ideally we end up close to Humans, Elves, and Goblins to maximize trade and sieges (there was a whole siege update btw. Probably the most consequential change since they introduced Z-levels to the game).

We also have choices to make about the biome. Do we want frozen winters? Do we want good/evil alignment? Do we want savage wilderness? What kind of wildlife are we looking for (bears obviously). Other important factors are aquifers, surface water sources, types of available minerals, flux stones, sand, whether we have a sedimentary layer (only place to find fuel ores) or an igneous extrusive layer (volcanoes, magma closer to the surface, but no coke to make steel, which must come from charcoal [trees] or trade). These are mutually exclusive.

Skills

The first seven players (counting myself) can also choose skills for a dwarf if they’d like (or a role if you don’t feel like looking at the whole list of skills). You can also choose a preferred gender, but genders are generated randomly before assigning skills, along with physical attributes like strength and age. I can only guarantee you’ll get a beard.

The initial seven roles have all been chosen. (still open to be amended)

1. Carpenter (myself)

2. Administrator (bookkeeper, appraiser, judge of intent, leader) (@gay_king_prince_charles@hexbear.net)

3. Doc (4 diagnostician, 3 surgeon, 3, medical-adjacent) (@Doubledee@hexbear.net)

4. Militia Captain (any melee (one of axe, spear, sword, or hammer), armor user, shield user, observer, teacher) (@Oreb@hexbear.net)

5. Miner (engraver, observer, fisher/crossbow depending on surroundings) (@Moonworm@hexbear.net)

6. Miner 2 (engraver, dodger, swimmer) (hunter, fisher, herbalist, crossbow, observer) (@context@hexbear.net)

7. Farmer (planter, brewer, cook, spinner) (@booty@hexbear.net)

Names

We also have the opportunity to choose a name for the world itself, the fortress, and the site government, along with an emblem. These are all limited by Dwarven vocabulary and Grammar.

Rules / Recommendations

pending, aside from the fact that the game updates on Fridays. Also not set in stone and subject to discussion.

Generally:

• Each player has one week to advance the game one year, ending on the first day of Spring (open for debate, we could do longer in-game terms). When they have completed their term, they upload their save, and make a comment about their term in the following week’s Fortress Friday post. Include a handful of screenshots. This comment will be pinned (I’m actually not sure who gets the power to do this). The next player continues playing this save.

• Generally, apply a “play it as it lies” playstyle. Don’t save-scum to produce the ideal outcome or revert the pump-stack you just botched. A crescendo of minor errors exploding into catastrophe is what makes the exercise fun. We might revert in cases of outright sabotage though (unless it is funny).

• Some helper mods like DFHack can be useful, but we want to ensure the save is as compatible as possible, so some thought is needed.

• Each player claims a dwarf (by assigning a nick-name) if they haven’t already. The survival of this dwarf doesn’t impact your ability to keep playing.

• In each turn, the player should try to accomplish a noteworthy project. Though simply managing stockpiles and shoring up the food supply are vital functions, they are boring and don’t create much of a narrative to role-play around, or generate interesting visuals. With time, the projects will grow larger and one player might not be able to complete them in one turn. It is okay to use blueprint designations to help the next player understand what you were doing, but try not to railroad them.

Players

Assigned chronologically based on applications, except for scheduling conflicts. Rotation will continue in this order, prioritizing new players and skipping over anybody who resigns.

1. (Beginning Dec. 5) Myself

2. (Dec. 12) @Moonworm@hexbear.net

3. (Dec. 19) @Doubledee@hexbear.net

4. (Dec. 26) (possibly, we’ll check again in <3 weeks) @gay_king_prince_charles@hexbear.net

5. (Jan. 2) (can move up a week) @booty@hexbear.net

6. (Jan. 9) @context@hexbear.net

7. (Jan. 16) @Oreb@hexbear.net

8. (Jan. 23) @Infamousblt@hexbear.net