Skip to content

Document arena design considerations #188

@PeterJCLaw

Description

@PeterJCLaw

When constructing the arena at the event we often realise that we've designed the arena in a manner which is then hard to replicate. For SR2023 we spent more time than usual attempting to mitigate this by considering the physical construction early on, however at the event still found we'd missed things.

There are also plenty of ways to construct an arena which make sense, but which then make the running of matches harder.

Considerations of note:

  • be aware of compound tolerance errors, i.e: places where one measurement is relative to another one (both with tolerances); consider using a single, common, origin to mitigate this
  • token markings should prefer remaining visible once the tokens have been put on top of them, this ensures that marshals can see at a distance & from any side whether a given token has moved
  • ensure tokens are identifiable in the relevant lighting conditions, including during the post-match lower lighting. This may include choosing to colour or mark them to be easily identified

This documentation especially should focus on the things to consider, with explanations as to why, without prescribing solutions. This will offer greatest flexibility when designing the game.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ContentRelates to the content (i.e: SR documentation) rather than runbook build/serving platform

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions