Home Creators Posts Import Register Favorites Logout

Content

So I mentioned this one awhile back, but got tied up in family stuff for a bit.

That said, the update is finally out. The changes here are.. fairly straight forward.

I added Morkborg to the game list.

.. there isn't a ton outside of that. (Although there were a lot of random bug fixes, and some redesign in the back.)

So disclaimer: I'VE NEVER PLAYED MORKBORG. So if something doesn't make sense, let me know.This one was done for the community, since D&D gets all the love but other systems kind of sit on the side.

Up next is Mothership, and.. I guess CAIN - since someone on the Discord seems very enthusiastic about that.

I can't promise timelines on those as I'll be starting on Smoke&Spectre 3.0 soon, and that might eat into my time.

Enjoy~

Files

Comments

Jorge Raphael

Hi, if you need some ideas for Mothership I'm currently playing a campaign, and I'm looking forward to migrating my Notion character sheet to Chronicle.

Battle-System

Appreciated! I do have some questions. The standard sheet has a lot of template/notes for how values should be assigned. Kind of like X leads to Y stuff. But then I also saw a compact sheet that does away with all of that, and just has spots for the values. Which is more useful? What's actually needed in standard play? What kind of things do people need, but aren't present? I also saw a ship sheet. How does that play into things? Does the GM run the ship? Is the GM also a player?

Jorge Raphael

The standard sheet works best for in-person and one-shots, for VTT the compact form is better. I can send you an example of the foundry form that uses the compact form. The ship sheet is visible to everyone.

Martin Nelson

Thanks for the continued work on this. I do have a question though, is there any chance that tying the sheets to the specfic Owlbear room is possible. It's probably way too complex, but as the GM of a lot of games, I have two rooms that my different groups play in. For Chronicle! it's not too much of an issue because I can have players fill in their own sheets, but things like Journal! feel like it would be helpful to tie them to the specific room. That way my Forest group and Lakeside group will only have access to the notes specific to them. For my own organisation, being able to only see Lakeside group's sheets in their room, and the Forest group's sheets in another would be helpful. If it's not possible or too complex to implement no problem, but if we don't ask...

Battle-System

(Stupid enter sent comment early.) In my head, there are a few issues with tying it to a room. From a technical standpoint and a QoL standpoint. - If the sheet is tied to the room, you can only ever edit that sheet within that room. - If the room is deleted, you no longer have access to that sheet unless you can somehow re-assign it. - If you have to assign sheets to rooms, it adds a different layer of complexity for upkeep because now I'd have to add more sheet management tools/logic. (Which would be fine for some, but confuse others.) Both extensions currently use LocalStorage as a base, with the remote storage if you opted in. They SHOULD be saving which slot you were on last. So for your Lakeside game that you GM, if you last used slot 3 on that room - the room saves which slot you were on. So when you hop back in, it'll go right to slot 3. - The players in that room can only see the sheet the GM has active for the party notes, so they'll never see the Forest game notes. - Their 'personal' notes are specific to them, and saved on their own machine (or remote). So no one would see those except them anyway. So I get where you're coming from, but what it came down to in a lot of places is that I opted for simplicity in some places because it's easier for people to just.. hop in and get going. I know there are a lot of tech savvy people online, but I also play with a lot of un-savvy people who tend to just give up when things get confusing. So I generally opt for, "Can my mom use this?"

Martin Nelson

Thanks for the response and yeah, that absolutely makes sense. We all have our own organisational systems and yeah, I wouldn't want to unfairly impose. The system is working quite nicely so would hate to see a suggestion cause it to break! Thanks again and look forward to seeing whatever comes next.