- Homepage
- http://www.interactiveliterature.org/O/Schedule.php?action=25&EventId=677&RunId=1262
- LARP
- 1870: Container
- Date
- @ 8 p.m.
- Convention
- Location
- Radisson Hotel, Chelmsford, MA, USA
- Notes
Run at Intercon O.
- Description
by Jason Alonso and Catherine Havasi
The year is 1870 in London, England. It is the time of Jules Verne and Charles Dickens. Technology is advancing at an unheard-of pace, new discoveries are being made every day, but grime and poverty are commonplace. A new class of industrial magnates find themselves catapulted to power, their family businesses transformed almost overnight into influential new industries. But Europe is a powder-keg waiting to explode, and an uneasy war has just begun between France and Prussia.
Against this backdrop, a trading summit has been called on a floating museum in the London Harbor. Aboard this stationary and seemly impossible craft, five magnates and their entourages have been summoned by a shadowy but failing industrial power named Rose & Prop. It promises to be an opportunity of a lifetime to exchange goods and make connections. It seems to be an evening full of singular opportunities... what could possibly go wrong?
Container is a game about industrialization, mass production, and the modernization of science. It is about the legacy parents leave their children. It is about searching for mystery in a world that seems to have none left.
Container focuses on role playing, character, and discussion with no easy answers. It is a historically-consistent yet alternative history with actual historical figures as playable characters, is relatively mechanics/combat light, and has long short-story style character sheets.
Hi! So, I've not really touched this website for years. It's fallen into disrepair and it would be irresponsible of me to pretend I'll ever have time to work on it again.
So, I'm going to mothball the site/set it to read-only. I've disabled the login links because they stopped working any I don't remember enough about how the site works to figure out how to fix them.
If any thing *really* needs updating (deadnaming-level stuff), let me know and I'll go in on the backend and make changes.