Appreciate I’m answering my own questions but…
Q1. Yes I think so but then I wouldn’t have proposed it otherwise!
The wide variety of house rules versions present on this site demonstrates to me that others also would consider it worthwhile and having been doing this independently. Whilst I don’t consider a Living Rulebook as replacing people’s own House Rules or Home Brewed content*, it may at least give a starting point for people to build their own homebrew material on if they wish, safe in the knowledge that they are starting with ALL the official content in a single place and that the most obvious and possibly least contentious bugs have been fixed.
Another important reason for me, is that one of the strengths of HeroQuest is that is isn't a Game, but a Game System i.e. player are actively encouraged to create their own Quests. Not having a definitive rulebook makes that task harder as you are never quite sure which version of the rules, which interpretation, which expansions those that choose to play your Quest might be using
*For the 2021 generation (i.e. those that have discovered HeroQuest as a result of the reboot or reprint), some of them may well not wish to spend 3 decades debating the finer points of game law (or lore) although they are welcome to, but equally they might appreciate a reference document that resolves some of the problems that they spot during play!
Q2. Personally I would like us to aim for consensus, which is not exactly the same thing as unanimity, so for example if I was to make the following proposal:
Can anyone give me a compelling reason why we shouldn’t use the US edition as our starting point?Provided that no-one, after a suitable period of discussion and a one month cooling off period, has provided a compelling reason why we shouldn’t, then we do it.
Q3.
Can anyone give me a compelling reason why we shouldn’t use the US edition as our starting point?See what I did there!
HQ2021 - I feel (I'm not a copyright lawyer) that the HQ2021 really belongs to Avalon Hill / Hasbro and is theirs to take in whatever direction they feel is appropriate, so I think we should leave well alone
Japanese Edition not only has the additional complication of translation but is quite different from the others, so that's a NO from me.
Of the other versions I'm working on the assumption that the more recent is the best (I did say that was an assumption!) hence my recommendation above. Of course if there are problems with elements of that version, then using the relevant EU rule instead, maybe a valid solution.
Q4. Having decided on our starting point, do we want to leave it formatted as per the original or modularise it?
The layout of the original rulebook leads to repetition and duplication of the same or similar rules, such as rules for Hero movement, Hero attack, Hero defence and so on and separately rules for Monster movement, Monster attack, Monster defence and so on, by converting this into a modular format and having a separate module by theme, e.g. movement, combat, spell casting, searching and so on, we can reduce repetition and duplication and make a clear distinction between topics (modules) making the rulebook easier to use as a reference document for players especially Zargon and by indexing this modular format we can facilitate discussions and modifications to specific rules and modules. As an example, and we don’t need to use the same layout, my HeroQuest Gold rules below show the application of such a modular approach
My natural position is to modularise it, it is more work up front, but makes it easier to maintain on an ongoing basis, as the idea of a living rulebook is that it is maintained eternally so less work in the long run.
That said agreeing on a new format might derail the project before we get started, so perhaps a hybrid method would be best. Initially we take the easier route of using the existing format and starting work, whilst in parallel kicking off discussions around modularisation. After a given point in time, perhaps 3 months, we can decide to either retain the original format, or to modularise based on the format that has been agreed (assuming one has), otherwise we stick with the original and continue or abandon the modular decision as we see fit. That way it doesn’t hold up any progress.
*For various reasons, copyright, size and simplicity, I would suggest that any base version omits all ‘narrative/story’ text, artwork, images and similar material and just sticks to text
If we decide to modularise it and agree on a new format, can we and do we want to apply that same modularisation to the ‘official rules’ forum?
Q5. My preference is “HeroQuest Gold: The Living Rulebook”
It contains the word ‘HeroQuest’ which is an excellent start, it describes what it is ‘The Living Rulebook’(I’m thinking of search engine optimisation here!) and the Gold bit is a thematic and catchy (easily to use short form) and is intended to invoke a ‘gold standard’, that serves to unite all the various versions. We could even have an icon that can be applied to Quests that have been (re)written to meet the standard
Q6. How best do we arrange this on the forum?
I’m probably going to wait until I get some options from those that are in the know on this, from a technical forum point of view, but some initial thoughts below
• HeroQuest Rooms -> Official HeroQuest Releases -> Official Rules is THE place for discussions around the official rules, all discussions around the official rules do sit in there and must remain in there.
• Project Discussion Thread: Discussions around the Project itself (NOT the rules) can be done under this topic (although this does need moving to the 'Project Forge')
• Rules of Engagement: maybe a sticky one that only 'Project Admins' can post to, where we can cover standing instructions, quick reference, what is the project, what is the scope, why are we doing it, how do I contribute, where can I get hold of the latest version, and perhaps a road map, news & announcements and similar
Q7. How do we keep momentum on this Project?
Establishing a regular cadence, setting a time limit for a particular discussion (for example 1 month), after which time we will see if it can be brought together as a proposal, if so then publish the proposal, give people 1 month to raise objections before putting it into the new version
Working in parallel, like the example above, have a side discussion about modularisation, if that ever comes to a point of agreement then it can be incorporated, if it doesn’t then the main work continues regardless
Publish indicative dates, such as we will publish a new version every three months, that will include whatever has been agreed by this point.
For example:
Timeline / Roadmap (by end of month indicated)
NOV2022 Need to get feedback on the key questions above especially Q1 but also Q2-Q6 - obviously if the outcome of Q1 is not to do this then it won't happen!
NOV2022 Publish draft 'Rules of Engagement / Project Charter agreeing the project goal, scope, method of decision making and so on i.e. the output of the previous step
DEC2022 Start to put together a text document of the basic ruleset, i.e. version 0 including cards and similar, including all expansions (to be completed by end Jan 2023) and work out where, when and how to publish this, plus need to decide whether to keep the original formatting (for now) or reformat and if reformat then how? Need page numbers for reference on this document
DEC2022 Need to discuss and agree and document how these posts are going to be arranged/managed on the forum (for example where should they sit, how do we want to format the topic subjects and the posts themselves, one topic per thread, prefixes) then these discussions can start at this point in parallel to anything else
JAN2023 Publish JAN2022 version of the Living Rulebook, this version 0 will be the starting point for all modifications
FEB2023 Publish next version, incorporating everything that has been agreed for inclusion by that date
Q8. Other Questions?
Where/how best to host the document(s)?
What format to work in Word, PDF?
Fonts to use?
One single document or multiple?
How best to implement version control / document control / change logs, do we need to make modifications in a different colour, retain original text but struck-through?
What language should we do this in? Obviously the Queen's (sorry King's) British English is the correct answer, however if we go with the US Edition as a base I'll just have to get used to spelling things wrong
