A2K PROJECT

......

Version 0.1by Caio Vallim MonazziA2K

🎯 Overview

"tagline"

Elevator Pitch

Elevator Pitch

Core Loop

Core Loop

1📋

GAME OVERVIEW

Title

✎ Sketch

🎮 Game Overview

This section establishes what the game is at a glance: a multiplayer FPS built in Unity with FishNet, inspired by old-school 90s arena shooters and focused on small, friend-based lobbies rather than strict competitive play. It summarizes the core concept, who the game is for, why it is distinctive, and the practical production targets (scope, platform, and engine).

Section	Purpose
High-Concept Pitch	One or two sentences that describe the game
Genre & Target Audience	What type of FPS it is and who it is for
Unique Selling Points	A short list of what makes this project stand out
Summary Paragraph	An "elevator pitch" version of the game overview
Production Goals	Realistic goals for scope, platform, and technology

✅ Section Checklist

High-Concept Pitch defined
Genre & Target Audience identified
Unique Selling Points listed
Summary Paragraph written
Production Goals finalized

📌 Moodboard

🎵Audio 1

1.1

High-Concept Pitch

High-Concept Pitch
A high-velocity multiplayer FPS built in Unity using FishNet, delivering crisp 90s-inspired arena combat with modern responsiveness. Players create or join small Steam-based lobbies, load into compact competitive spaces, and engage in pure, skill-driven firefights without grind, meta layering, or artificial progression barriers.

🎮 REDACTED Arena

A fast, readable arena shooter where small groups of friends drop into tight maps, trade pure skill shots, and reset in seconds.

📋 Overview

Built in Unity on top of FishNet, the game channels 90s arena pacing with modern responsiveness: low friction to start a match, high expression in aim, movement, and map knowledge. No grind walls, no forced meta loops—just focused multiplayer combat tuned for short, replayable sessions.

Property	Value
Engine	Unity 2022 LTS
Networking	FishNet
Genre	Multiplayer FPS
Mode	Arena / Deathmatch
Players	2-8 per lobby

🎯 Core Pillars

Core Fantasy

Jump into a lobby, lock into an arena, and rely purely on mechanics—aim, timing, positioning—to win fights with your group.

Social Focus

Built around friend lobbies instead of ranked ladders: quick to start, easy to rematch, tuned for small, repeatable sessions.

Tech Framing

Unity + FishNet as the backbone, with custom systems for weapons, movement, and UI designed to stay lean, modular, and extendable.

🕹️ Session Flow

┌─────────────────────────────────────────────────────────┐
│  1. HOST/JOIN  →  2. PICK ARENA  →  3. FIGHT  →  LOOP  │
└─────────────────────────────────────────────────────────┘

Host or Join — Steam lobby with friends
Pick Arena — Compact map and mode (DM / Team)
Play Fast — Quick rounds, swap map, repeat

⚔️ Design Intent

Philosophy: Old-school 90s arena feel with modern responsiveness.

Skill-first gunplay and movement
Minimal overhead between matches
No grind walls or forced meta loops
Ranked competitive mode (future)
Map editor (future)

🔧 Technical Architecture

Network Stack

┌──────────────────────────────────────┐
│            STEAM LOBBY               │
├──────────────────────────────────────┤
│           FISHNET SERVER             │
│  ┌────────────┐  ┌────────────────┐  │
│  │  Tick Mgr  │  │  Replication   │  │
│  └────────────┘  └────────────────┘  │
├──────────────────────────────────────┤
│  CLIENT  │  CLIENT  │  CLIENT  │ ... │
└──────────────────────────────────────┘

Core Systems

System	Purpose	Status
CentralizedTicker	Frame-perfect updates	✅
WeaponManager	Modular weapon handling	✅
InteractionSystem	World object interactions	✅
SurvivalStats	Health, stamina, etc.	✅
VolumetricFog	Atmosphere rendering	🔄

🎨 Visual Style

Color Palette

Name	Hex	Usage
Phosphor Green	`#33FF00`	Primary UI accent
Void Black	`#010A01`	Backgrounds
Hazard Yellow	`#F4F400`	Warnings, highlights
Dim Green	`#1A5C1A`	Secondary elements

Typography

Headers: Courier New, monospace
Body: System UI, sans-serif
Code: JetBrains Mono, monospace

📊 Player Stats Example

public class PlayerStats
{
    public float Health     { get; set; } = 100f;
    public float Armor      { get; set; } = 0f;
    public int   Kills      { get; set; } = 0;
    public int   Deaths     { get; set; } = 0;
    
    public float KDRatio => Deaths > 0 
        ? (float)Kills / Deaths 
        : Kills;
}

🗺️ Map Specifications

Arena Requirements

Requirement	Minimum	Target	Maximum
Size	50m²	200m²	500m²
Spawn Points	4	8	16
Weapon Pickups	2	5	10
Sightlines	2	4	6

Layout Principles

"Every position should have at least two escape routes and one power position should be contestable from three angles."

Verticality — At least 2 elevation levels
Flow — No dead ends, circular paths preferred
Cover — Mix of hard and soft cover
Pickups — Risk/reward positioning

📝 Glossary

Term	Definition
Tick	Single network update frame (64/sec)
Lobby	Pre-match gathering space via Steam
Arena	Playable combat map
DM	Deathmatch — free-for-all mode
TTK	Time-to-kill metric

🔗 Quick Links

Repository: github.com/yourname/arena-fps
Documentation: docs.yourgame.com
Discord: discord.gg/yourgame

✅ Milestone Checklist

Alpha 0.1

Basic movement controller
FishNet integration
Single weapon prototype
Test arena blockout

Alpha 0.2

Weapon switching
Hit registration
Kill/death tracking
Basic HUD

Beta 0.1

Steam lobby integration
3 playable arenas
5 weapon types
Audio pass

💬 Notes & Quotes

Design Note: Keep the barrier to fun as low as possible. A player should go from "I want to play" to "I'm shooting" in under 60 seconds.

Tech Note: FishNet's tick-based prediction handles most latency compensation, but weapon hitscan uses server-authoritative rollback.

📈 Appendix: Weapon Balance

Weapon	Damage	ROF	Range	Skill
Pistol	25	4/s	Med	⭐⭐
Shotgun	80	1/s	Short	⭐⭐
Rifle	35	8/s	Long	⭐⭐⭐
Rocket	100	0.8/s	Med	⭐⭐⭐⭐
Rail	150	0.5/s	Long	⭐⭐⭐⭐⭐

REDACTED Arena • Multiplayer FPS • Unity + FishNet

v0.1.0-alpha · Last Updated: December 2025

###

italic

italicboldbold and italic

1.2

Genre & Target Audience

A multiplayer first-person arena shooter for PC, built in Unity with FishNet, targeting players who enjoy 90s-inspired deathmatch pacing and small, friend-based lobbies instead of formal ranked queues.

Genre & Target Audience

Multiplayer FPSArena / DeathmatchPC / Steam

Genre Definition

Core genre: Multiplayer First-Person Shooter.
Subfocus: 90s-inspired arena and deathmatch play.
Session style: Short, round-based matches on compact maps.

Target Players

Players who like classic arena shooters and tight gunplay.
Small friend groups who want quick lobbies via Steam.
Players who prefer low-friction matches over long-term grind.

Primary MoodFast, focused, skill-forward.

Session LengthShort matches, easy to replay.

Social FramingFriends in a lobby, not strangers in ranked.

1.3

Unique Selling Points

Old-school 90s arena feel, modern Unity + FishNet tech, and a tight scope built around small Steam lobbies and pure, skill-driven matches without grind-heavy systems.

Unique Selling Points

🎯 90s Arena DNA

Movement, pacing, and combat flow take cues from classic arena shooters, emphasizing fast re-engagement and constant opportunities to fight.

👥 Friend-Centric Lobbies

Designed first for small Steam lobbies: easy invite flows, quick restarts, and minimal friction between “launch game” and “in a match with friends.”

🧩 Custom Tech Stack

Unity + FishNet as the backbone, with custom systems for weapons, movement, UI, and session flow tuned specifically for this project instead of generic plug-ins.

Skill-first gunplayLow meta overheadFocused, maintainable scope

1.4

Summary Paragraph (Elevator Pitch)

A Unity + FishNet multiplayer FPS that channels 90s arena shooters into modern, fast-loading Steam lobbies, giving small groups of friends short, repeatable deathmatch and team-based matches driven by pure gunplay and movement.

Summary Paragraph

This project is a multiplayer first-person shooter for PC that brings 90s arena energy into a modern Unity + FishNet stack, built around small Steam lobbies and fast match flow.

Players host or join a party, pick a compact arena, and jump into deathmatch or team-based modes where aim, movement, and map knowledge decide the outcome. The design deliberately keeps progression and meta light so the experience stays about the next fight, not the next unlock.

At a Glance

Multiplayer FPS with arena-style pacing.
Small, friend-focused Steam lobbies.
Short, repeatable matches instead of long grinds.
Custom-built systems on top of Unity + FishNet.

1.5

Production Goals

Ship a focused PC / Steam multiplayer FPS using Unity and FishNet, with a contained set of maps, modes, and weapons tuned for small friend lobbies rather than large-scale competitive infrastructure.

Production Goals

Scope

A contained roster of weapons, maps, and modes to keep balance and maintenance realistic.
Focus on core multiplayer loops (lobby → match → rematch) before expanding features.
Prioritize stability, readability, and responsiveness over sheer content volume.

Platform & Tech

Primary platform: PC (Windows) distributed via Steam.
Engine: Unity, with FishNet as the networking framework.
Networking model: host-client (party-based lobbies), with room to explore dedicated servers later.

Target ExperienceQuick-to-start matches with friends, low maintenance cost.

Anti-Cheat StanceBasic prevention and sanity checks; not a full esports solution.

Long-Term DirectionExtend systems once the core loop is solid and stable.

2⚙️

GAME LOOP

The game loop defines how players move from lobby to match and back again: forming a Steam party, selecting a map and mode, playing fast arena rounds, and deciding together whether to rematch, rotate maps, or switch modes, with optional secondary and tertiary systems layered carefully around that core.

🔄 Game Loop

Multiplayer FPS | Lobby → Match → Rematch | Short Sessions

The loop is built around fast, repeatable matches with minimal friction: form a lobby, play a round, make a quick group decision, and go again.

🎯 Core Flow

Host or join a Steam lobby with friends
Select map and mode (deathmatch or team-based)
Spawn into a compact arena and play the match
Match ends on score / time; results are shown
Return to lobby, rematch or rotate, repeat

🔗 Supporting Loops

Secondary loops refine combat rhythm, map control, and lobby flow between matches
Tertiary loops (stats / cosmetics) are optional and kept light to avoid grind
Progression is primarily skill-based, with any macro systems added cautiously

🏛️ Design Pillars

Pillar	Description
Low Friction	Shortest possible path from lobby to first engagement
High Repetition	Easy to chain multiple matches in one session
Group-Controlled	The party decides when to rematch, rotate maps, or stop

📊 Loop Structure

┌─────────────────────────────────────────────────────────┐
│                    PRIMARY LOOP                         │
│  ┌─────────┐   ┌─────────┐   ┌─────────┐   ┌────────┐  │
│  │  LOBBY  │ → │  MATCH  │ → │ RESULTS │ → │ DECIDE │  │
│  └─────────┘   └─────────┘   └─────────┘   └────────┘  │
│       ↑                                         │       │
│       └─────────────────────────────────────────┘       │
├─────────────────────────────────────────────────────────┤
│  SECONDARY: Combat rhythm, map control, loadout tweaks  │
├─────────────────────────────────────────────────────────┤
│  TERTIARY: Stats tracking, cosmetics (optional/light)   │
└─────────────────────────────────────────────────────────┘

✅ Implementation Checklist

Steam lobby integration
Map/mode selection UI
Match flow (spawn → play → end)
Results screen with stats
Rematch/rotate voting system
Session stats persistence

2.1

Core Loop

Players host or join a Steam lobby, select a map and mode, spawn into a compact arena, fight through fast rounds of deathmatch or team play, then return to the lobby to rematch or rotate maps.

Core Loop

Form Lobby – Host or join a party through Steam.
Select Map & Mode – Pick a compact arena and ruleset.
Spawn & Engage – Enter the match and fight.
Resolve Match – Score limit / timer ends, winner is declared.
Rematch or Rotate – Return to lobby, adjust settings, repeat.

Design Intent

Keep time between “launch game” and “first engagement” as short as possible.
Make it easy to chain multiple matches in a single session.
Prioritize clarity of objectives and score state at all times.

2.2

Secondary Loops

Secondary loops revolve around weapon choice, positioning, and map control during each match, plus simple lobby flow where the group can quickly change maps or modes between rounds.

Secondary Loops

⚔ Combat Decisions

Choosing when to push, hold, or rotate based on spawns and timers.
Adapting weapon choice to engagement ranges on each map.

📍 Map & Positioning

Controlling power positions, angles, and lines of sight.
Learning spawn patterns and safe routes over multiple matches.

🎛 Lobby Flow

Group decides whether to rematch, change map, or switch mode.
Keep transitions short to avoid breaking momentum.

Detailed mechanics for ammo, pickups, and advanced systems are still in development and will be defined as combat tuning evolves.

2.3

Tertiary Loops

Tertiary loops are minimal by design and may include simple stats, profiles, or cosmetics later, but the core experience does not depend on long-term progression.

Tertiary Loops

📊 Player Stats (Planned)

Optional tracking of basic metrics (matches played, kills, deaths, wins) for personal reference, not ranked matchmaking.

🎨 Cosmetics (Planned)

Potential for cosmetic variations (skins, badges) that do not affect gameplay.

🧪 Experiments

Additional long-term loops will only be added if they do not dilute the core “jump in and play a few matches with friends” experience.

All tertiary systems are explicitly secondary to the core combat loop and are subject to change or removal if they introduce unnecessary grind.

2.4

Progression Model

Progression is framed primarily at the micro and mid levels (life-to-life and match-to-match), with any macro progression kept light and optional to avoid grind dependency.

Progression Model

Micro – Moment to Moment

Spawn decisions, weapon use, and positioning within each life.
Short feedback loop: get into a fight, learn, respawn quickly.

Mid – Match to Match

Adapting to opponents and map over multiple rounds.
Group choices about map rotations and mode changes.

Macro – Session / Profile

Lightweight stats or cosmetics may be added later.
No mandatory unlock grind required to access core gameplay.

The progression model is intentionally minimal: skill growth and map knowledge are the main drivers of long-term improvement.

3🌍

WORLD & FICTION

The world and fiction serve as a lightweight narrative framework that supports the game’s fast-paced multiplayer focus. Rather than a sprawling universe, the setting provides cohesive atmosphere, consistent visual identity, and thematic grounding across arenas, weapons, and player presentation. Lore exists to reinforce tone and environment design, ensuring each map feels intentional without imposing mandatory storytelling on players whose primary goal is quick, replayable matches.

🌍 World & Fiction

Minimal Lore | Atmosphere-Driven | Multiplayer-Centric

The game's fiction is intentionally lightweight—supporting atmosphere, environment tone, and visual cohesion while keeping the gameplay focused on arena combat, mobility, and moment-to-moment skill expression.

Each map represents a distinct pocket of this world: industrial complexes, abandoned testing grounds, retro-futuristic facilities, or stylized combat arenas built to emphasize flow and clarity. The narrative avoids heavy lore drops, instead offering subtle worldbuilding through environmental cues.

🎯 Design Purpose

Support visual identity and tone across all arenas
Enable diverse but cohesive environments for competitive play
Reinforce mood (retro-futuristic, industrial, stylized, etc.)
Avoid intrusive narrative that slows the gameplay loop

⚙️ Functional Role

Provide a coherent aesthetic theme without overwriting gameplay
Guide level design via world rules, materials, and atmosphere
Offer subtle lore touches through map details and props
Remain flexible to support future modes or expansions

🏛️ World Design Pillars

Pillar	Philosophy
Atmospheric	Maps communicate tone through visuals, not cutscenes
Lightweight	Lore enhances the experience without demanding attention
Gameplay-First	Fiction supports readability and flow above all else

🗺️ Environment Types

Type	Description	Mood
Industrial	Factories, warehouses, machinery	Gritty, utilitarian
Testing Grounds	Abandoned labs, research facilities	Mysterious, clinical
Retro-Futuristic	80s/90s sci-fi aesthetic	Nostalgic, neon-lit
Combat Arenas	Purpose-built battle zones	Clean, competitive

🎨 Visual Language

WORLD TONE SPECTRUM
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  GRITTY ◄─────────────────────────────────► STYLIZED
    │                                            │
    ▼                                            ▼
  Industrial                               Combat Arena
  Abandoned                                Retro-Future

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  NARRATIVE PRESENCE: ░░░░░░░░░░░░░░░░░░░░ (Minimal)
  ATMOSPHERE FOCUS:   ████████████████████ (Maximum)
  GAMEPLAY CLARITY:   ████████████████████ (Maximum)

✅ World Design Checklist

Core visual identity defined
Environment type categories established
Lore approach documented (minimal/environmental)
Material palette per environment type
Prop library guidelines
Lighting mood guides per map type
Audio atmosphere direction

"Show, don't tell. Let the rust on the walls and the flicker of neon speak louder than any codex entry."

3.1

Setting & Lore Summary

The setting provides a flexible, lightly-defined world where competitive arenas exist as isolated environments built for testing, training, or conflict simulations. Lore remains optional, delivered through environmental cues rather than direct storytelling, allowing players to focus on fast multiplayer action while still enjoying a cohesive atmosphere across maps.

Setting & Lore Summary

Modular WorldEnvironmental LoreGameplay-Driven

The game's environments exist as isolated arenas, each built with a purpose—testing grounds, industrial platforms, abandoned facilities, or stylized combat zones—while staying grounded in a consistent atmospheric tone.

Instead of linear storytelling, lore is conveyed through subtle world details: signage, architecture, lighting, props, and environmental storytelling that enhance immersion without interrupting the fast-paced loop.

🌐 World Concept

A connected but fragmented environment where arenas are distributed across various industrial, retro-futuristic, or experimental zones. Each map contributes a piece of the overarching mood.

🏭 Environmental Identity

Compact arenas built with purpose: firing lanes, vertical routes, combat pockets, silhouette clarity, and thematic props that suggest function and history without explicit exposition.

🧩 Narrative Delivery

Lore is lightweight and optional. Players absorb world hints naturally through the environment, not through dialogue, cutscenes, or long text.

AtmosphericTone delivered visually, not verbally.

ModularMaps fit together thematically, not narratively.

Non-IntrusiveLore never slows matchmaking or pacing.

3.2

World Rules

World rules define the logical boundaries that shape level design, tone, and environmental storytelling. Physical rules ensure arenas remain readable, fair, and consistent, while narrative rules provide light thematic structure without constraining gameplay or requiring deep lore commitment.

World Rules (Physical & Narrative)

Physical RulesNarrative LogicConsistency

These rules ensure all environments share coherent structure and tone, keeping maps believable while supporting clean competitive play.

🌐 Physical Rules

Maps obey logical architectural structure (supports, platforms, access points).
Silhouette clarity is preserved through lighting and material contrast.
Interactive surfaces remain consistent across all arenas.
Traversal routes follow predictable readability: ramps, stairs, ladders, jump paths.
No map introduces exceptions that break player expectations.

📘 Narrative Rules

Each arena exists for a purpose (testing facility, industrial zone, abandoned site).
No explicit or mandatory story progression is required.
Environmental storytelling hints at function and history.
Props and signage reinforce setting identity without being intrusive.
The narrative never interrupts or slows the gameplay loop.

🎨 Aesthetic Consistency

Lighting, materials, and thematic cues maintain world cohesion across diverse arenas, ensuring maps feel different but never disconnected from the overall tone.

PredictablePlayers always know what surfaces and spaces mean.

GroundedEven stylized arenas feel physically plausible.

Non-IntrusiveNarrative adds to atmosphere but never slows combat.

3.3

Factions / Characters

The game does not rely on traditional narrative factions or deep character lore. Instead, it uses lightweight player identifiers and world entities that support visual clarity and multiplayer readability without affecting gameplay balance.

Factions, Characters & Entities

Minimal LoreReadabilityMultiplayer Focus

Character and faction design are deliberately minimal to preserve readability, reduce visual noise, and maintain competitive balance.

👤 Player Avatars

Simple, silhouette-friendly character rigs.
Readable from all distances and angles.
Cosmetic variations may be added later.
No gameplay-affecting character differences.

⚑ Teams / Factions

Teams are functional (e.g., Red / Blue) rather than narrative factions.
Color coding improves clarity in high-velocity firefights.
No lore impact or asymmetrical gameplay differences.

🗄 World Entities

Props and environmental objects support world tone.
Entities provide map context (machinery, terminals, platforms, signage).
Non-interactive by default to preserve pacing and clarity.

FairNothing grants gameplay advantage.

ReadableClear silhouettes at all distances.

ExpandableCosmetics possible without altering balance.

3.4

Narrative Structure

The game does not use a traditional narrative structure. Instead, narrative beats are environmental, subtle, and optional, existing only to enrich atmosphere across maps without imposing progression.

Narrative Structure

Non-LinearAtmosphericMinimal Story

There is no act-based structure or campaign progression. Narrative exists only through map design, environmental hints, and tone.

🧱 No Acts or Chapters

Matches do not follow scripted progression. Story elements are ambient and optional.

🔎 Environmental Beats

Subtle details—markings, architecture, abandoned tech—suggest history without overt narrative.

📦 Flexible Framework

Allows future modes or environments to expand tone without continuity constraints.

3.5

Tone, Themes, Aesthetic Direction

The tone blends retro-futuristic industrial design with clean competitive readability. Themes emphasize isolation, abandoned structures, and synthetic environments, while the aesthetic direction focuses on clarity, contrast, and a cohesive gunmetal visual identity.

Tone, Themes & Aesthetic Direction

GunmetalRetro-FuturisticCompetitive Readability

The game’s atmosphere blends retro-futuristic industrial spaces with bold neon cues and sharp environmental contrast, delivering arenas that feel functional, hostile, and optimized for competitive play.

🎨 Visual Tone

Gunmetal materials with neon accents.
Industrial and retro-tech textures.
Clean silhouettes for competitive clarity.
Cold lighting contrasted with vibrant color markers.

🧭 Themes

Abandoned testing grounds.
Retro-futuristic industrial labs and arenas.
Synthetic training environments.
Isolation, precision, and hostile architecture.

⚡ Aesthetic Direction

Prioritizes readability: clear depth, contrasting materials, controlled noise levels, and functional environmental props that reinforce flow.

4🎮

PLAYER & CONTROLS

The Player & Controls section defines the core identity of the player, their input scheme, movement capabilities, combat options, and progression systems. The focus is on responsive, readable, Quake-inspired controls with modern UX clarity and zero friction. Player abilities emphasize mobility, precision, and tactical decision-making rather than grind-based progression.

🎮 Player & Controls

FPS | Input System | Movement Core

Defines who the player is, how they control their character, and how their abilities shape the overall gameplay experience. Movement and responsiveness are inspired by 90s arena shooters but refined with modern sensibilities and clean UX feedback.

Principle	Description
Fast	Low-latency controls, instant responsiveness
Skill-Based	Movement, aim, and timing define success
Readable	Inputs, abilities, and states clearly communicated

🕹️ Input Philosophy

RESPONSE TIME TARGETS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  Input → Action:     < 1 frame (instant)
  State Change:       Immediate visual feedback
  Network Prediction: Client-authoritative feel

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

⚡ Control Pillars

Precision — Every input maps 1:1 to character action
Consistency — Same input always produces same result
Feedback — Audio/visual confirmation for all actions
Accessibility — Fully rebindable, sensitivity options

🔧 Technical Specs

Parameter	Value	Notes
Tick Rate	128 Hz	Server simulation
Input Polling	Every frame	No input buffering
Mouse Input	Raw	No acceleration/smoothing
Dead Zone	Configurable	Controller support

✅ Implementation Status

Core movement controller
Input binding system
Mouse look (raw input)
Controller support
Rebinding UI
Sensitivity curves
Accessibility options

4.1

Player Role & Identity

The player is a clean, non-lore-heavy combatant designed for maximum visual readability and competitive clarity. Their role is purely skill-driven: navigate arenas, engage opponents, and outplay them using movement and aim. No perks, classes, or narrative roles interfere with competitive balance.

Player Role & Identity

Neutral AvatarHigh ReadabilityCompetitive Fairness

The player embodies a neutral, non-narrative character whose identity supports gameplay function rather than story. Visual clarity, silhouette recognition, and fairness drive the design.

👤 Neutral Identity

No lore-defined personality or backstory.
Purely functional and competitive-facing.
Allows players to project their own identity.

🎯 Functional Purpose

Participate in deathmatch or team-based modes.
Master mobility and spatial awareness.
Engage in high-speed, aim-focused combat.

🎨 Readability-First Visuals

Silhouettes unmistakable at all distances.
Team colors highly differentiated.
Minimal visual clutter for maximum clarity.

4.2

Input Scheme

Inputs are streamlined using the Unity Input System, covering all essential FPS actions without duplication or redundancy. Movement is smooth and precise, designed to emulate Quake-style responsiveness while remaining accessible.

Input Scheme

Unity Input SystemMovementActions

🏃 Core Movement

Move (WASD / Left Stick)
Look (Mouse / Right Stick)
Jump
Sprint Modifier
Crouch / Slide
Slow Modifier (Precision)

🔫 Combat Inputs

Primary Fire
Secondary Fire
Reload
Switch Weapon
Melee
Throw Grenade / Utility

🎮 Interactions

Use / Interact
Open Inventory / Loadout
Pause / Menu
Scoreboard

4.3

Abilities

Abilities emphasize mobility, combat utility, and fast-paced traversal. Movement is intentionally expressive with mechanics inspired by classic arena shooters such as strafe-jumping, slide momentum, air control, and precise directional mastery.

Abilities

MobilityCombat SkillsTools

🏃 Movement Abilities

Sprint & sprint momentum
Air control (Quake-style)
Slide mechanics
Wall-jump or optional parkour extensions
Crouch-jump for height optimization

🎯 Combat Abilities

Hip-fire and ADS modes for some weapons
Quick melee strike
Grenade throws with variable strength
Weapon quick-swap mastery

🧰 Tactical Tools

Grenades (frag, smoke, flash depending on mode)
Optional deployables in future updates
No pay-to-win or progression-locked tools

4.4

Player Progression

Progression is intentionally minimal. No stat boosts, perks, or grind-based advantages. Cosmetic unlocks may exist but never impact gameplay. Skill expression is the only form of advancement.

Player Progression

No Power CreepCosmetics OnlySkill-Based Progression

🛡 No Gameplay Stats

No HP upgrades
No damage modifiers
No perk trees

✨ Cosmetic Unlocks

Player skins (non-silhouette changing)
Weapon skins
Banners / Emblems

🎯 True Progression = Skill

Mastery of movement, aiming, spatial control, and decision-making is the only path to improvement.

5🔧

SYSTEMS DESIGN

Systems Design defines the core rules and mechanical frameworks that govern combat, interaction, inventory,
economy, progression, and survival elements. These systems support the fast-paced arena shooter identity while
remaining modular, scalable, and clean for development within Unity + FishNet.

⚙️ Systems Design

Core Systems | Combat | Interaction | Inventory

The backbone of all gameplay mechanics. Every system is crafted to reinforce skill expression, readability, and tight multiplayer synchronization. Modular subsystems ensure long-term expandability without bloating the core competitive experience.

Principle	Description
Modular	Systems operate independently and scale cleanly
Network-Safe	Optimized for FishNet replication and authoritative logic
Competitive	Focused on fairness, clarity, and consistency

🏗️ System Architecture

┌─────────────────────────────────────────────────────────────┐
│                    GAME SYSTEMS LAYER                       │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│   ┌─────────────┐  ┌─────────────┐  ┌─────────────┐        │
│   │   COMBAT    │  │ INTERACTION │  │  INVENTORY  │        │
│   │   SYSTEM    │  │   SYSTEM    │  │   SYSTEM    │        │
│   └──────┬──────┘  └──────┬──────┘  └──────┬──────┘        │
│          │                │                │                │
│          ▼                ▼                ▼                │
│   ┌─────────────────────────────────────────────────┐      │
│   │              SHARED SERVICES LAYER              │      │
│   │  • Object Pooling    • Event Bus                │      │
│   │  • State Machine     • Network Sync             │      │
│   └─────────────────────────────────────────────────┘      │
│                           │                                 │
│                           ▼                                 │
│   ┌─────────────────────────────────────────────────┐      │
│   │              FISHNET NETWORK LAYER              │      │
│   │  • Server Authority  • Client Prediction        │      │
│   │  • State Replication • RPC Channels             │      │
│   └─────────────────────────────────────────────────┘      │
│                                                             │
└─────────────────────────────────────────────────────────────┘

📦 Core Subsystems

System	Responsibility	Network Authority
Combat	Weapons, damage, hit detection	Server
Interaction	Pickups, doors, triggers	Server
Inventory	Loadout, ammo, equipment	Server + Client prediction
Movement	Physics, collision, abilities	Client predicted, server verified
Audio	Spatial sound, events	Client-side
UI/HUD	Feedback, state display	Client-side

🔄 Data Flow

INPUT → PREDICTION → SERVER VERIFY → RECONCILE → RENDER

  [Client]           [Server]           [Client]
     │                  │                  │
     │  Input Packet    │                  │
     ├─────────────────►│                  │
     │                  │                  │
     │  Predict Local   │  Simulate Auth   │
     │      ▼           │       ▼          │
     │  [Local State]   │  [True State]    │
     │                  │                  │
     │                  │  State Snapshot  │
     │◄─────────────────┤                  │
     │                  │                  │
     │  Reconcile       │                  │
     │      ▼           │                  │
     │  [Corrected]─────┼─────────────────►│ Render
     │                  │                  │

🎯 Design Guidelines

Single Responsibility — Each system owns one domain
Event-Driven — Loose coupling via message bus
Deterministic — Same input = same output (for rollback)
Observable — All state changes emit events for UI/audio

✅ Implementation Status

Combat system foundation
Weapon state machine
Interaction raycast system
Basic inventory (weapons + ammo)
Equipment slots
Pickup spawner system
Match state manager
Kill feed / event log

5.1

Combat System

The combat system is fast, responsive, and skill-driven. Weapons, damage, recoil, hit feedback, and AI combat logic (if used in PvE modes) are all tuned for competitive clarity inspired by arena shooters.

Combat System

WeaponsDamage ModelAI BehaviorsNetwork-Synced

🔫 Weapons

Hitscan primaries (rifles, SMGs, snipers)
Projectile utilities (grenades, rockets — optional)
Reload timings balanced around aggression
No random spread; recoil is pattern-based

💥 Damage Model

Body multipliers: head, torso, limbs
No RNG damage spread
Clean TTK tuning for readability
Optional armor for team modes

🤖 AI Behaviors

Strafe, retreat, and push behaviors
Line-of-sight and pathfinding logic
Adaptive aggro based on player distance

🎯 Hit Reactions

Clear hit markers
Directional damage indicators
Network-synced impact effects

🧱 Cover & Stealth

Line-of-sight based detection
Light stealth options (sound cues, footsteps)
Optional crouch-peeking mechanics

5.2

Interaction System

A clean and readable interaction system that lets players pick up items, activate objects, and trigger gameplay events with consistent UI prompts. All interactions follow a predictable rule set ensuring clarity in multiplayer.

Interaction System

InteractionPromptsFeedback

🧩 Interactable Types

Pickups (weapons, ammo, items)
Switches / buttons
Doors / gates
Objective triggers

📏 Interaction Rules

Raycast-based
Clear distance thresholds
Network authority ensures fairness

💬 Feedback

Hover prompts
Icon + text indicators
Color-coded context cues

5.3

Inventory / Loadout

A lightweight inventory emphasizing fast weapon switching and clean loadout selection. No RPG weight systems, no grind; minimal friction and maximum clarity.

Inventory & Loadout

InventoryWeapons

📦 Item Types

Weapons (primary/secondary/melee)
Ammunition
Grenades / utilities

⚖ Slot Rules

One primary
One secondary
Melee
Up to 2 utilities

🛠 Crafting

Not applicable (competitive pacing).

5.4

Economy Systems

Economy is mode-dependent and lightweight. Some modes may use round-based credits or pickups, but no persistent meta-economies exist. The design avoids grind and pay-to-win structures entirely.

Economy Systems

Economy

🪙 Currencies

Round credits (if mode uses buy phase)
No premium currencies
No persistent soft progression

🔁 Sinks & Rewards

Buying weapons between rounds
Scoring bonuses for objectives

5.5

Progression Systems

Progression is cosmetic-only. No stat increases, skill trees, or gameplay advantages exist. Optional XP may unlock visual cosmetics.

Progression Systems

Cosmetic-Only

✨ XP

Optional system for unlocking cosmetics.

🌳 Skill Trees

Not applicable (no gameplay-altering perks).

📜 Quest Structure

Not applicable (arena-focused gameplay).

5.6

Survival / Needs

Survival systems are optional and only used in specific game modes. These include stamina, limited oxygen, or toxic-mask gameplay depending on the scenario.

Survival & Needs

Survival

⚡ Stamina

Affects sprinting and sliding
Regenerates out of combat

☣ Toxicity

Gas mask required for certain areas
Filter health depletes over time

🌡 Temperature / Environment

Mode-specific only.

6🗺️

LEVEL DESIGN

Level Design defines the structure, flow, pacing, and spatial readability of all combat arenas. Maps follow a
competitive 90s–inspired silhouette: compact, learnable, movement-friendly, and visually distinct. Each arena
supports fast re-engagement, clear lines of sight, strong landmarking, and consistent multiplayer fairness.

🗺️ Level Design

Arenas | Flow | Readability

Arena map design focuses on fast combat loops, recognizable callouts, clean traversal routes, and tight optimization for networked firefights. Every level supports both 1v1/2v2 duels and larger DM/Team modes.

Principle	Description
Readable	Clear silhouettes and predictable sightlines
Fast	Short routes and rapid re-engagement timings
Competitive	Fair spawns and balanced control points

🏟️ Arena Philosophy

MAP SIZE SPECTRUM
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  SMALL (1v1/2v2)          MEDIUM (4-6)           LARGE (8+)
       │                        │                      │
       ▼                        ▼                      ▼
  ┌─────────┐             ┌──────────┐           ┌─────────┐
  │  DUEL   │             │   DM     │           │  TEAM   │
  │  PIT    │             │  ARENA   │           │  WAR    │
  └─────────┘             └──────────┘           └─────────┘
  
  Spawn-to-Fight:  3-5 sec          5-8 sec          8-12 sec
  Control Points:     1                2-3              3-5
  Verticality:       Low            Medium             High

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📐 Layout Guidelines

Element	Guideline	Reason
Spawn Points	Min 3 per team, LOS-blocked	Prevent spawn camping
Sightlines	Max 2-3 long angles per map	Promote movement over camping
Cover	Every 10-15 units of open space	Allow tactical repositioning
Height Layers	2-3 vertical tiers	Reward map control
Chokepoints	1-2 major, flanks available	Create risk/reward decisions

🎯 Flow Patterns

STANDARD 3-LANE STRUCTURE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

           ┌─────────────── HIGH LANE ───────────────┐
           │            (Exposed, Fast)              │
           │                                         │
  ┌────┐   │   ┌─────┐              ┌─────┐        │   ┌────┐
  │ A  │◄──┼──►│ MID │◄────────────►│ MID │◄───────┼──►│ B  │
  │SPAWN│   │   │     │   CONTROL    │     │        │   │SPAWN│
  └────┘   │   └─────┘    POINT      └─────┘        │   └────┘
           │                 ★                       │
           │                                         │
           └─────────────── LOW LANE ────────────────┘
                        (Covered, Slow)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎨 Visual Readability

Element	Treatment	Purpose
Player Silhouettes	High contrast vs environment	Instant target recognition
Team Colors	Saturated, distinct hues	No friendly fire confusion
Pickups	Glow + particle + audio	Visible at distance
Hazards	Warning colors (orange/red)	Avoid accidental deaths
Callout Zones	Unique landmarks	Voice comm clarity

📊 Map Metrics Template

Metric	Target	Measurement
Avg Engagement Time	15-30 sec	Time between fights
Respawn-to-Fight	5-8 sec	Spawn → first enemy LOS
Map Traversal	12-20 sec	Corner to corner
Pickup Cycle	30-45 sec	Major item respawn
Verticality Ratio	30-40%	Elevated combat area

✅ Level Design Checklist

3-lane flow structure defined
Spawn point placement rules
Sightline guidelines documented
Blockout template created
Pickup placement guide
Callout naming convention
Performance budget (tris/drawcalls)
Lighting mood per zone type

6.1

Structure & Flow

Maps follow a three-lane inspired structure with clear choke points, flank paths, and vertical variation. Flow is designed to keep players rotating, re-engaging, and contesting high-value positions without stagnation.

Level Structure & Flow

FlowLanesVerticality

🎯 Core Structure

Three-lane silhouette
Short rotation paths
Defined choke points

🔄 Flow Model

Continuous combat loops
Minimal downtime after respawn
Predictable player traffic

🧗 Verticality

Light elevation shifts
Jump pads or risers when appropriate
High-ground vantage balanced by counter-flanks

6.2

Landmarks

Each map features 3–5 clear landmarks used for callouts and orientation. These POIs support spatial memory, team coordination, and rapid navigation.

Landmarks & Points of Interest

LandmarksCallouts

📍 Anchor Landmarks

Main Arena Center
High-Ground Platform
Connector Tunnel

🗺 Functional POIs

Power Positions
Weapon Spawns
Health/Ammo Pickup Areas (if used)

6.3

Encounter Design

Encounters are shaped by lane geometry, cover density, verticality, and combat sightlines. Engagements are short, high-lethality exchanges that reward accuracy and positioning.

Encounter Design

EncountersCoverSightlines

🔫 Engagement Zones

Close-quarters corners
Mid-range corridors
Long-range lanes

🧱 Cover Layout

Predictable cover spacing
No camping-prone dead-ends
Cover supports strafing and peeking

📏 Sightlines

Clear mid-lane visibility
High-ground angle presence
Counter-play routes available

6.4

Environmental Storytelling

Environmental storytelling is subtle and functional. Small visual cues reinforce location identity without distracting from competitive clarity.

Environmental Storytelling

ArtAtmosphere

🎨 Visual Identity

Subtle props to indicate map purpose
Color-coded sectors for navigation
Ambient storytelling elements

🔎 Clarity First

No clutter affecting visibility
Avoids misleading pathing
Landmarks inform gameplay

6.5

Puzzles / Interactables

Only used in optional modes. Puzzles are lightweight, readable, and interaction-based.

Puzzles & Interactables

Interaction

Optional feature. If included, puzzles rely on switches, timed triggers, or objective-based interactions.

6.6

Traversal Layout

Traversal is fast and readable. Movement routes enable quick rotation, strafing, and controlled vertical shifts.

Traversal Layout

TraversalMovement

🏃 Movement Paths

Flanking routes
Tight cornering options
Fast mid-lane re-entry

🧗 Vertical Features

Light height variation
Jump pads or lifts (if desired)
Balanced high-ground positions

7👤

ENEMIES / NPCs

Enemies and NPCs are optional depending on the chosen game mode. While core arena FPS gameplay does not require AI combatants, the system supports lightweight bots, ambient NPC roles for hub areas, and simple AI opponents for testing or offline play. Focus remains on clarity, predictable behavior, and fairness.

🤖 Enemies & NPCs

AI | NPC Systems | Optional Feature

AI characters, if included, serve as supportive elements for offline play, training modes, or contextual world NPCs. They are intentionally limited in complexity to maintain stable networking and predictable encounter patterns.

Principle	Description
Predictable	Consistent and learnable behavior
Lightweight	Optimized for multiplayer environments
Optional	Only used in specific modes or hubs

🎯 Use Cases

NPC DEPLOYMENT CONTEXTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ┌──────────────┐    ┌──────────────┐    ┌──────────────┐
  │   TRAINING   │    │   OFFLINE    │    │    WORLD     │
  │     MODE     │    │    PLAY      │    │    HUBS      │
  └──────┬───────┘    └──────┬───────┘    └──────┬───────┘
         │                   │                   │
         ▼                   ▼                   ▼
    Target Bots         Bot Matches         Ambient NPCs
    Aim Trainers        Practice Mode       Shop Vendors
    Tutorial Guides     Warmup Arena        Quest Givers*

                    * Future consideration

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🧠 AI Architecture

Type	Behavior	Complexity	Network Cost
Target Dummy	Stationary, no AI	None	Minimal
Patrol Bot	Waypoint movement	Low	Low
Combat Bot	Seek + Shoot	Medium	Medium
Ambient NPC	Idle + Interact	Low	Minimal

🔄 Behavior State Machine

┌─────────────────────────────────────────────────────────┐
│                   BOT STATE MACHINE                     │
├─────────────────────────────────────────────────────────┤
│                                                         │
│         ┌──────────┐                                    │
│    ┌───►│   IDLE   │◄───┐                              │
│    │    └────┬─────┘    │                              │
│    │         │          │                              │
│    │    Enemy Spotted   │ Target Lost                  │
│    │         ▼          │                              │
│    │    ┌──────────┐    │                              │
│    │    │  CHASE   │────┘                              │
│    │    └────┬─────┘                                   │
│    │         │                                         │
│    │    In Range                                       │
│    │         ▼                                         │
│    │    ┌──────────┐                                   │
│    │    │  ATTACK  │                                   │
│    │    └────┬─────┘                                   │
│    │         │                                         │
│    │    Low Health                                     │
│    │         ▼                                         │
│    │    ┌──────────┐                                   │
│    └────│ RETREAT  │                                   │
│         └──────────┘                                   │
│                                                         │
└─────────────────────────────────────────────────────────┘

⚡ Performance Budget

Constraint	Limit	Rationale
Max Active Bots	8 per match	Network bandwidth
AI Tick Rate	10 Hz	CPU optimization
Pathfinding	Simple navmesh	Memory footprint
Perception	Raycast only	No complex sensors
State Sync	Position + State	Minimal replication

📋 Bot Difficulty Tiers

Tier	Accuracy	Reaction	Movement	Use Case
Easy	25-40%	500ms+	Predictable	New players
Medium	50-65%	300-500ms	Basic strafing	Warmup
Hard	75-85%	150-300ms	Advanced movement	Practice
Nightmare	90%+	<150ms	Near-optimal	Challenge

✅ Implementation Status

Target dummy (stationary)
Basic waypoint patrol
Combat bot (seek + shoot)
Difficulty scaling system
Bot backfill for matches
Training mode integration
Ambient NPC framework

7.1

Enemy Types

Enemy types are minimal and functional: basic bots or training dummies used for target practice or experimental modes.

Enemy Types

AI BotsTraining

🤖 Basic Combat Bot

Simple movement routes
Basic aim & firing routines
Predictable behaviors for practice

🎯 Training Dummy

Static or moving targets
No combat logic
Used for weapon testing

7.2

Behavior Profiles

AI behavior is intentionally simple: patrolling, chasing, attacking, and disengaging. No advanced tactical behavior is used.

Behavior Profiles

AI Logic

🚶 Patrol

Moves along predetermined routes.

🎯 Engage

Attacks player when in sight.

🔁 Reset

Returns to idle when target is lost.

7.3

Combat Phases / Patterns

Combat behavior consists of simple aggressive loops: spot player → aim → fire → reposition → repeat.

Combat Phases & Patterns

Combat

Detection → Spot player.
Aiming → Delay or accuracy check.
Firing → Simple burst patterns.
Reposition → Short strafe or fallback.

7.4

AI Sensory Systems

AI sensory logic uses simple raycasts for sight checks and distance thresholds for awareness.

AI Sensory Systems

Senses

Raycast vision cone
Distance-based hearing
Basic threat detection

7.5

Dialogue Behavior Rules

NPC dialogue, if any, is minimal—restricted to training, hub areas, or simple voice lines.

Dialogue Behavior Rules

Optional feature for flavor only. No branching choices or narrative progression.

7.6

NPC Roles

Only applies if a hub or meta-progression mode is added. NPCs may serve basic vendor or utility functions.

NPC Roles

Training Instructor (hub)
Vendor (cosmetics)
Match Selector NPC

8🖥️

UI/UX

UI/UX emphasizes clarity, fast navigation, minimal friction, and competitive readability. Every interface supports quick decision-making and consistent feedback during high-speed combat.

🖥️ UI / UX

UI | UX | Feedback

A clean interface designed to be readable at a glance, responsive under stress, and fully supportive of arena shooter pacing. HUD elements are compact, high-contrast, and anchored to consistent visual rules.

Principle	Description
Readable	Clear HUD with no clutter
Responsive	Instant feedback during combat
Fast Navigation	Menus load instantly with predictable structure

📐 HUD Layout

┌─────────────────────────────────────────────────────────────┐
│  ┌─────────┐                              ┌─────────────┐   │
│  │ HEALTH  │                              │  KILLFEED   │   │
│  │ ██████░░│                              │  Player1 ► X│   │
│  │ ARMOR   │                              │  You ► Bot  │   │
│  │ ████░░░░│                              └─────────────┘   │
│  └─────────┘                                                │
│                                                             │
│                         ┌───┐                               │
│                         │ + │  CROSSHAIR                    │
│                         └───┘                               │
│                                                             │
│                    ┌─────────────┐                          │
│                    │ HIT MARKER  │                          │
│                    └─────────────┘                          │
│                                                             │
│  ┌─────────┐                              ┌─────────────┐   │
│  │ WEAPON  │                              │    AMMO     │   │
│  │ ══════  │                              │   24 / 120  │   │
│  │ Shotgun │                              │   ████████  │   │
│  └─────────┘                              └─────────────┘   │
│                    ┌─────────────┐                          │
│                    │  TIMER 4:32 │                          │
│                    └─────────────┘                          │
└─────────────────────────────────────────────────────────────┘

🎯 HUD Elements

Element	Position	Priority	Update Rate
Health/Armor	Bottom-left	Critical	Real-time
Ammo	Bottom-right	Critical	On change
Crosshair	Center	Critical	Every frame
Weapon	Bottom-left	High	On switch
Kill Feed	Top-right	Medium	On event
Timer/Score	Top-center	Medium	Per second
Minimap	Corner (optional)	Low	10 Hz

⚡ Feedback Systems

FEEDBACK HIERARCHY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  CRITICAL (Immediate)          INFORMATIONAL (Queued)
  ────────────────────          ──────────────────────
  • Hit confirmation            • Kill notifications
  • Damage taken                • Pickup messages
  • Low health warning          • Objective updates
  • Death                       • Score changes

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  FEEDBACK CHANNELS:
  
  ┌──────────┐  ┌──────────┐  ┌──────────┐  ┌──────────┐
  │  VISUAL  │  │  AUDIO   │  │ HAPTIC*  │  │CROSSHAIR │
  └────┬─────┘  └────┬─────┘  └────┬─────┘  └────┬─────┘
       │             │             │             │
       ▼             ▼             ▼             ▼
   Hit marker    Impact SFX    Controller    Color/Size
   Screen flash  Confirm ping  rumble       expansion
   Damage nums   Voice cues                 Hit tick

                              * Controller only

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🗂️ Menu Structure

MAIN MENU
    │
    ├── PLAY
    │     ├── Quick Match
    │     ├── Create Lobby
    │     ├── Join Lobby
    │     └── Training
    │
    ├── ARMORY
    │     ├── Loadouts
    │     ├── Weapons
    │     └── Cosmetics
    │
    ├── PROFILE
    │     ├── Stats
    │     ├── Match History
    │     └── Achievements
    │
    ├── SETTINGS
    │     ├── Controls
    │     ├── Video
    │     ├── Audio
    │     └── Accessibility
    │
    └── QUIT

🎨 Visual Style Guide

Property	Value	Notes
Primary Font	Sans-serif, bold	Readable at distance
Font Size (HUD)	18-24px	Scales with resolution
Font Size (Menu)	16-20px	Comfortable reading
Contrast Ratio	7:1 minimum	WCAG AAA
Accent Color	Team-specific	Blue/Red distinction
Background	Semi-transparent	60-80% opacity
Animation	<100ms transitions	Snappy response

📱 Responsive Scaling

Resolution	HUD Scale	Safe Zone
1080p	100%	Full
1440p	110%	Full
4K	125-150%	90%
Ultrawide	100%	Centered

✅ Implementation Status

Core HUD layout
Health/Armor display
Ammo counter
Crosshair system
Hit markers
Kill feed
Damage numbers (optional)
Menu system
Settings UI
Accessibility options

8.1

Layout

Interface layout is shallow and predictable. Menus never exceed two layers deep to maintain frictionless access.

UI Layout & Navigation

Main Menu → Play / Settings / Quit
Play → Host Game / Join Lobby
In-Game → Inventory / Scoreboard / Pause

8.2

HUD

HUD elements prioritize combat visibility and situational awareness with a minimalistic, non-distracting layout.

HUD

Health & armor indicators
Ammunition panel
Minimal crosshair
Damage & hit indicators

8.3

Feedback Systems

Feedback communicates combat results instantly and clearly with sound, animation, UI, and screen-space effects.

Feedback Systems

Hit markers
Directional damage indicators
Dynamic reticle behavior
Interaction prompts

8.4

Menus

Menus are lightweight, instant-loading, and navigable in under two clicks.

Menus

Inventory (optional)
Settings
Pause Menu

8.5

Accessibility

Basic accessibility features ensure usability across different player needs without altering competitive fairness.

Accessibility Features

Colorblind-safe palettes
Adjustable FOV
Audio sliders
Subtitles for NPC lines

9🔊

AUDIO DESIGN

Audio direction supports the fast-paced arena gameplay with sharp, readable cues, spatial clarity, and high-impact weapon feedback. Music is atmospheric and optional during matches.

🔊 Audio Design

Audio | Feedback

Weapon sounds, footsteps, UI cues, and ambient effects provide instant clarity and improve gameplay situational awareness across all skill levels.

Principle	Description
Spatial	Directionally accurate and 3D-mixed
Readable	Easy to interpret under pressure
Impactful	Forceful and satisfying combat feedback

🎧 Audio Architecture

AUDIO PRIORITY SYSTEM
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  PRIORITY 1 (Never Duck)        PRIORITY 2 (High)
  ─────────────────────          ─────────────────
  • Your weapon fire             • Enemy weapon fire
  • Damage received              • Nearby footsteps
  • Death sound                  • Pickup sounds
  • Critical alerts              • Hit confirmations

  PRIORITY 3 (Medium)            PRIORITY 4 (Low/Ambient)
  ───────────────────            ────────────────────────
  • Distant combat               • Background ambience
  • Teammate sounds              • Environmental loops
  • UI feedback                  • Music (if any)
  • Voice comms                  • Decorative SFX

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📍 Spatial Audio

3D SOUND SPACE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

                        FRONT
                          │
                  ┌───────┼───────┐
                  │       │       │
                  │   ┌───┴───┐   │
           LEFT ──┼───┤PLAYER ├───┼── RIGHT
                  │   └───┬───┘   │
                  │       │       │
                  └───────┼───────┘
                          │
                        BACK

  DISTANCE ATTENUATION:
  ├────────────────────────────────────────────────────►
  0m        10m        25m        50m        100m
  FULL      -6dB      -12dB     -24dB      SILENT

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🔫 Sound Categories

Category	Examples	Spatial	Priority
Weapons	Fire, reload, switch	3D	1-2
Movement	Footsteps, jump, land	3D	2-3
Combat	Hits, damage, death	3D + 2D	1-2
Pickups	Ammo, health, weapons	3D	2
UI	Menu clicks, alerts	2D	2-3
Ambient	Environment, weather	3D	4
Music	Menu, match end	2D	4

🎯 Combat Audio Feedback

WEAPON FIRE CHAIN
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  INPUT          LAYERS                    OUTPUT
  ─────          ──────                    ──────
    │
    │   ┌────────────────────────────┐
    ├──►│  Mechanical (click/action) │──┐
    │   └────────────────────────────┘  │
    │                                   │
    │   ┌────────────────────────────┐  │   ┌──────────┐
    ├──►│  Explosion (main body)     │──┼──►│  MIXED   │
    │   └────────────────────────────┘  │   │  OUTPUT  │
    │                                   │   └──────────┘
    │   ┌────────────────────────────┐  │
    └──►│  Tail (environmental)      │──┘
        └────────────────────────────┘

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  HIT CONFIRMATION:
  
  ┌──────────┐    ┌──────────┐    ┌──────────┐
  │   HIT    │    │ HEADSHOT │    │   KILL   │
  │   tick   │    │  *ding*  │    │  thump   │
  └──────────┘    └──────────┘    └──────────┘
      Low             High           Layered
     pitch           pitch          + confirm

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

👣 Footstep System

Surface	Sound Character	Recognition
Metal	Sharp, ringing	High
Concrete	Flat, solid	Medium
Wood	Hollow, creaky	High
Tile	Clicky, clean	Medium
Grate	Metallic, open	High
Water	Splashy, wet	High

🎚️ Mix Settings

Bus	Default Level	User Adjustable
Master	100%	✓
SFX	100%	✓
Weapons	100%	✓
Footsteps	100%	✓
Ambient	70%	✓
Music	50%	✓
Voice	100%	✓
UI	80%	✓

⚡ Technical Specs

Parameter	Value	Notes
Sample Rate	48 kHz	Standard quality
Format	OGG Vorbis	Compressed
Max Voices	32	Pooled
Spatialization	Unity Audio	HRTF optional
Occlusion	Raycast-based	Performance aware
Reverb Zones	Per-area presets	Indoor/outdoor

✅ Implementation Status

Audio manager singleton
Weapon fire sounds
Footstep surface detection
3D spatial positioning
Hit confirmation sounds
Occlusion system
Reverb zones
Dynamic mixing (ducking)
Settings UI integration

9.1

Music Direction

Music is optional during gameplay, focusing instead on stylized menu and loading tracks inspired by retro-futuristic 90s shooters.

Music Direction

Menu and lobby music emphasize high-energy analog tones and retro flair.

9.2

SFX System & Categories

SFX are categorized for weapons, movement, UI, and ambience, each mixed for clarity during overlapping events.

SFX Categories

Weapon Fire
Reloads
Footsteps
Damage & hit feedback
Ambient loops
UI clicks and confirmations

🎵Audio 1 (Copy)

🎵Audio 2

9.3

Voice Lines & Events

Voice lines are kept lightweight and optional — announcer calls, hit confirmations, or kill streak callouts.

Voice Lines & Events

Announcer (kills, countdowns)
Hit confirmations
Kill streak callouts

9.4

Audio Feedback Loop

Feedback loops reinforce gameplay clarity: every successful action has an immediate, satisfying audio response.

Audio Feedback Loop

Immediate hit sound
Kill confirmation sound
Low-health warnings
Critical reload audio cues

9.5

Audio Feedback Loop (Copy)

Ambient audio is subtle and atmospheric, supporting immersion without masking gameplay-critical cues.

Ambient Audio

Light wind or machinery hums
Environmental reverb zones
Subtle background loops

10🎨

ART BIBLE

Art direction blends retro 90s arena shooter identity with modern gunmetal aesthetics, neon highlights, sharp silhouettes, and clear environmental readability.

✎ Sketch

🎨 Art Bible

Visuals | Style

A striking gunmetal aesthetic supported by neon accents defines the visual identity. Clean silhouettes, readable geometry, and high-contrast UI form the backbone of the game's competitive clarity.

Principle	Description
Gunmetal Grunge	Rough metallic surfaces & heavy industrial tones
Neon Trim	Accent colors for callouts & readability
Competitive Clarity	Everything readable at first glance

🖌️ Visual Identity

STYLE SPECTRUM
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  REALISTIC ◄───────────────────●─────────► STYLIZED
                                │
                          OUR POSITION
                         "Grounded Stylized"

  KEY INFLUENCES:
  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐
  │   QUAKE     │  │  TITANFALL  │  │   DOOM      │
  │  Industrial │  │  Clean Sci-Fi│  │  Bold Color │
  └─────────────┘  └─────────────┘  └─────────────┘

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎨 Color Palette

PRIMARY PALETTE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  BASE TONES (Environment)
  ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐
  │████████│ │████████│ │████████│ │████████│ │████████│
  │████████│ │████████│ │████████│ │████████│ │████████│
  └────────┘ └────────┘ └────────┘ └────────┘ └────────┘
   #1A1A1E    #2D2D35    #3D3D48    #4A4A55    #5C5C68
   Void       Gunmetal   Steel      Slate      Silver

  NEON ACCENTS (UI / Highlights)
  ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐
  │░░░░░░░░│ │░░░░░░░░│ │░░░░░░░░│ │░░░░░░░░│ │░░░░░░░░│
  │░░░░░░░░│ │░░░░░░░░│ │░░░░░░░░│ │░░░░░░░░│ │░░░░░░░░│
  └────────┘ └────────┘ └────────┘ └────────┘ └────────┘
   #00F0FF    #FF3366    #00FF88    #FFAA00    #AA66FF
   Cyan       Red        Green      Orange     Purple
   (Pickup)   (Enemy)    (Health)   (Warning)  (Rare)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🏗️ Material Language

Material	Use Case	Properties
Brushed Metal	Walls, floors, structures	Low roughness, subtle reflection
Worn Steel	Props, machinery, crates	High roughness, scratches, dirt
Grated Metal	Walkways, vents, platforms	Alpha cutout, industrial
Concrete	Floors, pillars, bunkers	Matte, weathered, cracked
Neon Emissive	Signs, trim, pickups	HDR bloom, saturated
Glass/Hologram	Screens, barriers	Transparency, refraction

👤 Character Silhouettes

READABILITY TEST
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  PASS: Identifiable at distance     FAIL: Ambiguous shape

     ┌───┐                              ┌───┐
     │ ○ │                              │   │
     ├───┤                              │   │
    ┌┤   ├┐                             │   │
    │└───┘│                             │   │
     │   │                              │   │
    ┌┘   └┐                             └───┘
    │     │
    └─┘ └─┘

  Distinct head,                    Boxy, unclear
  shoulders, limbs                  proportions

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  TEAM DISTINCTION:
  
  ┌─────────────┐          ┌─────────────┐
  │  TEAM BLUE  │          │  TEAM RED   │
  │   ┌───┐     │          │     ┌───┐   │
  │   │ ○ │ ░░░ │          │ ░░░ │ ○ │   │
  │   └───┘     │          │     └───┘   │
  │  Cool tones │          │  Warm tones │
  │  Cyan glow  │          │  Red glow   │
  └─────────────┘          └─────────────┘

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🔫 Weapon Design Language

Element	Guideline	Purpose
Shape	Distinct silhouette per class	Instant recognition
Size	Scaled to screen presence	Visual hierarchy
Color	Gunmetal base + accent trim	Consistent identity
Glow	Emissive on active state	Feedback clarity
Animation	Snappy, exaggerated	Satisfying feel

🏛️ Environment Hierarchy

VISUAL PRIORITY LAYERS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  LAYER 1 - GAMEPLAY (Highest Contrast)
  ────────────────────────────────────
  Players, Pickups, Hazards, Objectives
  → Bright, saturated, emissive

  LAYER 2 - INTERACTIVE
  ─────────────────────
  Doors, Buttons, Platforms, Cover
  → Medium contrast, subtle highlights

  LAYER 3 - STRUCTURE
  ───────────────────
  Walls, Floors, Pillars, Barriers
  → Low saturation, grounded tones

  LAYER 4 - BACKGROUND (Lowest Contrast)
  ──────────────────────────────────────
  Skybox, Distant geometry, Decorative
  → Desaturated, atmospheric depth

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

💡 Lighting Guidelines

Context	Key Light	Fill	Accent
Arena	Neutral white	Cool blue	Neon highlights
Industrial	Warm orange	Dark shadow	Spark emissive
Tech Lab	Cool white	Cyan fill	Hologram glow
Outdoor	Sun (warm)	Sky (cool)	Neon signs

⚡ Performance Targets

Asset Type	Budget	Notes
Characters	15-25k tris	LOD at distance
Weapons (FP)	8-12k tris	High detail
Weapons (World)	2-4k tris	Simplified
Props	500-2k tris	Instanced
Textures	1024-2048px	Compressed
Draw Calls	<500 per frame	Batched

✅ Art Pipeline Status

Color palette defined
Material library started
Character silhouette guidelines
Weapon design templates
Environment kit (modular)
Prop library
VFX style guide
Lighting presets per biome
LOD pipeline setup

📌 Moodboard

10.1

Visual Pillars (Mood, Color, Materials)

Visual pillars reinforce the identity: metallic industrial surfaces, retro-futuristic neon, and clean FPS silhouettes.

Visual Pillars

Gunmetal + Neon Palette
High-contrast silhouettes
Sharp industrial materials

📌 Moodboard

10.2

Character Art

Characters use simple, readable silhouettes with team-color accents and minimal noise.

Character Art

Simple neutral armor
Team-colored trims
Clean silhouettes for competitive visibility

10.3

Environment Art

Environments mix clean geometric arenas with industrial props, retro lighting, and neon-fused tones.

Environment Art

Industrial metal structures
Neon signage and accents
Clean competitive geometry

10.4

Weapon / Prop Art

Weapons follow a chunky 90s-inspired silhouette with modern material definition.

Weapon & Prop Art

Chunky, readable silhouettes
Metallic materials with subtle wear
Neon highlights for function zones

10.5

UI Art Style

UI blends gunmetal plates, neon-accented highlights, and minimalistic structure.

UI Art Style

Square frames with glow trims
Readable thin-line icons
Subtle scanline effects

10.6

Technical Art Notes (Shaders, VFX)

Technical art focuses on performant shaders, stylized muzzle flashes, and lightweight environment VFX.

Technical Art Notes

Optimized PBR shaders
Stylized muzzle flash VFX
Low-saturation particle sets

11💻

TECH DESIGN

Tech design outlines the engine, tools, networking framework, systems architecture, and performance targets. All systems prioritize multiplayer stability, deterministic behavior, and modular expandability.

⚙️ Tech Design

Unity | Networking | Tools

Built with Unity and powered by the FishNet multiplayer framework, the project emphasizes deterministic systems design, clean modular managers, and scalable architectures suitable for rapid iteration and long-term maintenance.

Principle	Description
Modular	Easily extendable managers and systems
Network-Ready	Sync rules designed around multiplayer fairness
Optimized	Performance-first, low overhead architecture

🏗️ System Architecture

HIGH-LEVEL ARCHITECTURE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ┌─────────────────────────────────────────────────────┐
  │                   GAME LAYER                        │
  │  ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐   │
  │  │ Combat  │ │Movement │ │Inventory│ │   UI    │   │
  │  │ Manager │ │ Manager │ │ Manager │ │ Manager │   │
  │  └────┬────┘ └────┬────┘ └────┬────┘ └────┬────┘   │
  │       └───────────┴───────────┴───────────┘         │
  │                       │                             │
  ├───────────────────────┼─────────────────────────────┤
  │                       ▼                             │
  │              ┌────────────────┐                     │
  │              │  GAME MANAGER  │                     │
  │              │  (Singleton)   │                     │
  │              └───────┬────────┘                     │
  │                      │                              │
  ├──────────────────────┼──────────────────────────────┤
  │                      ▼                              │
  │  ┌──────────────────────────────────────────────┐  │
  │  │              FISHNET LAYER                   │  │
  │  │  ┌──────────┐ ┌──────────┐ ┌──────────┐     │  │
  │  │  │ Network  │ │  Object  │ │  State   │     │  │
  │  │  │ Manager  │ │  Spawner │ │  Sync    │     │  │
  │  │  └──────────┘ └──────────┘ └──────────┘     │  │
  │  └──────────────────────────────────────────────┘  │
  │                      │                              │
  ├──────────────────────┼──────────────────────────────┤
  │                      ▼                              │
  │  ┌──────────────────────────────────────────────┐  │
  │  │              UNITY ENGINE                    │  │
  │  │  Physics │ Rendering │ Audio │ Input         │  │
  │  └──────────────────────────────────────────────┘  │
  └─────────────────────────────────────────────────────┘

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🌐 FishNet Network Model

CLIENT-SERVER AUTHORITY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ┌──────────────┐                    ┌──────────────┐
  │   CLIENT A   │                    │   CLIENT B   │
  │  ┌────────┐  │                    │  ┌────────┐  │
  │  │ Input  │  │                    │  │ Input  │  │
  │  └───┬────┘  │                    │  └───┬────┘  │
  │      │       │                    │      │       │
  │      ▼       │                    │      ▼       │
  │  ┌────────┐  │                    │  ┌────────┐  │
  │  │Predict │  │                    │  │Predict │  │
  │  └───┬────┘  │                    │  └───┬────┘  │
  └──────┼───────┘                    └──────┼───────┘
         │                                   │
         │         ┌──────────────┐          │
         └────────►│    SERVER    │◄─────────┘
                   │  ┌────────┐  │
                   │  │Simulate│  │
                   │  │  Auth  │  │
                   │  └───┬────┘  │
                   │      │       │
                   │      ▼       │
                   │  ┌────────┐  │
                   │  │ State  │  │
                   │  │ Sync   │  │
                   │  └───┬────┘  │
                   └──────┼───────┘
                          │
         ┌────────────────┼────────────────┐
         ▼                                 ▼
  ┌──────────────┐                  ┌──────────────┐
  │  RECONCILE   │                  │  RECONCILE   │
  │   Client A   │                  │   Client B   │
  └──────────────┘                  └──────────────┘

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📦 Core Managers

Manager	Responsibility	Network Role
GameManager	Match state, round logic	Server authority
PlayerManager	Spawn, despawn, tracking	Server authority
CombatManager	Damage, kills, respawn	Server authority
WeaponManager	Loadout, ammo, switching	Client predicted
MovementManager	Physics, abilities	Client predicted
UIManager	HUD, menus, feedback	Client only
AudioManager	Spatial audio, mixing	Client only
PoolManager	Object pooling	Both

🔄 Update Pipeline

CENTRALIZED TICKER SYSTEM
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  TICK GROUPS (Ordered Execution)
  ────────────────────────────────

  ┌─────────────────────────────────────────────────────┐
  │  GROUP 0: INPUT                                     │
  │  └─ Read input, queue commands                      │
  ├─────────────────────────────────────────────────────┤
  │  GROUP 1: PHYSICS                                   │
  │  └─ Movement, collision, physics sim                │
  ├─────────────────────────────────────────────────────┤
  │  GROUP 2: GAMEPLAY                                  │
  │  └─ Combat, abilities, interactions                 │
  ├─────────────────────────────────────────────────────┤
  │  GROUP 3: NETWORK                                   │
  │  └─ State sync, reconciliation                      │
  ├─────────────────────────────────────────────────────┤
  │  GROUP 4: PRESENTATION                              │
  │  └─ Animation, VFX, audio                           │
  ├─────────────────────────────────────────────────────┤
  │  GROUP 5: UI                                        │
  │  └─ HUD updates, menu state                         │
  └─────────────────────────────────────────────────────┘

  TICK RATE: 128 Hz (Server) / Variable (Client)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🛠️ Tech Stack

Component	Technology	Version
Engine	Unity	2022.3 LTS
Networking	FishNet	4.x
Transport	Tugboat (UDP)	Latest
Physics	Unity PhysX	Built-in
Audio	Unity Audio	Built-in
UI	UI Toolkit	Built-in
Build	IL2CPP	Release
Platform	Steam	Steamworks.NET

📊 Performance Budgets

Metric	Target	Hard Limit
Frame Time	<8ms (120+ FPS)	<16ms (60 FPS)
Tick Rate	128 Hz	64 Hz min
Network RTT	<50ms	<150ms playable
Memory	<2 GB	<4 GB
Draw Calls	<500	<800
Triangles	<2M	<4M

🧪 Debug & Tools

EDITOR TOOLING
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ┌─────────────────┐  ┌─────────────────┐
  │ Network Monitor │  │ Performance HUD │
  │  • Ping graph   │  │  • FPS counter  │
  │  • Packet stats │  │  • Memory usage │
  │  • State diff   │  │  • Draw calls   │
  └─────────────────┘  └─────────────────┘

  ┌─────────────────┐  ┌─────────────────┐
  │  Hitbox Viewer  │  │  Console Plus   │
  │  • Colliders    │  │  • Filters      │
  │  • Raycasts     │  │  • Commands     │
  │  • Hit confirm  │  │  • Logging      │
  └─────────────────┘  └─────────────────┘

  BUILD MODES:
  ├── Development   (Full debug, cheats enabled)
  ├── Staging       (Logging, no cheats)
  └── Release       (Stripped, optimized)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📁 Project Structure

Assets/
├── _Project/
│   ├── Scripts/
│   │   ├── Core/           # Managers, singletons
│   │   ├── Player/         # Controller, input
│   │   ├── Combat/         # Weapons, damage
│   │   ├── Network/        # FishNet extensions
│   │   ├── UI/             # HUD, menus
│   │   └── Utilities/      # Helpers, extensions
│   ├── Prefabs/
│   ├── ScriptableObjects/
│   ├── Materials/
│   ├── Audio/
│   └── Scenes/
├── Plugins/
│   ├── FishNet/
│   └── Steamworks.NET/
└── Resources/

✅ Implementation Status

FishNet integration
CentralizedTicker system
Player controller (networked)
Weapon state machine
Object pooling
Full reconciliation pipeline
Steam lobby integration
Dedicated server build
Performance profiling pass
Editor tools suite

11.1

Engine & Tools

Unity (URP) is used for rendering and tools, with custom editor utilities for faster iteration.

🛠️ Engine & Tools

Unity | URP | Custom Tooling

The project is built on Unity with the Universal Render Pipeline, supported by a suite of custom editor tools designed to accelerate content creation and maintain consistency.

Component	Details
Engine	Unity 2022.3 LTS
Render Pipeline	Universal Render Pipeline (URP)
Custom Tools	Map Maker, Item Editors, Debug Utilities

📦 Core Stack

TECHNOLOGY LAYERS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ┌─────────────────────────────────────────────────────┐
  │                 CUSTOM TOOLS                        │
  │  ┌───────────┐ ┌───────────┐ ┌───────────────────┐ │
  │  │ Map Maker │ │Item Editor│ │ Debug Utilities   │ │
  │  └───────────┘ └───────────┘ └───────────────────┘ │
  ├─────────────────────────────────────────────────────┤
  │                 UNITY ENGINE                        │
  │  Physics │ Audio │ Input │ UI Toolkit │ Animation  │
  ├─────────────────────────────────────────────────────┤
  │                 URP RENDERING                       │
  │  Forward+ │ Post-Processing │ Shader Graph │ VFX   │
  └─────────────────────────────────────────────────────┘

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🔧 Custom Editor Tools

Tool	Purpose	Status
Map Maker	Level blockout and layout	🟢 Active
Item Editor	Weapon/pickup configuration	🟢 Active
Prefab Validator	Asset consistency checks	🟡 WIP
Performance Monitor	Real-time profiling HUD	🟢 Active
Network Debugger	FishNet state inspector	🟡 WIP

✅ Setup Checklist

Unity 2022.3 LTS installed
URP configured and optimized
Map Maker tool functional
Item Editor tool functional
Prefab Validator complete
CI/CD pipeline configured
Build automation scripts

11.1.1

GDDEditorTool

📘 GDD Editor Pro
Professional Game Design Documentation for Unity
GDD Editor Pro provides a complete workflow for documenting game concepts, mechanics, systems, and visual references—all directly within the Unity Editor.
🛠 Visual Editors
GDD Editor Pro includes three specialized visual editors to handle different documentation needs.
1. 📊 Graph Editor
Create node-based flowcharts for game logic, state machines, dialogue trees, and system architectures.
Node Types
Flow Control: Start, End, Branch (Fork), Merge (Join), Sequence.
Logic: Decision, Condition, Switch, Random.
Execution: Action, Wait/Delay, Variable, Loop.
Events: Event, Trigger, State, Transition.
2. 📌 Moodboard Editor
Assemble visual reference boards for art direction, style guides, and inspiration.
Item Types
Image: Reference images (project assets or embedded).
Text Note: Sticky notes with customizable colors.
Color Swatch: Palette samples with Hex values.
Shape: Rectangles for layout blocking.
Layer Control Items are organized in a layer hierarchy. You can toggle visibility (👁), lock layers (🔒) to prevent accidental edits, and drag-and-drop to reorder.
3. ✏️ Sketch Editor
A vector drawing tool for diagrams, wireframes, UI mockups, and technical illustrations.
🖼 Asset Registry & Management
The Asset Registry allows you to decouple images from specific file paths. Assign tags to images and reference them anywhere.
Workflow
Open the Assets Tab.
Click + Add Asset.
Assign a unique Tag (e.g., hero-banner).
Configure Alt Text, Captions, and Click Actions.
Dynamic Referencing
Insert images into Section Summaries, Content, or HTML using double-brace syntax:

📤 Publishing & Export
Share your GDD with the team using the powerful export tools.
HTML Export Features
Responsive: Mobile-friendly layout.
Search: Built-in full-text search.
Navigation: Collapsible sidebar and auto-generated Table of Contents.
Light/Dark Mode: Users can toggle themes in the browser.
GitHub Pages Integration
Publish directly to the web with one click:

📋 Overview

GDD Editor Pro is a Game Design Document creation tool built for Unity. It provides a complete workflow for documenting game concepts, mechanics, systems, and visual references—all within the Unity Editor.

✨ Key Features

Feature	Description
Hierarchical Sections	Organize content with unlimited nesting depth
Rich Content Modes	Plain text, Markdown, or raw HTML
Visual Modules	Graph flowcharts, Moodboards, and Sketch canvases
Asset Registry	Tag and reference images anywhere with `{{tag-name}}`
Image Galleries	Grid, Masonry, Carousel, List, and Filmstrip layouts
Export Options	Responsive HTML, GitHub Pages, or standalone files
Theming	Light/Dark modes with full color customization

📁 Document Structure

Sections

Documents are organized into sections that can be nested to any depth. Each section contains:

Field	Description
Title	Section heading displayed in navigation and content
Summary	Brief description shown as a blockquote (supports `{{image}}` tags)
Content	Main body text with Markdown/HTML support
Images	Gallery of images with captions and lightbox
Graph	Node-based flowchart module
Moodboard	Visual reference board with images, notes, and swatches
Sketch	Vector drawing canvas for diagrams

Section Properties

Type — Categorize sections (Concept, Mechanic, System, etc.)
Status — Track progress (Draft, In Progress, Review, Complete)
Priority — Set importance level (Low, Medium, High, Critical)
Highlight — Apply visual emphasis with colored backgrounds
Collapsible — Allow sections to expand/collapse in export
Custom CSS Class — Add custom styling hooks

📊 Graph Editor

The Graph Editor creates node-based flowcharts for documenting game logic, state machines, dialogue trees, and system architectures.

Node Types

Category	Nodes
Flow Control	Start, End, Branch (Fork), Merge (Join), Sequence
Logic	Decision, Condition, Switch, Random
Execution	Action, Wait/Delay, Variable, Loop
Events	Event, Trigger, State, Transition
Organization	Note, SubGraph, Comment

Controls

GRAPH EDITOR SHORTCUTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  TOOLS                         NAVIGATION
  ─────                         ──────────
  Q — Hand tool (pan)           Mouse Wheel — Zoom in/out
  W — Move tool (drag)          Middle Mouse — Pan canvas
  E — Rotate tool               F — Fit to content
  R — Scale tool
  T — Rect tool (resize)        EDITING
                                ───────
                                Delete — Remove selection
                                Click+Drag — Box select

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Connections

Click and drag from an output port to an input port to create connections.

Type	Style	Purpose
Flow	Solid line	Standard execution flow
Conditional	Colored	True/False branches
Optional	Dashed line	Optional paths
Data	Thin line	Variable/data transfer

Groups

Select multiple nodes and use Create Group to organize related nodes visually. Groups can be colored, titled, and collapsed.

📌 Moodboard Editor

The Moodboard Editor creates visual reference boards for art direction, style guides, and inspiration collections.

Item Types

Type	Description
Image	Reference images from project or embedded
Text Note	Sticky notes with customizable colors
Color Swatch	Color palette samples with hex values
Shape	Rectangles for layout and grouping

Controls

MOODBOARD SHORTCUTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  TOOLS                         ACTIONS
  ─────                         ───────
  Q — Hand tool (pan)           Drag & Drop — Add images
  W — Move tool                 Double-click — Edit note text
  E — Rotate tool               Delete — Remove selection
  R — Scale tool
  T — Rect tool (free resize)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Layer Panel

Items are organized in layers with full control:

👁 Visibility toggle per layer/item
🔒 Lock toggle to prevent editing
↑↓ Reorder layers
Expand/collapse layer contents

✏️ Sketch Editor

The Sketch Editor provides vector drawing tools for creating diagrams, wireframes, UI mockups, and technical illustrations.

Drawing Tools

Key	Tool	Description
1	Rectangle	Draw rectangles and squares (hold Shift)
2	Ellipse	Draw ellipses and circles (hold Shift)
3	Line	Draw straight lines
4	Arrow	Draw lines with arrowheads
5	Pencil	Freehand drawing paths
6	Text	Add text labels

Transform Tools

TRANSFORM SHORTCUTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  Q — Hand (pan canvas)
  W — Move selection
  E — Rotate selection
  R — Proportional scale
  T — Free resize (Rect tool)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Style Settings

Fill — Enable/disable fill with color picker
Stroke — Enable/disable stroke with color and width
Canvas Color — Background color for export
Grid — Toggle grid with adjustable size
Snap — Snap to grid while drawing

Layer Management

Like the Moodboard, Sketch supports full layer management with visibility, locking, and reordering of both layers and individual elements.

🖼️ Asset Registry

The Asset Registry allows you to tag images and reference them anywhere in your document using simple tags.

Registering Assets

Open the Assets tab in GDD Editor
Click + Add Asset
Assign a Tag (e.g., hero-banner, logo, screenshot-1)
Select the image source (Project asset or embedded)
Configure alt text, caption, and click action

Using Asset Tags

Reference registered assets anywhere using double-brace syntax:

           → Inserts the image tagged "logo"
{{hero-banner}}    → Inserts the image tagged "hero-banner"
{{screenshot-1}}   → Inserts the image tagged "screenshot-1"

Asset tags work in:

Section Content
Section Summary
Markdown text
HTML content

Asset Properties

Property	Description
Tag	Unique identifier for referencing
Label	Display name in Asset Registry
Alt Text	Accessibility description
Caption	Text shown below image
Alignment	Left, Center, Right, or Full width
Click Action	None, Lightbox, or Open Link
Custom Size	Override width/height

🖼️ Image Galleries

Each section can include an image gallery with multiple layout options.

Gallery Layouts

Layout	Description
Grid	Equal-sized cells in rows and columns
Masonry	Pinterest-style variable height columns
Carousel	Horizontal slider with navigation arrows
List	Vertical stack of full-width images
Filmstrip	Horizontal scrolling row of thumbnails

Gallery Settings

Columns — Number of columns (Grid/Masonry)
Gap — Spacing between items in pixels
Show Captions — Display image captions
Lightbox — Click to view full-size

📤 Export Options

HTML Export

Export your GDD as a standalone HTML file with all assets embedded.

Feature	Description
Theme	Light or Dark mode
Custom Colors	Override all theme colors
Navigation	Collapsible sidebar with search
Table of Contents	Auto-generated with configurable depth
Responsive	Mobile-friendly layout
Lightbox	Full-screen image viewing
Print Styles	Optimized for printing

GitHub Pages Publishing

Publish directly to GitHub Pages with one click:

Configure repository URL and branch
Set Personal Access Token (PAT)
Click Publish
Access at https://username.github.io/repo-name

Export Settings

Setting	Description
Include Images	Embed images in export
Include Modules	Export Graph/Moodboard/Sketch as SVG
Image Lightbox	Enable click-to-enlarge
Start Collapsed	Sections collapsed by default
Show Navigation	Include sidebar navigation
Show Search	Enable search functionality

🎨 Theming & Styling

Document Branding

Element	Purpose
Logo	Displayed in navigation header
Cover Image	Hero image at document top
Favicon	Browser tab icon
Primary Color	Main brand color
Secondary Color	Supporting brand color
Accent Color	Highlights and interactive elements

Section-Level Styling

Each section can override global styles:

Custom header/body fonts
Font sizes and line height
Margins and padding
Background colors
Custom CSS classes

Highlights

Define highlight styles for visual emphasis:

Style	Color	Use Case
Info	Blue	Information callouts
Success	Green	Completed items
Warning	Yellow	Cautions and notes
Danger	Red	Critical warnings
Custom	Any	Project-specific emphasis

⌨️ Keyboard Shortcuts

Global

Shortcut	Action
Ctrl+S	Save document
Ctrl+Z	Undo
Ctrl+Y	Redo
Delete	Delete selection
F	Fit to content

Canvas Editors (Graph/Moodboard/Sketch)

Shortcut	Action
Q	Hand/Pan tool
W	Move tool
E	Rotate tool
R	Scale tool
T	Rect/Resize tool
Mouse Wheel	Zoom
Middle Mouse Drag	Pan
Shift+Click	Add to selection

Sketch-Specific

Shortcut	Action
1	Rectangle tool
2	Ellipse tool
3	Line tool
4	Arrow tool
5	Pencil tool
6	Text tool

💡 Tips & Best Practices

Organization

Use section types consistently to categorize content
Set status on sections to track documentation progress
Use collapsible sections for lengthy technical details
Create a Table of Contents section at the top

Visual Modules

Set explicit canvas dimensions for consistent export sizing
Use the Fit (F) button to frame all content
Group related nodes in the Graph editor
Use layers in Moodboard/Sketch for organization

Images

Register frequently-used images in the Asset Registry
Use meaningful tags like {{ui-main-menu}} instead of {{image-1}}
Set alt text for accessibility
Choose appropriate gallery layout for content type

Export

Preview in browser before publishing
Test on mobile devices for responsive layout
Use GitHub Pages for team sharing
Enable lightbox for detailed images

GDD Editor Pro — Professional game design documentation, right inside Unity.

11.1.2

Editor Prefs

11.1.3

Console System

11.1.4

TaskManager

11.1.5

QuickNotes

11.1.6

UI_Toolkit QuickNotes

User Guide

A complete guide to using Quick Notes Pro effectively in your Unity workflow.

Getting Started

Opening Quick Notes

Navigate to Tools → A2K → Quick Notes (UI Toolkit) in the Unity menu bar.

Quick Notes Pro

A2K Quick Notes Pro v3.0 — A professional note-taking system for the Unity Editor, built with UI Toolkit.

Organize your development thoughts, track bugs, document features, and keep your project knowledge centralized — all without leaving the Unity Editor.

Features

Note Management

Create, edit, and delete notes with rich formatting
Quick-add notes from the header bar
Full-text search across titles, content, and tags
Pin important notes to the top
Archive completed or inactive notes
Drag-to-reorder with animated transitions

Organization

Categories — Group notes by Development, Art, Audio, Design, QA, or custom categories
Tags — Add multiple tags per note for flexible cross-referencing
Icons — 27 emoji icons for visual identification (bugs, ideas, warnings, etc.)
Attachments — Link Unity assets directly to notes via drag-and-drop

Styling System

12 preset accent colors
Custom color picker for unlimited options
Theme System — 5 built-in themes with full customization
Per-Note Styling — Override theme with custom colors, fonts, and spacing
Live preview while editing themes

Productivity

Multi-select with Ctrl/Cmd+Click and Shift+Click
Bulk operations (pin, archive, delete)
Keyboard shortcuts for common actions
Undo/Redo support
Import/Export to JSON
Automatic save and session restoration

Installation

Copy the following files to your Unity project's Editor folder:

```

Assets/

└── Editor/

└── QuickNotes/

├── Quicknotes_UIToolkit.cs

├── Quicknotes_UIToolkit.uxml

├── Quicknotes_UIToolkit.uss

└── Quicknotes_NoteCard.uxml

```

Open Unity and wait for compilation.

Access via menu: Tools → A2K → Quick Notes (UI Toolkit)

Quick Start

Creating Your First Note

Open Quick Notes from Tools → A2K → Quick Notes (UI Toolkit)
Click the + button or press Ctrl+N
Enter a title and content
Select an accent color from the palette

Using Quick Add

Type in the quick-add field at the top of the notes list and press Enter to instantly create a note with that title.

Organizing Notes

Pin — Click the star icon to pin notes to the top
Category — Assign from the dropdown in the editor
Tags — Expand the tags section and add keywords
Archive — Hide completed notes without deleting them

Applying Themes

Click the palette icon in the header to open Theme Manager
Select a built-in theme or create your own
In the Style Sidebar, choose "Theme" and select your preferred theme
Or choose "Custom" for per-note styling

Keyboard Shortcuts

Shortcut	Action
Ctrl/Cmd + N	Create new note
Ctrl/Cmd + A	Select all notes
Ctrl/Cmd + S	Force save
Delete	Delete selected notes
Escape	Clear selection

Data Storage

Notes are stored in your project's ProjectSettings folder:

File	Purpose
`A2K_Notes.json`	Notes data
`A2K_NotesCategories.json`	Category definitions
`A2K_NotesThemes.json`	Custom themes

These files are automatically created on first use and saved whenever changes occur.

Requirements

Unity 2021.3 or later
UI Toolkit (included with Unity)

Architecture

Quick Notes Pro follows a strict separation of concerns:

File	Responsibility
`.uxml`	Structure only — element hierarchy and names
`.uss`	Styling only — colors, layout, animations
`.cs`	Logic only — data binding, events, persistence

This architecture enables:

Easy theming without code changes
Clean, maintainable codebase
Optimal runtime performance

See ARCHITECTURE.md for technical details.

License

Support

For issues, feature requests, or contributions, please contact the A2K development team.

The window can be docked alongside other Unity panels or floated independently. Minimum size is 750×500 pixels.

Interface Overview

┌─────────────────────────────────────────────────────────────────┐
│  [🎨] [☆] [▼ Category]      [🔍 Search...]      [+ Quick Add]  │
├──────────────────────┬──────────────────────────────────────────┤
│                      │  [📝] [Color Palette] [🎨] [★] [⋮]      │
│  ┌────────────────┐  ├──────────────────────────────────────────┤
│  │ 📝 Note Title  │  │  ┌──────────────────────────────────┐   │
│  │ Preview text...│  │  │  Title                           │   │
│  │ Category  2h   │  │  └──────────────────────────────────┘   │
│  └────────────────┘  │  ┌──────────────────────────────────┐   │
│                      │  │                                  │   │
│  ┌────────────────┐  │  │  Content area...                 │   │
│  │ 💡 Another     │  │  │                                  │   │
│  │ More text...   │  │  └──────────────────────────────────┘   │
│  └────────────────┘  │                                          │
│                      │  Category: [▼ Development]               │
│                      │  Tags: [tag1] [tag2] [+ Add]            │
│                      │  Attachments: [📄 Script.cs]             │
├──────────────────────┴──────────────────────────────────────────┤
│  12 notes (2 archived)                    [☐ Show Archived]     │
└─────────────────────────────────────────────────────────────────┘

Managing Notes

Creating Notes

Method 1: New Note Button

Click the + button in the notes list header
Press Ctrl/Cmd + N

Method 2: Quick Add

Type in the quick-add field at the top
Press Enter to create instantly
The note inherits the current category filter

Editing Notes

Select a note from the list to open it in the editor panel:

Title — Click to edit, auto-saves on change
Content — Multi-line text area with scroll
Icon — Click the emoji button to choose from 27 icons
Color — Select from 12 presets or use the color picker
Pin — Click the star to pin/unpin

Deleting Notes

Select a note and click the trash icon
Right-click a note and choose "Delete"
Select multiple notes and use bulk delete

All deletions can be undone with Ctrl/Cmd + Z.

Organization

Pinning

Pinned notes always appear at the top of the list, regardless of sort order.

Toggle Pin:

Click the star icon in the editor toolbar
Right-click a note and select "Pin"

Filter Pinned:

Click the star button in the header to show only pinned notes.

Archiving

Archive notes you want to keep but hide from the main list.

Toggle Archive:

Right-click a note and select "Archive"
Use bulk archive for multiple notes

View Archived:

Check "Show Archived" in the footer to include archived notes.

Attachments

Link Unity assets directly to notes for quick reference.

Adding Attachments

Drag and Drop:

Select a note
Drag any asset from the Project window
Drop it on the attachments area

From Selection:

Select an asset in the Project window
Click "Add Attachment" in the note
Choose "Link Selected Asset"

Using Attachments

Select — Click to ping the asset in the Project window
Remove — Click the × to unlink (doesn't delete the asset)

Supported Types

All Unity asset types are supported:

Scripts (📜)
Textures (🖼)
Audio (🔊)
Prefabs (📦)
Other (📄)

Themes and Styling

Style Modes

Each note can use one of three style modes:

Mode	Description
Default	Uses USS base styles
Theme	Applies a selected theme
Custom	Per-note color overrides

Using Themes

Click the style button (🎨) in the editor toolbar
Open the Style Sidebar
Select "Theme" mode
Choose a theme from the dropdown

Built-in Themes

Theme	Description
Default Dark	Yellow accent, dark gray background
Ocean	Cyan accent, deep blue tones
Forest	Green accent, natural earth tones
Sunset	Orange accent, warm browns
Lavender	Purple accent, soft violets

Creating Custom Themes

Click the palette icon in the header
Open Theme Manager
Click "New Theme"
Configure colors and typography
Use the live preview to verify
Click "Save"

Theme Properties

Property	Description
Accent Color	Left border color
Card Background	Note card fill color
Title Color	Title text color
Content Background	Editor area color
Content Color	Body text color
Title Size	Title font size (px)
Content Size	Body font size (px)
Accent Width	Left border width (px)
Padding	Internal spacing (px)

Per-Note Custom Styling

Open the Style Sidebar
Select "Custom" mode
Adjust individual properties
Click "Save as Theme" to reuse later

Multi-Select Operations

Selecting Multiple Notes

Action	Result
Ctrl/Cmd + Click	Toggle individual selection
Shift + Click	Select range from last clicked
Ctrl/Cmd + A	Select all visible notes
Escape	Clear selection

Bulk Operations

When multiple notes are selected, a toolbar appears:

Pin — Toggle pin on all selected
Archive — Archive all selected
Delete — Delete all selected

Right-click for context menu options.

Import and Export

Exporting Notes

Click the options menu (⋮)
Select "Export Notes..."
Choose a location and filename
All notes export to JSON format

Importing Notes

Click the options menu (⋮)
Select "Import Notes..."
Choose a JSON file
Select import mode:

- Merge — Add to existing notes

- Replace — Clear and import

- Cancel — Abort import

Keyboard Shortcuts

Shortcut	Action
Ctrl/Cmd + N	Create new note
Ctrl/Cmd + A	Select all notes
Ctrl/Cmd + S	Force save all data
Ctrl/Cmd + Z	Undo last action
Ctrl/Cmd + Y	Redo
Delete	Delete selected notes
Escape	Clear selection
Enter (in quick-add)	Create note from text

Tips and Best Practices

Workflow Recommendations

Use Categories for Scope — Development, Art, Audio maps to team roles
Use Tags for Topics — "multiplayer", "bug", "polish" work across categories
Pin Active Work — Keep current tasks pinned
Archive Completed — Don't delete, archive for reference

Performance Tips

Archive old notes rather than keeping hundreds visible
Use specific search terms rather than browsing
Keep attachment count reasonable per note

Data Safety

Notes auto-save on every change
Use Export regularly for backups
JSON files can be version-controlled
Files are stored in ProjectSettings (project-specific)

Troubleshooting

Notes Not Saving

Check that ProjectSettings folder exists
Verify write permissions
Check Console for error messages

Styling Not Applying

Ensure USS file is in same folder as UXML
Check that element names match between UXML and C#
Verify no syntax errors in USS file

Window Not Opening

Check Console for compilation errors
Verify all four files are present
Ensure files are in an Editor folder

Import Failing

Verify JSON file is valid
Check that it was exported from Quick Notes
Look for special characters in note content

Architecture

Quick Notes Pro is built with Unity's UI Toolkit following a strict Model-View separation pattern. This document details the technical architecture and design decisions.

File Structure

QuickNotes/
├── Quicknotes_UIToolkit.cs      # Logic layer (EditorWindow)
├── Quicknotes_UIToolkit.uxml    # Main window structure
├── Quicknotes_UIToolkit.uss     # Complete stylesheet
└── Quicknotes_NoteCard.uxml     # Note card template

Separation of Concerns

UXML — Structure Only

UXML files define what elements exist and their hierarchy. They contain:

Element types (VisualElement, Button, TextField, etc.)
Element names for C# queries
CSS classes for styling
Hierarchical relationships

UXML files do not contain:

Inline styles
Hardcoded colors or dimensions
Asset GUIDs or paths
Template references (loaded dynamically)

<!-- Example: Clean UXML structure -->
<VisualElement name="note-card" class="note-card">
    <VisualElement name="accent-bar" class="accent-bar"/>
    <VisualElement name="card-content" class="card-content">
        <Label name="title" class="card-title"/>
    </VisualElement>
</VisualElement>

USS — Styling Only

USS files define how elements appear. They contain:

Colors, backgrounds, borders
Layout properties (flex, padding, margins)
Typography (font size, weight, color)
Transitions and hover states
CSS variables for theming

USS files do not contain:

Business logic
Unsupported pseudo-classes (:last-child, :nth-child)
Asset references

/* Example: USS with CSS variables */
:root {
    --accent: #F5D923;
    --bg-dark: #1A1A1C;
}

.note-card {
    background-color: var(--bg-dark);
    border-radius: 6px;
    transition: background-color 0.15s;
}

.note-card:hover {
    background-color: #2A2A2C;
}

C# — Logic Only

The C# file handles all runtime behavior:

Dynamic asset loading via AssetDatabase.FindAssets()
Element queries and event binding
Data management and persistence
Theme application and dynamic styling
User interaction handling

// Example: Dynamic asset loading (no hardcoded GUIDs)
private string FindAssetPath(string name, string extension)
{
    var guids = AssetDatabase.FindAssets($"{name} t:VisualTreeAsset");
    foreach (var guid in guids)
    {
        var path = AssetDatabase.GUIDToAssetPath(guid);
        if (path.EndsWith($".{extension}")) return path;
    }
    return "";
}

Data Architecture

Storage Files

File	Location	Format
Notes	`ProjectSettings/A2K_Notes.json`	JSON
Categories	`ProjectSettings/A2K_NotesCategories.json`	JSON
Themes	`ProjectSettings/A2K_NotesThemes.json`	JSON

Data Classes

NotesData
├── Notes: List<Note>
├── LastOpenedId: string
├── Version: int
└── DefaultThemeId: string

Note
├── Id: string (GUID)
├── Title: string
├── Content: string
├── ColorIndex: int
├── ColorHex: string
├── IconId: string
├── Category: string
├── Tags: List<string>
├── Attachments: List<Attachment>
├── LinkedTaskId: string
├── Created: string (ISO date)
├── Modified: string (ISO date)
├── Pinned: bool
├── Archived: bool
├── SortOrder: int
├── Style: NoteStyle
└── UseCustomStyle: bool

NoteStyle
├── ThemeId: string
├── AccentHex: string
├── CardBgHex: string
├── TitleColorHex: string
├── ContentBgHex: string
├── ContentColorHex: string
├── TitleSize: int
├── ContentSize: int
├── TitleBold: bool
├── TitleItalic: bool
├── AccentWidth: int
└── Padding: int

NoteTheme
├── Id: string
├── Name: string
├── Description: string
├── Author: string
├── Created: string
├── [Same color/style properties as NoteStyle]
└── IsBuiltIn: bool

Attachment
├── Name: string
├── Path: string
├── GUID: string
└── Type: string

Panel System

The content panel uses a mode-based system to switch between views:

private enum PanelMode { NoteEditor, ThemeManager, ThemeEditor, CategoryManager }

Each mode corresponds to a view container in UXML:

note-editor-view — Main note editing interface
empty-state-view — Shown when no note is selected
theme-manager-view — Theme list and management
theme-editor-view — Individual theme editing
category-manager-view — Category list and management

Only one view is visible at a time via the .hidden class.

Styling Pipeline

Static vs Dynamic Styling

Type	Source	Applied By
Static	USS	UI Toolkit (automatic)
Dynamic	Theme/NoteStyle	C# (programmatic)

Static styling handles:

Base colors and layout
Hover states and transitions
Typography defaults
Component structure

Dynamic styling handles:

Per-note accent colors
Theme-based backgrounds
Active/selected states
Custom style overrides

Style Resolution Order

Default — USS base styles
Theme — If note.Style.ThemeId is set, apply theme colors
Custom — If note.UseCustomStyle is true, apply note.Style directly
State — Active/selected states override background

private NoteStyle GetNoteStyle(Note note)
{
    // Check for theme-based style
    if (!string.IsNullOrEmpty(note.Style?.ThemeId))
    {
        var theme = _themes?.Themes.FirstOrDefault(t => t.Id == note.Style.ThemeId);
        if (theme != null) return ThemeToStyle(theme);
    }
    // Fall back to note's custom style or default
    return note.Style ?? new NoteStyle();
}

ListView Implementation

The notes list uses UI Toolkit's ListView with virtualization for performance:

_notesList.makeItem = MakeNoteCard;      // Creates reusable card elements
_notesList.bindItem = BindNoteCard;      // Binds data to card elements
_notesList.fixedItemHeight = 72;         // Enables virtualization
_notesList.selectionType = SelectionType.None;  // Custom selection handling
_notesList.reorderable = true;           // Drag-to-reorder support
_notesList.reorderMode = ListViewReorderMode.Animated;

Card Template Loading

The note card template is loaded dynamically at runtime:

var cardTemplatePath = FindAssetPath("Quicknotes_NoteCard", "uxml");
_noteCardTemplate = AssetDatabase.LoadAssetAtPath<VisualTreeAsset>(cardTemplatePath);

If the template isn't found, cards are created programmatically as a fallback.

Undo System

Quick Notes integrates with Unity's Undo system via a ScriptableObject buffer:

private class NotesUndoState : ScriptableObject { public string JsonState; }

private void RecordUndo(string operationName)
{
    Undo.RecordObject(_undoState, operationName);
    _undoState.JsonState = JsonUtility.ToJson(_data);
}

private void OnUndoRedo()
{
    _data = JsonUtility.FromJson<NotesData>(_undoState.JsonState);
    RefreshUI();
}

Performance Considerations

Virtualized ListView — Only visible cards are rendered
CSS Variables — Theme colors defined once, referenced everywhere
Minimal Repaints — Targeted refresh methods update only affected elements
Lazy Loading — Assets loaded on demand, not at compile time
Efficient Queries — Elements cached in fields, not re-queried per frame

Extensibility

Adding New Icons

Add entries to the ICONS array:

public static readonly IconInfo[] ICONS = {
    new("custom", "🎮", "Gaming"),
    // ...
};

Adding Built-in Themes

Add entries in EnsureBuiltInThemes():

new NoteTheme {
    Id = "builtin_custom",
    Name = "Custom Theme",
    IsBuiltIn = true,
    AccentHex = "#...",
    // ...
}

Adding New Panel Views

Add UXML structure for the view
Add enum value to PanelMode
Query the view element in QueryElements()
Handle visibility in RefreshContentPanel()
Create refresh method for the view

Testing Checklist

Notes persist across Unity restart
Themes apply correctly to cards and editor
Multi-select works with Ctrl and Shift
Drag-to-reorder updates sort order
Undo/Redo restores previous state
Import/Export produces valid JSON
All keyboard shortcuts function
No hardcoded GUIDs in UXML files
No unsupported pseudo-classes in USS

User Guide

A complete guide to using Quick Notes Pro effectively in your Unity workflow.

Getting Started

Opening Quick Notes

Navigate to Tools → A2K → Quick Notes (UI Toolkit) in the Unity menu bar.

The window can be docked alongside other Unity panels or floated independently. Minimum size is 750×500 pixels.

Interface Overview

┌─────────────────────────────────────────────────────────────────┐
│  [🎨] [☆] [▼ Category]      [🔍 Search...]      [+ Quick Add]  │
├──────────────────────┬──────────────────────────────────────────┤
│                      │  [📝] [Color Palette] [🎨] [★] [⋮]      │
│  ┌────────────────┐  ├──────────────────────────────────────────┤
│  │ 📝 Note Title  │  │  ┌──────────────────────────────────┐   │
│  │ Preview text...│  │  │  Title                           │   │
│  │ Category  2h   │  │  └──────────────────────────────────┘   │
│  └────────────────┘  │  ┌──────────────────────────────────┐   │
│                      │  │                                  │   │
│  ┌────────────────┐  │  │  Content area...                 │   │
│  │ 💡 Another     │  │  │                                  │   │
│  │ More text...   │  │  └──────────────────────────────────┘   │
│  └────────────────┘  │                                          │
│                      │  Category: [▼ Development]               │
│                      │  Tags: [tag1] [tag2] [+ Add]            │
│                      │  Attachments: [📄 Script.cs]             │
├──────────────────────┴──────────────────────────────────────────┤
│  12 notes (2 archived)                    [☐ Show Archived]     │
└─────────────────────────────────────────────────────────────────┘

Managing Notes

Creating Notes

Method 1: New Note Button

Click the + button in the notes list header
Press Ctrl/Cmd + N

Method 2: Quick Add

Type in the quick-add field at the top
Press Enter to create instantly
The note inherits the current category filter

Editing Notes

Select a note from the list to open it in the editor panel:

Title — Click to edit, auto-saves on change
Content — Multi-line text area with scroll
Icon — Click the emoji button to choose from 27 icons
Color — Select from 12 presets or use the color picker
Pin — Click the star to pin/unpin

Deleting Notes

Select a note and click the trash icon
Right-click a note and choose "Delete"
Select multiple notes and use bulk delete

All deletions can be undone with Ctrl/Cmd + Z.

Organization

Pinning

Pinned notes always appear at the top of the list, regardless of sort order.

Toggle Pin:

Click the star icon in the editor toolbar
Right-click a note and select "Pin"

Filter Pinned:

Click the star button in the header to show only pinned notes.

Archiving

Archive notes you want to keep but hide from the main list.

Toggle Archive:

Right-click a note and select "Archive"
Use bulk archive for multiple notes

View Archived:

Check "Show Archived" in the footer to include archived notes.

Attachments

Link Unity assets directly to notes for quick reference.

Adding Attachments

Drag and Drop:

Select a note
Drag any asset from the Project window
Drop it on the attachments area

From Selection:

Select an asset in the Project window
Click "Add Attachment" in the note
Choose "Link Selected Asset"

Using Attachments

Select — Click to ping the asset in the Project window
Remove — Click the × to unlink (doesn't delete the asset)

Supported Types

All Unity asset types are supported:

Scripts (📜)
Textures (🖼️)
Audio (🔊)
Prefabs (📦)
Other (📄)

Themes and Styling

Style Modes

Each note can use one of three style modes:

Mode	Description
Default	Uses USS base styles
Theme	Applies a selected theme
Custom	Per-note color overrides

Using Themes

Click the style button (🎨) in the editor toolbar
Open the Style Sidebar
Select "Theme" mode
Choose a theme from the dropdown

Built-in Themes

Theme	Description
Default Dark	Yellow accent, dark gray background
Ocean	Cyan accent, deep blue tones
Forest	Green accent, natural earth tones
Sunset	Orange accent, warm browns
Lavender	Purple accent, soft violets

Creating Custom Themes

Click the palette icon in the header
Open Theme Manager
Click "New Theme"
Configure colors and typography
Use the live preview to verify
Click "Save"

Theme Properties

Property	Description
Accent Color	Left border color
Card Background	Note card fill color
Title Color	Title text color
Content Background	Editor area color
Content Color	Body text color
Title Size	Title font size (px)
Content Size	Body font size (px)
Accent Width	Left border width (px)
Padding	Internal spacing (px)

Per-Note Custom Styling

Open the Style Sidebar
Select "Custom" mode
Adjust individual properties
Click "Save as Theme" to reuse later

Multi-Select Operations

Selecting Multiple Notes

Action	Result
Ctrl/Cmd + Click	Toggle individual selection
Shift + Click	Select range from last clicked
Ctrl/Cmd + A	Select all visible notes
Escape	Clear selection

Bulk Operations

When multiple notes are selected, a toolbar appears:

Pin — Toggle pin on all selected
Archive — Archive all selected
Delete — Delete all selected

Right-click for context menu options.

Import and Export

Exporting Notes

Click the options menu (⋮)
Select "Export Notes..."
Choose a location and filename
All notes export to JSON format

Importing Notes

Click the options menu (⋮)
Select "Import Notes..."
Choose a JSON file
Select import mode:

- Merge — Add to existing notes

- Replace — Clear and import

- Cancel — Abort import

Keyboard Shortcuts

Shortcut	Action
Ctrl/Cmd + N	Create new note
Ctrl/Cmd + A	Select all notes
Ctrl/Cmd + S	Force save all data
Ctrl/Cmd + Z	Undo last action
Ctrl/Cmd + Y	Redo
Delete	Delete selected notes
Escape	Clear selection
Enter (in quick-add)	Create note from text

Tips and Best Practices

Workflow Recommendations

Use Categories for Scope — Development, Art, Audio maps to team roles
Use Tags for Topics — "multiplayer", "bug", "polish" work across categories
Pin Active Work — Keep current tasks pinned
Archive Completed — Don't delete, archive for reference

Performance Tips

Archive old notes rather than keeping hundreds visible
Use specific search terms rather than browsing
Keep attachment count reasonable per note

Data Safety

Notes auto-save on every change
Use Export regularly for backups
JSON files can be version-controlled
Files are stored in ProjectSettings (project-specific)

Troubleshooting

Notes Not Saving

Check that ProjectSettings folder exists
Verify write permissions
Check Console for error messages

Styling Not Applying

Ensure USS file is in same folder as UXML
Check that element names match between UXML and C#
Verify no syntax errors in USS file

Window Not Opening

Check Console for compilation errors
Verify all four files are present
Ensure files are in an Editor folder

Import Failing

Verify JSON file is valid
Check that it was exported from Quick Notes
Look for special characters in note content

API Reference

Complete reference for Quick Notes Pro data structures, classes, and customization points.

Namespace

namespace A2K.Editor.Tools.Quicknotes.UIToolkit

Main Class

QuickNotesUIToolkit

public class QuickNotesUIToolkit : EditorWindow

The main editor window class. Access via menu Tools → A2K → Quick Notes (UI Toolkit).

Static Method

[MenuItem("Tools/A2K/Quick Notes (UI Toolkit)")]
public static void ShowWindow()

Opens or focuses the Quick Notes window.

Data Classes

Note

Represents a single note entry.

[Serializable]
public class Note
{
    public string Id;              // Unique GUID identifier
    public string Title;           // Note title
    public string Content;         // Note body text
    public int ColorIndex;         // Preset color index (0-11), -1 for custom
    public string ColorHex;        // Custom hex color (e.g., "#FF5733")
    public string IconId;          // Icon identifier (see Icons section)
    public string Category;        // Category name or empty
    public List<string> Tags;      // List of tag strings
    public List<Attachment> Attachments;  // Linked Unity assets
    public string LinkedTaskId;    // Reserved for task integration
    public string Created;         // ISO date string (yyyy-MM-dd HH:mm)
    public string Modified;        // ISO date string (yyyy-MM-dd HH:mm)
    public bool Pinned;            // Pin to top of list
    public bool Archived;          // Hidden from main view
    public int SortOrder;          // Position in list
    public NoteStyle Style;        // Styling configuration
    public bool UseCustomStyle;    // True = use Style directly, False = use theme
}

NoteStyle

Per-note styling configuration.

[Serializable]
public class NoteStyle
{
    public string ThemeId;         // Theme to apply, or empty for custom
    public string AccentHex;       // Accent/border color
    public string CardBgHex;       // Card background color
    public string TitleColorHex;   // Title text color
    public string ContentBgHex;    // Content area background
    public string ContentColorHex; // Content text color
    public int TitleSize;          // Title font size in pixels (default: 16)
    public int ContentSize;        // Content font size in pixels (default: 12)
    public bool TitleBold;         // Bold title text
    public bool TitleItalic;       // Italic title text
    public bool ContentBold;       // Bold content text
    public bool ContentItalic;     // Italic content text
    public int AccentWidth;        // Left border width in pixels (default: 4)
    public int Padding;            // Internal padding in pixels (default: 12)
    
    public void Clear();           // Resets all properties to empty/default
}

NoteTheme

Reusable theme definition.

[Serializable]
public class NoteTheme
{
    public string Id;              // Unique GUID identifier
    public string Name;            // Display name
    public string Description;     // Optional description
    public string Author;          // Theme creator
    public string Created;         // ISO date string
    public string AccentHex;       // Accent/border color
    public string CardBgHex;       // Card background color
    public string TitleColorHex;   // Title text color
    public string ContentBgHex;    // Content area background
    public string ContentColorHex; // Content text color
    public int TitleSize;          // Title font size
    public int ContentSize;        // Content font size
    public bool TitleBold;         // Bold title
    public bool TitleItalic;       // Italic title
    public bool ContentBold;       // Bold content
    public bool ContentItalic;     // Italic content
    public int AccentWidth;        // Left border width
    public int Padding;            // Internal padding
    public bool IsBuiltIn;         // True = protected from deletion
    
    public NoteTheme DeepCopy();   // Creates independent copy with new ID
}

Attachment

Represents a linked Unity asset.

[Serializable]
public class Attachment
{
    public string Name;    // Asset name
    public string Path;    // Asset path (e.g., "Assets/Scripts/Player.cs")
    public string GUID;    // Unity asset GUID for path recovery
    public string Type;    // Asset type name (e.g., "MonoScript", "Texture2D")
}

NotesData

Root container for notes storage.

[Serializable]
public class NotesData
{
    public List<Note> Notes;       // All notes
    public string LastOpenedId;    // ID of last active note
    public int Version;            // Data format version (current: 3)
    public string DefaultThemeId;  // Default theme for new notes
}

ThemesData

Root container for themes storage.

[Serializable]
public class ThemesData
{
    public List<NoteTheme> Themes; // All themes
    public string DefaultThemeId;  // Global default theme
}

CategoriesData

Root container for categories storage.

[Serializable]
public class CategoriesData
{
    public List<string> Categories; // Category names
}

Icons

IconInfo

public class IconInfo
{
    public string Id;    // Unique identifier
    public string Emoji; // Display emoji
    public string Name;  // Human-readable name
}

Available Icons

ID	Emoji	Name
`note`	📝	Note
`idea`	💡	Idea
`star`	⭐	Important
`bookmark`	🔖	Bookmark
`flag`	🚩	Flag
`bug`	🐛	Bug
`fix`	🔧	Fix
`code`	💻	Code
`gear`	⚙️	Settings
`rocket`	🚀	Deploy
`question`	❓	Question
`check`	✅	Done
`warning`	⚠️	Warning
`error`	❌	Error
`clock`	🕐	Pending
`link`	🔗	Link
`file`	📄	File
`folder`	📁	Folder
`image`	🖼️	Image
`audio`	🔊	Audio
`chat`	💬	Chat
`email`	📧	Email
`user`	👤	Person
`team`	👥	Team
`high`	🔴	High Priority
`medium`	🟡	Medium Priority
`low`	🟢	Low Priority

Colors

Preset Colors

12 preset accent colors (index 0-11):

Index	Color	RGB
0	Yellow	`(0.95, 0.85, 0.35)`
1	Orange	`(0.95, 0.65, 0.25)`
2	Red	`(0.95, 0.45, 0.45)`
3	Pink	`(0.95, 0.55, 0.75)`
4	Purple	`(0.75, 0.55, 0.95)`
5	Indigo	`(0.45, 0.55, 0.95)`
6	Cyan	`(0.35, 0.75, 0.95)`
7	Teal	`(0.35, 0.85, 0.65)`
8	Green	`(0.45, 0.85, 0.45)`
9	Lime	`(0.65, 0.75, 0.45)`
10	Gray	`(0.55, 0.55, 0.60)`
11	White	`(0.85, 0.85, 0.85)`

File Paths

Constants

private const string DATA_PATH = "ProjectSettings/A2K_Notes.json";
private const string CATEGORIES_PATH = "ProjectSettings/A2K_NotesCategories.json";
private const string THEMES_PATH = "ProjectSettings/A2K_NotesThemes.json";
private const string PREFS_PREFIX = "A2K_QuickNotes_";

EditorPrefs Keys

Key	Type	Purpose
`A2K_QuickNotes_ShowTags`	bool	Tags section expanded
`A2K_QuickNotes_ShowArchived`	bool	Show archived notes

CSS Classes

Note Card

Class	Applied To
`.note-card`	Card container
`.note-card-active`	Currently selected card
`.note-card-selected`	Multi-selected card
`.accent-bar`	Left color bar
`.card-content`	Main content area
`.card-top-row`	Icon, title, indicators row
`.card-bottom-row`	Category, date row
`.card-title`	Note title label
`.card-preview`	Content preview label
`.card-indicators`	Tag/attachment/pin icons

Editor Panel

Class	Applied To
`.editor-toolbar`	Top toolbar
`.editor-accent-bar`	Left accent bar
`.editor-content-section`	Main editor area
`.title-field`	Title input
`.content-field`	Content textarea
`.style-sidebar`	Right style panel

Buttons

Class	Applied To
`.icon-button`	Icon-only buttons
`.icon-button-active`	Active state
`.small-button`	Compact buttons
`.btn-accent`	Accent color button
`.btn-green`	Green action button
`.btn-yellow`	Yellow warning button
`.btn-red`	Red danger button

Utility

Class	Applied To
`.hidden`	Display: none
`.tag-chip`	Tag badges
`.color-swatch`	Color picker buttons
`.color-swatch-selected`	Selected color

CSS Variables

Defined in :root for theming:

:root {
    --bg-dark: #1A1A1C;
    --bg-med: #242426;
    --bg-light: #2D2D2F;
    --bg-lighter: #353538;
    
    --border: #3A3A3D;
    --border-light: #4A4A4D;
    
    --accent: #F5D923;
    --accent-hover: #FFE44D;
    
    --green: #4CAF50;
    --green-hover: #66BB6A;
    --yellow: #FFC107;
    --yellow-hover: #FFCA28;
    --red: #F44336;
    --red-hover: #EF5350;
    
    --text: #E8E8E8;
    --text-dim: #AAAAAA;
    --text-muted: #666666;
    
    --selection: #3D5A80;
}

Built-in Themes

ID	Name	Accent	Card BG	Content BG
`builtin_default`	Default Dark	#F5D923	#2D2D2F	#1A1A1C
`builtin_ocean`	Ocean	#00D4FF	#0A2540	#061830
`builtin_forest`	Forest	#4CAF50	#1B2E1B	#0D1A0D
`builtin_sunset`	Sunset	#FF7043	#3E2723	#1A0E0A
`builtin_lavender`	Lavender	#9C27B0	#2A1B2E	#1A0D1E

JSON Schema

Notes Export Format

{
    "Notes": [
        {
            "Id": "guid-string",
            "Title": "Note Title",
            "Content": "Note content...",
            "ColorIndex": 0,
            "ColorHex": "",
            "IconId": "note",
            "Category": "Development",
            "Tags": ["tag1", "tag2"],
            "Attachments": [
                {
                    "Name": "Script",
                    "Path": "Assets/Scripts/Script.cs",
                    "GUID": "asset-guid",
                    "Type": "MonoScript"
                }
            ],
            "LinkedTaskId": "",
            "Created": "2024-01-15 10:30",
            "Modified": "2024-01-15 14:22",
            "Pinned": false,
            "Archived": false,
            "SortOrder": 0,
            "Style": {
                "ThemeId": "",
                "AccentHex": "",
                "CardBgHex": "",
                "TitleColorHex": "",
                "ContentBgHex": "",
                "ContentColorHex": "",
                "TitleSize": 16,
                "ContentSize": 12,
                "TitleBold": true,
                "TitleItalic": false,
                "ContentBold": false,
                "ContentItalic": false,
                "AccentWidth": 4,
                "Padding": 12
            },
            "UseCustomStyle": false
        }
    ],
    "LastOpenedId": "guid-string",
    "Version": 3,
    "DefaultThemeId": ""
}

Quick Reference Card

A single-page reference for Quick Notes Pro.

Keyboard Shortcuts

Key	Action
`Ctrl+N`	New note
`Ctrl+A`	Select all
`Ctrl+S`	Save
`Ctrl+Z`	Undo
`Delete`	Delete selected
`Escape`	Clear selection
`Enter`	Quick-add note

Mouse Actions

Action	Result
Click note	Select and edit
Ctrl+Click	Toggle multi-select
Shift+Click	Range select
Right-click	Context menu
Drag note	Reorder
Drag asset	Attach to note

Icons

📝 Note      💡 Idea      ⭐ Important   🔖 Bookmark
🚩 Flag      🐛 Bug       🔧 Fix         💻 Code
⚙️ Settings  🚀 Deploy    ❓ Question    ✅ Done
⚠️ Warning   ❌ Error     🕐 Pending     🔗 Link
📄 File      📁 Folder    🖼️ Image       🔊 Audio
💬 Chat      📧 Email     👤 Person      👥 Team
🔴 High      🟡 Medium    🟢 Low

Styling Modes

Mode	Description
Default	USS base styles
Theme	Apply saved theme
Custom	Per-note colors

Built-in Themes

Theme	Accent
Default Dark	🟡 Yellow
Ocean	🔵 Cyan
Forest	🟢 Green
Sunset	🟠 Orange
Lavender	🟣 Purple

Data Files

ProjectSettings/
├── A2K_Notes.json           # Notes
├── A2K_NotesCategories.json # Categories
└── A2K_NotesThemes.json     # Themes

Menu Path

Tools → A2K → Quick Notes (UI Toolkit)

Default Categories

General
Development
Art
Audio
Design
QA

Color Palette

🟡 Yellow   🟠 Orange   🔴 Red      💗 Pink
🟣 Purple   🔵 Indigo   🔷 Cyan     🩵 Teal
🟢 Green    🫛 Lime     ⬜ Gray     ⚪ White

Quick Tips

Quick Add — Type in header field, press Enter
Pin — Click ★ to keep notes at top
Archive — Hide without deleting
Search — Matches title, content, and tags
Themes — Click 🎨 in header for Theme Manager
Export — Menu → Options → Export Notes

11.1.7

Vector Art

11.1.8

MoodBoard

11.1.9

Bookmarks

11.1.10

SceneManager

11.1.11

WorldManager

11.2

Systems Architecture

Architecture is modular: each core system is isolated into single-responsibility managers with ScriptableObject-driven data.

Systems Architecture

GameManager
PlayerManager
UIManager
AudioManager
NetworkManager (FishNet)

11.3

Networking

FishNet handles replication, prediction, and lag compensation. Sync rules ensure fairness and consistency across clients.

Networking (FishNet)

State Replication
Movement Prediction
Hit Lag Compensation
Authority Rules per Object Type

11.4

Performance Targets

Optimized for stable 60–144 FPS gameplay and predictable network tick rates.

Performance Targets

60–144 FPS target
Low GC allocations
Stable FishNet tick timing

11.5

Platform Requirements

Designed for modern mid-tier PCs with standard multiplayer capabilities.

Platform Requirements

Windows PC
Steam Integration

11.6

Build Pipeline & Version Control

Uses Git for version control and automated build profiles for quick iteration.

Build Pipeline & Version Control

Git + Git LFS
Automated build scripts
Separate development & release branches

12📌

PRODUCTION PLAN

The production plan outlines the development roadmap, milestones, risks, and QA structure required to deliver a polished multiplayer FPS experience.

Production Plan

ProductionRoadmap

A clear milestone-driven production structure ensures that core systems, networking, weapons, maps, and UI reach completion in a stable and testable order.

MilestonesFeature-based delivery checkpoints.

Risk ControlEarly identification of blockers.

TestingRegular playtests & automated checks.

12.1

Milestones & Sprints

Milestones are structured around core deliverables: movement, combat, networking, UI, and maps.

Milestones & Sprints

Movement + Player Controller
Weapons + Combat
Networking Integration
First Playable Map
UI / HUD Completion

12.2

Feature List

Features organized into must-haves, should-haves, and optional enhancements.

Feature List

Must Have: Movement, Shooting, Networking, One Map
Should Have: Grenades, Basic Cosmetics
Nice to Have: Bots, Hub Area

12.3

Risk Assessment

Risks relate primarily to networking complexity, weapon balancing, and performance targets.

Risk Assessment

Networking desync
Weapon balance inconsistencies
Performance drops

12.4

QA Plan

QA emphasizes regular playtests and automated regression checks on core systems.

QA Plan

Weekly playtests
Automated test scenes
Network stress tests

12.5

Release Roadmap

The roadmap defines the timeline from prototype to early access, with structured feature rollout.

Release Roadmap

Prototype → Vertical Slice → Alpha → Beta → Early Access