|Patrick Harris @ MU|
|4 people marked this as a favorite.|
Folks, over in this thread it has become very apparent that people are confused about GM Star replays and whether or not they renew.
Here is the text from the Guide, page 20, with relevant text bolded:
Alternatively, campaign GMs who are recognized for their efforts by receiving GM stars (see page 37), may receive additional player or GM credit for a number of non-Tier 1 scenarios or sanctioned modules per GM star they have earned. For example, a three-star GM may select any three scenarios or sanctioned modules that she can then play or GM for credit one additional time each. For each of these adventures, she can thus earn a total of three Chronicle sheets, rather than the two normally allowed. When replaying a scenario with GM-star credit, the GM completing the Chronicle sheet will annotate the Notes section of the Chronicle sheet and add “GM Star Replay Credit × Star” to annotate the use of star credit replay. The GM Star Replay Credits are a once per star, lifetime benefit.
The confusion stems from the fact that the "Beta" version of the Guide 5.0, which was released before GenCon 2013, said that they would renew every season. However, from the time the Guide went live, the policy has been "lifetime"; this is not a mid-season shift.
If you have a version of the Guide that says otherwise, you need to download the new version of the Guide!
Now, it is possible that this will change in the future, but time will tell.
Finally, I want to note something here: I am concerned that this is going to be blamed on the fact that the Guide sees a beta release at all. While I definitely absolutely agree with the general sentiment that the next beta release should be clearly marked as such--not least because at least a few of the people who expressed confusion in that other thread are Venture Officers--I think it's worth noting that the confusion was internal as well as external (note not just the linked message but the one it was replying to, please). I don't think the policy of releasing the Guide early, for feedback, is to blame; it was in fact that same early release that caught this error. While the process of release obviously needs some refinement, let's not throw the baby out with the bathwater.