Okay, so I stayed up late and put together this fat wall of text to outline the design and review processes for EoV. Let me know what you think and if there are any gaps in my understanding.
A key question is whether advancing stages in the Workshop is vote driven or design lead driven. I think votes aren't needed actually, since votes are taken during the ERB, and rejection there can just move things back into the "Blueprint" thread for refining the design.
The Engineers of Valhalla Charter
The Engineers of Valhalla (EoV) has been created to give HeroScape players a source of new terrain objects for map and scenario creation in the spirit of official HeroScape. The EoV works in two different areas - the Workshop and the Engineering Review Board. The Workshop (and the child Blueprint threads for each design) are where new ideas from EoV members are publicly debated and refined. The Engineering Review Board is where designs from the Workshop (or from any community member!) are assessed against a set of standard criteria to obtain the EoV Stamp of Approval.
The Workshop
The “Engineers of Valhalla Workshop Thread” is used to track active projects. Projects start as an “Idea”, are moved into “Design”, then “Public Feedback”, then “Editing and Playtesting”, “Revision”, then finally “Documentation”. More details on these steps is below. Each project is contained in it’s own “Blueprint of Valhalla” thread, where detailed discussion on each item can be documented, details can be hashed out, and playtesting results recorded.
Idea Stage: This is where we maintain a backlog of potential ideas and designs from members. We don’t want to overwork our volunteers, so we limit the number of projects that move out of this stage. Once a design passes “Documentation”, we vote on the next idea to tackle (using ranked choice, see here
https://ballotpedia.org/Ranked-choice_voting_(RCV)) and the design lead (the original creator by default) creates the "Blueprint of Valhalla" thread to kick things off.
Design: In this stage, the assigned design lead lays out their vision and takes the feedback of the group (the eventual voters on EoV approval!) to shape the design (either game mechanics or physically - this is terrain after all!).
Public Feedback: In this stage, we solicit feedback from the wider HeroScape community on the design - is it manufacturable, do people like the powers, are a destructible object’s life/attack/defense appropriate, etc. After sufficient time has passed or notice given, the design will be moved into the next stage by the Workshop crew.
Editing and Playtesting: This is an exciting phase! Maps will be created and games played (virtually, in person, solo, whatever!) with the design. As feedback is received, small changes to the design can also be playtested to inform the design space. Think of this stage as repeating a match with a custom figure but with more life, or without their special attack, or in a different army build. This empowers playtesters to find improvements without restarting the design process. The goal for EoV is at least 5 playtests for a given design.
Revision: This stage of development is the culmination of the playtesting and feedback efforts to finalize the design.
Documentation: This is a collaborative effort in the workshop to put together two key items. The first is a “Terrain Effects Description”. This is a way for the EoV to classify types of designs (see ERB section), and ensure that rules are well understood. The second item is a “Creator’s Guide” describing how to make the terrain object in question (whether it’s 3-D printed, or existing terrain repainted like the tundra glaciers and D&D rock outcrops). Once completed to Workshop crew satisfaction with a majority vote, we move to the next stage - the Engineering Review Board!
The Engineering Review Board
The ERB is where community designs and Blueprints from the Workshop are assessed to see if they are worthy of the EoV Stamp. An individual (either as a community member or as a design lead from the Workshop) may only have one design in review at a time.
Designs from the Workshop that pass "Documentation" automatically go into ERB review, and a majority vote from the ERB can be used to review any submission nominated by the community in the "Engineers of Valhalla - Engineering Review Board" thread. This thread will also contain the status of past and present reviews.
Each design will be evaluated based on its terrain type, outlined by Grishnakh and defined by the EoV below.
1. Terrain Tiles (or just Tiles)
These are the actual tiles that you build the battlefield out of (battlements, grass, rock, sand, water, ice, snow, road, lava, lava field, jungle, shadow, ladders, etc.). Note that these tiles may affect movement, dice rolled, LOS, and other aspects of the game. Submissions here must include a title, height (obstacle height, half hex tile, or full height tile) and a name and description for each associated rule (Ex. Desert Tile - Full-hex height - Shifting Sands, Moving onto a desert tile counts as two spaces.)
2. Objects
These are basically Non-Destructible Objects. They are placed onto the battlefield, but you cannot interact with them, nor destroy them. Some examples would be buildings, trees, large rocks, castle walls, bridges, glaciers, rock outcrops, etc. Submissions here must include a title and height.
3. Interactive Terrain Features (ITFs)
ITFs are terrain that is placed on the battlefield that you can use, or interact with. You can pick up these items and carry them, or use them as weapons. These items are such things as cars, street signs, computer consoles, train cars, equipment "glyphs", etc. Submissions here must include a title, height, hex count, and a name and description for each associated rule (Ex. Train Car - Height 8 - Two Hexes - All Aboard - When a small or medium hero moves adjacent to the Train Car, you may remove their figure from the battlefield and place it on this Army Card. - Conductor- When revealing an order marker on a hero whose figure is located on this Army Card, instead of moving normally you may move this Train Car up to 7 spaces in a straight line and place that figure adjacent to the Train Car.)
4. Destructible Objects (DOs)
These are objects placed on the map that can be destroyed through the course of play. We have two examples associated with the official game, the castle door and the wall section of the ruined warehouse. Submissions here must include a title, life, defense, and a name and description for each associated rule. Height may also be needed depending on the design to determine adjacency.
Approving Designs Through the ERB
A majority vote of ERB members is needed for approval. After approval, the EoV will translate the ruleset into a printable “Terrain Effects Card” with the EoV stamp so that any member of the community can print or share to easily teach the use of the new terrain design. Included on the card will be icons or language indicating that the design is suitable for competitive maps, casual play, or both (% or maybe we let the map designers determine this! Castle walls seldom used in competitive maps for balance reasons, but there are some).
The ERB will utilize the below criteria for each design. Each member will document their response to each question, and provide a final yes or no vote for inclusion.
Are the rules coherently written?
Do the rules interfere in a negative way with gameplay?
Is the design fun or offer interesting choices for all players in the game?
Is the design something you would want on the battlefield?
Does the design bring something new to the table?
Does it visually fit into official HeroScape (ie correct scale, feature quality, theme)?
Has the design been adequately playtested?
Are example maps with build instructions provided?
Is the design manufacturable? Note that all submissions to the ERB should have a .stl file accessible to the public. This ensures accessibility and improves the likelihood that the terrain aesthetically fits into HeroScape (no popsicle stick walls please). You may submit additional manufacturing instructions (papercraft, foam carving, etc) if desired.
Administration of the EoV
If a voting member of the EoV has not responded to direct requests for votes on the forums for a period of 1 month, the remaining members may vote to make their vote an abstain. IF a EoV member has been voted into abstainment on three consecutive design review, another vote may be taken to replace their position.