FTL Punk: Anarchy in the KU*

The FTL Punk festival is a gathering of the best* punk bands from across the known universe (KU), performing free, all-ages shows across a few ramshackle stages just for the joy of it. This cycle’s festival just so happens to be taking place on Dregulon IV, a world which has completely outlawed punk of all sorts – music, fashion, and especially attitude. It’s a delicious combination that no properly righteous punk would dream of missing.

The plan was for your band to touch down near the festival, soak in the scene for a day or so, and then put on a hell of show.  The reality is that your tour bus is crash-landing in the wilderness of the planet, and you'll have to hoof it across a series of hostile environments in order to make it to the stage on time. 

This game features everything you'll need to run up to five players through a ridiculous, action-packed story about punk rock, community, and resistance:

• Five pre-generated characters for band members with unique personalities, specialized gear and abilities, and unlockable special upgrades
• Basic rules for resolving actions during a scene  
  
• Rules for creating and performing a punk rock song in the middle of a scene
• Eighteen exciting locations split across three sectors:
  • The hazardous wilderness of Dregulon IV
  • The hostile urban settings within Capital City
  • The FTL Punk Festival Grounds, under assault from corporate influencers
• Guidelines for running the game as a one-shot, or across multiple sessions
• A VTT created in Google Sheets so you and your friends can play online

 This game was created for the Havoc Engine Jam, and uses ideas from the Havoc Engine, created by Rowan, Rook and Decard.  It borrows heavily from the tone and gameplay of Eat the Reich by Grant Howitt. 

The VTT uses Google Script to handle dice-rolling and some display automation.  This will require all players to authorize the script prior to using those functions.  The script was entirely written by Gemelli, and can be reviewed prior to copying/authorizing the code.  The data that can be accessed by the VTT code is explicitly limited to what is within your copy of the workbook itself.