DanDare2050
Mongoose
Hi, this is a topic I have just started over at RPG Geek: https://www.rpggeek.com/article/26391055
I will reproduce my opening statements here.
In the real world I formed and run the Kenmore Role Playing Society.
We have an Open Table D&D campaign that meets twice a month. 3 GMs (2 more in training) and 19 players have joined since we started in January. (Look at my Big Index to find all the session reports)
I'm looking at building a parallel open table using Mongoose Traveller 2e.
Its a tougher ask. The nature of space travel in the game means that the 1 to 1 mapping of real life dates to in game dates we use for D&D won't work. After careful consideration and tinkering with alternatives I'm planing to go with 1 IRL day to 7 IG days. So if the sessions are 2 weeks apart in real life then they will start 14 weeks apart in the game world.
I'm also thinking of playing live online using a mixture of Roll20, Discord and whatever other software tools help us along.
I'd like to discuss the design of the open table methodology for Traveller here and also take expressions of interest for GMing and Playing.
The first aim is that there should be multiple GMs, each in charge of a sub sector. Players will join at regular play sessions and move their character to which ever sub sector they are playing in (simply depends on availability of spaces at GMs virtual tables and order of arrival).
GMs are responsible for their campaign data and managing changes as factions etc do stuff over time.
Players will each be responsible for their character and assets and need a way to move that information with them from one sub sector to the next.
Player owned business assets or any planet/star system based assets are probably part of the GMs notes and the GM can apply changes to them over time as they see fit.
Roll20 doesn't really afford a mechanism for this so I'm interested in ideas about how this may be executed.
1) Players joining a session
2) Players moving their data about from GM to GM
I will reproduce my opening statements here.
In the real world I formed and run the Kenmore Role Playing Society.
We have an Open Table D&D campaign that meets twice a month. 3 GMs (2 more in training) and 19 players have joined since we started in January. (Look at my Big Index to find all the session reports)
I'm looking at building a parallel open table using Mongoose Traveller 2e.
Its a tougher ask. The nature of space travel in the game means that the 1 to 1 mapping of real life dates to in game dates we use for D&D won't work. After careful consideration and tinkering with alternatives I'm planing to go with 1 IRL day to 7 IG days. So if the sessions are 2 weeks apart in real life then they will start 14 weeks apart in the game world.
I'm also thinking of playing live online using a mixture of Roll20, Discord and whatever other software tools help us along.
I'd like to discuss the design of the open table methodology for Traveller here and also take expressions of interest for GMing and Playing.
The first aim is that there should be multiple GMs, each in charge of a sub sector. Players will join at regular play sessions and move their character to which ever sub sector they are playing in (simply depends on availability of spaces at GMs virtual tables and order of arrival).
GMs are responsible for their campaign data and managing changes as factions etc do stuff over time.
Players will each be responsible for their character and assets and need a way to move that information with them from one sub sector to the next.
Player owned business assets or any planet/star system based assets are probably part of the GMs notes and the GM can apply changes to them over time as they see fit.
Roll20 doesn't really afford a mechanism for this so I'm interested in ideas about how this may be executed.
1) Players joining a session
2) Players moving their data about from GM to GM