User
├─ id (PK)
├─ username
├─ email
├─ password_hash
├─ avatar_url
├─ reputation
├─ role (member, junior_mod, senior_mod, admin)
└─ created_at
Category
├─ id (PK)
├─ name
├─ description
└─ parent_category_id (FK → Category)
Thread
├─ id (PK)
├─ title
├─ author_id (FK → User)
├─ category_id (FK → Category)
├─ created_at
├─ updated_at
├─ is_sticky
├─ is_locked
├─ view_count
└─ tags (many‑to‑many via ThreadTag)
Post
├─ id (PK)
├─ thread_id (FK → Thread)
├─ author_id (FK → User)
├─ content (markdown)
├─ created_at
├─ edited_at
├─ upvotes / downvotes
└─ is_accepted_answer (bool)
Tag
├─ id (PK)
├─ name
└─ description
ReputationLog
├─ id (PK)
├─ user_id (FK → User)
├─ change (int)
├─ reason (enum: upvote, accepted_answer, badge, admin_adjust)
└─ created_at
Notification
├─ id (PK)
├─ user_id (FK → User)
├─ type (enum: reply, mention, tag_sub, system)
├─ payload (JSON)
├─ read_at (nullable)
└─ created_at
PM_Conversation
├─ id (PK)
├─ participant_ids (JSON array)
└─ created_at
PM_Message
├─ id (PK)
├─ conversation_id (FK → PM_Conversation)
├─ sender_id (FK → User)
├─ body
├─ created_at
└─ read_by (JSON array of user_ids)
Feel free to swap the tech stack (SQL vs. NoSQL) – the relationships stay the same.
When external hosting sites like MediaFire and Mega would purge files due to copyright claims, the forum acted as a digital ark. Users maintained backup threads for tools that had vanished from the surface web, including specific versions of model converters and UV unwrappers that are no longer supported by their original developers.
In an age of AI-generated noise and asset flips, the MIAS3DXWorld Forum remains human-scale, craft-driven, and ruthlessly curious. We are not building for metaverse investors or NFT roadmaps. We are building for the 3 a.m. creator who just solved a lightmap UV error and wept.
We are building for the player who will sit on that virtual bench and feel something real.
We are building the fifth dimension — not of space or time, but of intention.
