Best practices for running games

[dcgreenwood]

This is a pretty broad question, but I've spent a lot of time building a campaign and soon will be faced with running it. There are so many options for navigation and organizing, I'm wondering what other users are learning as the best approach to navigating during play. Do you primarily uses the relationships panes to jump around, build complex plot webs and use that for navigation? I'm a little afraid I may find when I finally run it that I missed some tricks for entering and linking content that will hamper my using it for game play.

[Acenoid]

So far I have it used just for entering my data and campaign planning. Here are my results from my first session I had a few days ago:

For my first session I used it only for articles / rules reference and some tracking of enemies. The remainder I updated afterwards. Also I just use a laptop for tracking my GM's notes.

Unfortunately the handling for map / revealing them and putting them on player windows seems to be to complicated. There seems too much clicking / confirming / handling of tabs involved, so I make a quickly drawn map on paper for the players at the moment. Maybe I will add those steps at a later time as well, but currently I dont know.

I contained only "related" groups, which I also want to change. It is no problem to contain a relevant topic under a, for example, adventure area, if you will most likely need it when the group is there. So link / contain / group / tag topics that are related, so you have a multitude of ways to get to the topic.

For me I have seen that it is important for the future to build some "hubs" for the quests, where I can reach the relevant links quickly.

Also I want to track player progress in some dedicated topics (also für my reference) e.g. active spells or permanent effects or important decisions from a particular character.

I would not expect to much from the first session and overwhelm yourself. Just add it step by step so you feel comfortable.

I recommend you read the tips and tricks manual as it contains a lot of answers. Just read what youre currently interested in. They suggest for example to open needed tabs before hand and arrange the items to show in the player view also before the session.

[dcgreenwood]

I completely forgot the tips article existed until after I posted this and yes, it answered some questions. I did my first player view trial and had the same reaction you did...lots of clicks to reveal something. I are why they suggested preparing tabs and windows ahead of time. Once they are prepped and you get the sequence down I think it will work, but I think hours if practice before the first session may be needed. The article dealt with the hub concept using storyline so I will try that. I also see how it suggested using casts and the like to organize rather than "relationships" and that makes sense.

[Vampyre]

I've yet to run my first campaign with Realmworks, so all I did so far, was to create inside RW. But here are my thoughts.

On my first settings, I first read the full book, understanding its concepts. Then, I started to create the universe in which my players would be evolving. And when the universe was created, I started a plot. Now that my first plot is done, I feel myself totally lost. I have too much material inside RW that need work, and am completely overwhelmed. Not to mention that when I started working on the character sheets (an electronic one, using a special program in doing them since my game system is not in HL and won't be due to copyright issue with the current holder of the rights), I noticed many flaws in the game system, and even stats that are not covered in any books. So yeah, a system broken, and to much information inside my campaign, and I don't know what to do next.

In about a week or something, I will receive my books for two other settings, using the same rules. And here is what I plan on doing : first, read and type the rules inside RW as I go through the books. Like that, I'm never overwhelmed by the description of the rules. I learn one rule, I bring it to RW. Like that, by the end of the book, I will have all the rules under my hand. And I will only bring what I need for my next playthrough.

What I did good though, I will keep on doing again. And that is to create groups where groups are logical. And using a very heavy system of tags / groups / links / and anything possible. This allow me to jump wherever I need from wherever I need. Linking my plot is also mandatory to me. Just a quick sentence in the plot, and a double click later, I can access anything relating to that particular scene.

For the reveal, I play only face to face, in a club. There is no TV where I play, and no internet. So the reveal is useless to me, and I won't comment on it.

[AEIOU]

This doesn't answer your question directly....

I use RW primarily for campaign development, session planning and session resolution. It's a repository for all gameplay information. It remembers the links and little details for me. Map reveal, rumor tracking, treasure details.... It's a database.

I use RW for module dissection/integration. I enter the material and make changes to names, places, events to match my needs. I reorganize and reorder material from paragraphs to appropriate snippets. I create cast lists and location lists so I can quickly find things. I create links between NPC's to better understand their dynamics.

I do not use RW for any rules mechanics. I'm story heavy; rules light. In my games rules are merely guidelines and I seldom actually refer to them preferring to hear how the characters plausibly resolve situations in-game rather than relying on tables and dice and rules.

I do not use RW for any in-game player presentation. Nor do I plan to.

I use RW at the table for looking up encounter information and as a reference to NPC's, locations, groups, etc. It's really wonderful to have it all at my fingertips.

The one place RW falls miserably short is in regards to interacting nicely with programs other than HL--it can't export. I have to maintain a separate directory for images and maps outside of RW and d20pro.... This irritates the bejesus out of me. I import all of these images and maps into both programs (doublework) and can't get them out of either.... So if I must maintain a third copy that isn't tied to either program in case I need to make edits which is starting to cause version control annoyance. Sigh.

I use d20pro for gameplay at the table. Maps, dice rolls and combat tracking are all nicely handled there.

I use HeroLab for PCs, NPCs, mobs and encounters. It integrates nicely with RW and exports nicely to d20pro.

[Acenoid]

I agree the images are a hassle. I hope they can improve on that. Windows has so many options, embeedding objects and hopefully support for other tools is extended and embedded more nicely.

[Farling]

Originally Posted by AEIOU

The one place RW falls miserably short is in regards to interacting nicely with programs other than HL--it can't export. I have to maintain a separate directory for images and maps outside of RW and d20pro.... This irritates the bejesus out of me. I import all of these images and maps into both programs (doublework) and can't get them out of either.... So if I must maintain a third copy that isn't tied to either program in case I need to make edits which is starting to cause version control annoyance. Sigh

RealmWorks allows you to add a Foreign Object snippet. I use this to add a file of monsters which can get loaded into Combat Manager for actually running encounters. Clicking on the foreign object snippet immediately launches Combat Manager and loads the file.

[AEIOU]

@Farling: That is really cool to hear. I'm hoping that something similar happens with d20pro and RW where I can create material, store it in RW and share it to d20pro.

My point was that once you put something into RW, you can't get it out. You can't edit or make changes to it once it is embedded into RW. Linking to CC3 or PhotoShop like the Foreign Object snippet linking to Combat Manager would be great -- then we could manipulate what we have input and we can save it to other formats if we like.

RW has a lot of growth ahead and I'm very hopeful that the implementation of data sharing will include better data import and the beginnings of data export.

[Parody]

I'm on the other side of this one: I would never want to save my source projects into Realm Works because I want revision control. I keep all of my maps, handouts, and other projects in a version control system and back up the repositories. Realm Works is only going to get appropriately-sized output formats. Yes, this means I have to replace the graphics or whatever in Realm Works when I change things, but that's just part of making revisions.

Looking towards the future, this also means that by only putting browser-compatible data formats into the database it shouldn't matter what platform my players use to view things. (RW was planned to be Win/Web/Mac, after all.) It also means that I'm not taking up extra space in my server allotment storing both the source and output formats of the same item, which can be hefty for certain types of files. There's also side issues for larger projects like player handouts that use linked graphics files.

Don't get me wrong: you should be able to export graphics and other imported objects, but there are good reasons you might want to keep their sources separate from your Realm Works database.

[AutoDMC]

I've now run three sessions with RealmWorks, and while it's great for organizing my game universe in my head, I find that it's a bit cumbersome to use in the actual session. (At least until some sort of player viewer is actually available, but I've already beat that drum in another thread.)

The only feature I really use in Player View are maps. The "Fog of War" isn't too hard to manage, and my players are usually patient enough when moving that they don't mind the delay. Also, it adds a bit of tension because they have to do Notice checks when they travel and the extra DM time always makes them wonder what they may have missed

Everything else is just too clumsy at this time. Data windows are small and hard to read on my screen, so I end up reading them over the air anyway. At this time, as far as my players are concerned, this is just a regular game. They have notepads they scratch notes on just like they always do, because it's easier to reference their notes than to ask me to pull up a data sheet that may or may not have been filled with that data.

Additionally, while the system is nice for planning, I've found it way too cumbersome when I need to create on the fly. I have a notepad that I scratch my on-the-fly creations on as the party navigates the dungeon/vault/city, and then after the session I smash the data into the database.