retro.styleRoleSet
- .metadata176 B
- README.md2.3 KB
- roles.yaml2.0 KB
README.md
Retro arcade (role set)
For an old-school arcade or 8-bit and 16-bit style game: chunky, nearly even outlines on everything that matters, in a few loud console colours. The hero in lime green, allies in sky blue, enemies in hot magenta, the boss in a deep violet slab of a line, coins and power-ups in orange and pink, hazards in red, scenery flat and dark.
A set for a kind of game rather than a kind of look: it extends: look, so its line weights and inks are laid over the set the scene's look suits (toon game under a toon look, pencil sketch under a pencil look, and so on), and that set keeps deciding how much fill and paper reach each role and what the free value does. It also turns shading down on projectiles and scenery, for the flat colour of an old cartridge game. It works the same under every look, and every set of this kind fills the same roles, so a game switches from one to another with one call: StyleRoles.use("retro"). The look stays as it is. It pairs well with a pixel or dithered look (starterBlocks' ditherPalette, a posterize).
| Role | Line | Ink | Shading |
|---|---|---|---|
hero | 2.4 | #30d020 | look's |
partner | 2.2 | #20a8ff | look's |
friendly | 2 | #e8e8e8 | look's |
enemy | 2.4 | #e010c0 | look's |
elite | 2.8 | #a010e0 | look's |
boss | 3.6 | #5010a0 | look's |
pickup | 2 | #ff8c00 | look's |
rarePickup | 2.4 | #ff3a90 | look's |
usable | 2 | #00c0c0 | look's |
objective | 2.4 | #ffe000 | look's |
hazard | 2.4 | #ff2010 | look's |
projectile | 1.6 | #ffff40 | none |
prop | 1.2 | #202040 | two thirds |
ghost | 0.8 | #8080c0 | none, a third of the line |
distant | 0.6 | #303050 | two thirds |
asRendered and every role not written here come from the look's set. Variant lines: enemy #e010c0, hazard #ff2010, pickup #ff8c00, player #30d020.
Known limits
- At most eight distinct settings are drawn per scene; roles that resolve to the same setting share one (#24549, #22178).
- A per-object value cannot reach a geometry pass, so some per-object looks need passes of their own (#24549).
- Two engines on one account join as one player, so a two-player check needs two accounts or two machines (#14448).
The package README's Known limits lists the rest.