Aincrad Rewritten

«System Announcement»Current objective · Floor 1

Aincrad
Rewritten

Kirito doesn't exist here. You take his place.

None of his history carries over. You start on floor 1 as your own person, and what you become and who you trust decide how the death game ends.

Join the Floor 1 team See the game

01 · Current operation

Floor 1 has to work end to end.

The Town of Beginnings, the fields above it, and the first boss clear form one shippable milestone. Every later floor has to play by the rules this one proves.

Milestone boundary

Floor 1 vertical slice

In production

  1. Town of BeginningsIdentity, quests, shops, and the first people who remember you.
    In scope
  2. Fields and combatFirst-person sword skills, enemies, traversal, and the route upward.
    In scope
  3. First boss clearThe encounter that proves a complete floor can hold together.
    Milestone
  4. The floor stays aliveQuests you finished, shops, and the people on this floor keep changing after the boss dies.
    Persistent
The milestone ends at the boss clear. The world state does not.

«Recruiting»

Build the work Floor 1 cannot ship without.

Required production work is paid on agreed milestones, whether or not the game releases. Volunteer work never blocks a release.

  • 3D artists

    Enemy models, and environment kits for the Town of Beginnings and the fields above it.

    Paid

    Join as a 3D artist

  • Animators

    First-person sword-skill sets, plus the enemy animation the floor 1 boss fight runs on.

    Paid

    Join as an animator

  • Composers and sound designers

    Town themes, field ambience, and the audio that sells a sword connecting.

    Paid

    Join for audio

  • Writers

    Side quests and dialogue for the people still living on the floors you have cleared.

    Volunteer

    Join as a writer

  • Godot programmers

    Tools, editor workflow, and systems work the floor can ship without.

    Volunteer

    Join as a programmer

No unwritten taste tests.

One person reviews every contribution against a written spec. Feedback names the rule and the change.

  1. 01

    Take a written brief

    The task names its scope, milestone, and acceptance rules before work begins.

    Brief
  2. 02

    Build against it

    You know which decisions are fixed and which ones are yours to make.

    Work
  3. 03

    Review named rules

    Revisions come back as itemized changes against the brief, never "doesn't feel right."

    Review
  4. 04

    Accept or repair the spec

    If the reviewer cannot point to a rule, the work is accepted and the missing rule is added.

    Decision

Project initialization confirmed

Early development has begun.

There is little to show yet. New entries appear when there is concrete progress to report.

Read the system log

Build the part that gets the first floor across the line.

Choose a role