Nations: Mysore
over 1 year ago – Thu, Apr 13, 2023 at 12:23:08 AM

We're a full two weeks in! At 11.5 thousand dollars, I think we've got a real chance of hitting our first stretch goal for VTT Integration, especially if backers share the project with friends who'd love the project.

But that's enough self-promotion. We've taken a look at your enemies in Guns Blazing, so let's take a look at your allies.

The History of Mysore

Historically, Mysore was a nation in southern India. Ruled by the Wodeyar dynasty, then briefly by Hyder Ali and Tipu Sultan, it fell in 1799 at the end of the fourth Anglo-Mysore War and was thereafter a princely state in British India. Massive famines would regularly kill large portions of the population under British rule, with individual famines estimated as killing about a fifth of the local population. Deindustrialization and other colonial policies would cause significant decline in wealth and standards of living.

But Guns Blazing is an alternate history, and Mysore's fate is one of its big divergences.

Here, Mysore never fell. The Fourth Mysore War was delayed by about a decade and changing political climes (And the British intervention in a Marathan succession dispute) meant that the British Empire had less support from Hyderabad, and none from the Marathas, going into the war. Mysore survives, though it doesn't win the conflict, and with foreign aid continues to survive. 

By 1920, Mysore has gone from an embattled corner of the Indian subcontinent into a heavily militarized, technologically advanced regional power. It's the origin of the combat walker, has made gains against the English, and is now exerting its weight on the international stage instead of simply trying to survive.

The Republic of Mysore

Mysore is a constitutional monarchy with a structure based heavily on the First French Republic and the American government. The Wodeyar dynasty are legally Maharaja, but their position is purely ceremonial, while the descendants of Hyder Ali are technically the sultan, and their position is mostly ceremonial and extremely politically contentious. A legislative assembly and a president manage actual governance. 

Mysore has a heavily industrialized economy. There's a large farming sector, but it's best known for its industrial exports: Appliances, automobiles, engines, and an enormous quantity of weaponry. It has a significant, but embattled, labor movement and various socialist and unionist movements are increasingly popular in politics.

Mysore's foreign policy is inexorably warped around the threat of the British Empire. It bases its actions and alliances on how they will counterbalance the British in case war breaks out, or how they might prevent war from breaking out in some fashion. As such, it has rough alliances with Iran and France and arms an enormous number of insurgent and anti-colonial groups worldwide, often to the detriment of its formal alliances. Conversely, its friendship with non-British colonial powers diminishes its prestige in the eyes of peoples colonized by those powers.

Since the turn of the century, Mysore has begun to flex its power. Arms manufacturers have allied with both reactionary and anti-colonial groups to lobby for political change, often championing a hardline position against the British. Pan-Indian groups see Mysore as the head of a united India, while nationalist movements see the British Raj as an opportunity for Mysore to exploit and enrich itself as Britain has, and anti-colonial political parties want Mysore to stand alongside Persia as a bastion of anti-colonial sentiment throughout the world.

Mysore in the RPG

In the RPG, Mysore is an ally but not always a trustworthy one. From the perspective of player characters, a Mysoran supplier is an incredible asset! Well-supplied, eager for you to cause chaos, and without the vulnerability common to many insurgent movements. However, it's not always clear what part of Mysore you're working with and how well their interests actually align with yours.

Unless you're fighting the British. Then they're fairly uncomplicated in motivation.

It's also a convenient background for a player character: Mysore has a large anti-colonial movement and plenty of Mysoran veterans want to be better than their government often is. A Mysoran soldier who's opted to go Volunteer after leaving the army, or a Mysoran intelligence agent whose handlers may-or-may not know exactly what they're up to, is a flexible background for a PC.

Mysore in the Wargame

Mysore is one of the four launch factions in the Guns Blazing wargame. They're a straightforward and durable faction, with a focus on heavy armor, walkers, and vehicles. They're less flexible than others often are, lacking the numbers of the British, the flexibility of the Green Band, or the esoterica of the Majooj. But what they lack in mobility and stealth, they make up for in a torrent of heavy metal.

Mysore is designed to be fairly friendly to new players: They're forgiving of mistakes, straightforward to play, and can get away with smaller model counts. Their list is broken up between the straightforward Regular Army, and the janky-but-powerful Experimental Cadres, which feature such joys as all-casemate battle tanks,  irradiated heavy infantry, and sniper teams armed with light cannon.

The Squad System
over 1 year ago – Mon, Apr 10, 2023 at 09:17:12 PM

Many combat games have a simple problem: Fights against huge numbers of dudes are really annoying to manage.

In video games, they quickly overwhelm your players or your operating system. In wargames, they bloat game length. In tabletop RPGs, they bloat game length and butcher the action economy. It's an issue.

So you get workarounds: Simplifying enemy logic, loading in stuff as it's needed, only resolving what you're paying attention to, etc. etc. TTRPGs have had more difficulty doing this successfully than other systems, Minion mechanics in 4e and Genesys have had promise, Exalted has its battlegroups (For better and for worse), MCDM is currently trialing its own spin on minions, and one of my first TTRPG contracts was on Formations. Hellpiercers, which is still funding, is trialing its own take on swarm mechanics as we speak.

But Guns Blazing is based on First Person shooters, a genre that relies on large numbers of dangerous-yet-disposable foes. It needs a way to handle a bunch of foes in a fight, and it needs this to work well and be fairly swift at-the-table.

Enter the Squad:

The Squad Trait

Many enemies in Guns Blazing have the Squad trait. Formatted as Squad (x), this trait all of Guns Blazing's minion rules.

If multiple enemies of the same type with the Squad ability are in a fight, they form a Squad. Squads simplify a group into a single enemy for the purpose of bookkeeping: They activate together, they make attacks together, they only roll once for opposed checks, if you have multi-injury squaddies, injuries are applied to the squad as a whole rather than individual foes, etc.

Each Squad has a Squad Rating (The number in Parenthesis). Squads gain a single bonus die per squad member who would normally participate in a check, and a single bonus activation per squad member, capped at their rating. Ie. Squad (1) Sporelings only gain 1 bonus Activation and 1 bonus die from swarming players in melee combat. Squad (3) Restitched Cogs gain 3.

This encourages approaching squads tactically: You want to slice corners and take Squads a few at a time to minimize their bonuses. Rushing in against the odds is risky (If, potentially, enormously rewarding). Squad bonuses and Ahadi's focus on opposed checks also provides Squads a bit of durability: Being up against a single, larger dice pool means that Squads are effectively a single, multi-wound opponent you're aiming to dismember and then finish off.

This also makes particularly large squads less overwhelming. While health keeps scaling, adding more enemies past the squad cap increases robustness, health, and area control without increasing morale, danger, or action economy.

However, each member of a squad is still an individual. They can be affected by status conditions, targeted individually, and have different weapons. You can have a sergeant, machine gunner, or named NPC in a squad without having to break them off as their own part of the initiative track. Some might even bring in their own special abilities that can be removed by killing the appropriate squad member.

Why Squads

The Squad system has its own tradeoffs: It's more tracking than, say, MCDM's current approach. However, the flexibility provides an important lever for DMs in an early-modern setting and for shooter-derived gameplay. It lets you throttle the threat of squads via specialists and run large fights with a minimum of overhead while still providing players intuitive tactical choices to make when engaging. 

It also works on the same logic as the rest of the system: You don't need to learn a new way that health, conditions, AoE abilities, or movement work. A squad attritions similarly to large monsters and hostile vehicles, maneuvers similarly to other infantry, and has similar damage output to other threats.

We're funded! & The Tier System
almost 2 years ago – Thu, Apr 06, 2023 at 09:07:16 PM

This was meant to be up on Tuesday but I, tragically, fell ill.

Fortunately, that means WE'RE NOW FUNDED.

Absolutely incredible. Thank you to everyone who backed for pushing us over this milestone. Over the next week (Health allowing), I'll be talking about our plans for STL files, stream kits, and supporting Guns Blazing after the initial book.

But before that, let's talk about character progression.

What's in a Level

So when I'm talking about character progression the mind goes to level and XP spend systems, which work differently but with the same end goal: Providing a structure for players to improve their characters in meaningful, discrete, and manageable chunks. The specifics vary quite a bit: D&D alikes use discretelevels, the Dark Heresy line has XP purchases with tier rankings based on XP spent, Storyteller uses XP purchases with tier rankings purchased with XP, PBTA games have their own methods of purchasing Advancements, and there are interminable other options. All of these shape how the game is played and how progression feels.

A leveling system is going to be a similar experience between players. While there are ways to level 'incorrectly', and therefore suboptimally, you can generally rely on characters getting the things they should as they go. You aren't going to get characters just missing important bits of their toolkit unless you've made a pretty unfortunate mistake. However, if you don't have a variety of options in a level characters in a given class are liable to end up overly similar to each other. 'Monobuild problems'.

A pure XP spend system is far more varied. You allow for a truly incredible variety of character builds: Whatever can be engaged with in your system is a valid basis for an entire character concept! However, this makes it easier to have characters that don't fit well in common game situations: A social face who has nothing to do when guns are drawn, a hacker who forces everyone else to sit down and twiddle their thumbs while they do their thing, or characters forgetting to purchase health and ending up very, very fragile at fairly high XP counts. It encourages pursuing flashy purchases with your carefully hoarded xp, which can result in extremely monofocused characters. 

I can go over examples and their downsides pretty much indefinitely. What's important is this: All of these approaches have their own limitations and drawbacks, you just have to pick what fits your system.

What are Tiers

Tiers are an XP-with-Tier-Ranking system. You have a Combat Tier and a Narrative Tier, each rated from 0 to 4, and each determining how skilled you are in that field. As you progress, you'll spend XP on various Perks, which give you additional power and play options. When you purchase a certain number of perks, or hit certain narrative milestones, your tier increases.

When your tier increases, you get a variety of passive bonuses. Additional skills, boosted Aspects, additional Injuries, etc. You'll also unlock requirements for new perks.

Tiers are tied together by default: Whenever you purchase a combat perk, you get a narrative perk. Whenever you increase one tier, you increase both. However, options are provided to separate these for your campaign. You can play a team of hyperlethal, Tier 4 Combat badasses who suffer greatly outside of it due to being at Narrative Tier 1, or a group of skilled professionals in their field at Narrative Tier 2 but who are in a survival horror scenario because they're all Combat Tier 0. Theoretically you could delineate by individual character, but it isn't recommended.

Why Tiers

I wanted the flexibility of a XP-spend progression system, but needed to constrain it to ensure a good play experience for new players. Guns Blazing is fundamentally a game about cool gun fights as much as it is one about colonial politics, so everyone needed to be able to engage with cool gun fights. Playbooks like the Captain and Engineer exist if you don't want to be rambo, but everyone needed a baseline competence that wouldn't fall behind their fellows because they wanted to grab some out-of-combat tracks.

As such: split-linked tracks. You get a solid combat build with the same resources as everyone else and a narrative build with the same resources as everyone else, and they increase at roughly the same speed. You can be better or worse at a given thing, specialize as you please, and differentiate your characters pretty dramatically, but you'll be on a basically even footing in gameplay when you're new to the game.

And, as the tracks have been codified as fully functional separate organisms, you can then de-link them for specific scenarios (Comedy of error with murder machines or survival horror), or split them up between players once you're more used to the system. You could even add new tracks if you have an idea for a subsystem or expansion. Like a less ludicrously detailed version of Battletechs many optional rules.

I'm not going to pretend it's a simple system, but I think it's a powerful one and one that I'm eager to see people mess with once they have the full game.

Supernatural Threats: Iram
almost 2 years ago – Mon, Apr 03, 2023 at 08:21:11 PM

9K passed! Absolutely incredible. With that behind us, let's get a better look at one of your most prevalent foes in Guns Blazing: Iram

What is Iram?

As with all Supernatural Threats in Guns Blazing, there are two answers. 

In fiction: Iram is an ancient fungal parasite, inadvertently reawakened by the British Empire in the late 18th century.   It feeds on blood, sweat, and suffering, infecting victims, then working them to death or devouring them outright to spread its spores and create fungiform monsters. To get access to victims, it makes deals with the powerful, offering them fabulous treasures and loyal monsters if they but aid and protect it.

Narratively: Iram is colonialism as a parasite.  It's a literalization of the extractive mechanisms, and the wealth they afforded colonizers, common to the period, and how those systems perpetuate themselves once the colonizer is gone. Iram is mercenary rather than ambitious: Should a colonial power be defeated, it's happy to make a new deal with those in charge to maintain access to victims. 

It's not going to slip its bonds and become a world ending threat, it needs people to protect it from its own victims, and there's never going to be a grand reveal that forces everyone to work together to defeat it.

And that means it will happily persist so long as there are people to feed it.

A History of Iram

Iram is a city mentioned, very briefly, in the Qur'an. It was a city of grand and lofty pillars, whose rulers spread oppression on the land, and it was divinely destroyed at some point. More extensive descriptions tell of a city with grand buildings ruled by a horrible tyrant and wiped out by sandstorms (Or destroyed in a cataclysm that created the Empty Quarter).

Iram's been a periodic feature of genre fiction (Especially lovecraftian horror) due to both orientalist retellings of Islamic legends and Lovecraft mentioning it in the cthulhu mythos. These depictions tend to drop the religious and historical elements and make it a broadly depicted lost city, often with lovecraftian trappings.

Guns Blazing tries to bridge the two: Iram is an embodiment of the city's sin as a mystical threat.  It's uncovered by British archaeologists in the late 18th century, inadvertently revived, and promptly started making deals across Europe as the colonial era entered its apex.

Iram in your Game

Iram is attached to most, but not all, colonial empires. It's most prominent in the British empire, with varying prominence elsewhere based on in-fiction political factors. The USA disdains Iram as a European invention, Portugal and the Ottoman Empire consider it politically controversial, while Spain is clinging ever-closer to it as its colonial empire crumbles.

This means it's going to be a prominent foe in most campaigns, where players will face off with Iramite fungiforms and destroy iramite infrastructure. 

Fungiforms are monsters created by Iram to do its bidding, rnaging from dog-sized Sporelings to towering Grenadiers and Subalterns. Fungiforms are normally deployed in support of their human masters, but aren't particularly formidable foes on their own.  They tend to have abilities that help their human masters, providing cover against attacks, guiding their shots, speeding their movements, or just providing a well of disposable bodies players must account for.

Iramite infrastructure are implements of colonialism: towering fungal factories and farms, turning the blood and sweat of the oppressed into alien treasures. Hidden nests, counting and surveiling the populace to grease the colonial machine. Fruiting garrisons, deploying monsters to enforce the will of colonial administrations.

Most upsetting, however, are the infected. Iram infects many of its victims with its spores, sapping at their vitality. To a healthy person, such an infection isn't dangerous, but it is insidious. And when the infected die, the spore consumes them, turning their body into fungiforms, spreading the infection, or integrating it into Iram's next design. 

Of course, infection can be cured. A few months away from infection vectors, a few days of medical treatment, or even some quick field medicine can all get rid of the issue. But the infected are rarely allowed such luxuries. They're indentured laborers, the working poor, and those with few other options. 

Others are volunteers. Colonial soldiers trying to serve their country, sure that if they just serve well enough they will earn the respect afforded white soldiers. Standing in the way of liberation for reasons heroic and venal, and just as dedicated to your defeat as any European soldier.

While You're Here

Look, if you're here you probably like punk fiction in the original, anti-authoritarian definition of the term. You are on board for ruining the day of some rich prick, maybe to make the world a better place, or maybe just to scrounge out a living in an increasingly desperate world. And if you can do it in the warm, relaxed atmosphere of a tropical vacation, all the better!

If that's your jam,  check out Ettin's latest project: Wetrunner! It's a cyberpunk heist RPG set in a post-climate collapse earth.  Enjoy the eternal summer dystopia! Infiltrate the tropical estates of rich assholes! And, when they least expect it, steal all their fish.

I've been reading and playing Ettin's work since before I joined the industry. He's a talented designer who creates really fun settings. If you enjoy any sort of cyberpunk action, im sure itll be worth your while.

Fixed Discord Link
almost 2 years ago – Sun, Apr 02, 2023 at 06:02:52 AM

This post is for backers only. Please visit Kickstarter.com and log in to read.