Becoming Better
Game Developers Together

DiNusty Empire · Game Developer Knowledge Base

A community-driven knowledge base built by game developers, for game developers — workflows, art fundamentals, career guidance, and industry insight, all grounded in real shipped games.

/ to focus

All

Workflows, fundamentals, career guidance, industry insight — everything in one place.

0 topics

Have Something Worth Sharing, or a Topic Suggestion?

Submit a topic for review, or suggest one you would like to see covered. Approved entries are credited to your profile.

Notifications

Loading notifications...

Review Queue

Welcome back

Password

Join the Codex

Create an account to submit entries and save bookmarks across devices.

or sign up with email

Username

Visible on your submissions. Lowercase, no spaces.

Password

Magic Link

Enter your email and we'll send you a sign-in link — no password needed.

Check your email

We sent a confirmation link to your email address.

Saved Entries

0 entries saved

No saved entries yet

Tap the bookmark icon on any post to save it for later — works across mobile and desktop.

Suggest an Edit

Your suggestion will be reviewed by an editor

Entry

—

Edit the content below

Ctrl+B Bold

Ctrl+U Underline

Ctrl+V Paste image

Select text → toolbar appears

Game References — optional

Tags — optional

Comma separated.

External Links — optional

Note for the reviewer — optional

Suggest a Topic

Have an idea for a post but don't want to write it yourself? Drop it here — anyone can browse the open list.

Tags

Comma separated.

External Links — optional

Writing Guide

A good entry is specific, practical, and saves someone time. Think of it as the thing you wish existed when you were figuring something out.

Structure

Title

Be specific and descriptive. Bad: "UE5 Lighting". Good: "How to set up Lumen for a shipped mobile game without killing performance."

Summary

1-2 sentences. What does this cover and who is it for? This shows on the card so make it count.

Content — suggested format

1. The Problem — what situation or challenge does this address?

2. The Solution / Technique — explain the approach clearly. Use headings, lists, images.

3. Key Settings / Steps — the specific values, commands, or decisions that matter.

4. Watch Outs — common mistakes or things to avoid.

5. Further Reading — link to docs, videos, or other resources.

Tips

Write for someone with 1-2 years experience unless it's explicitly a beginner or advanced topic

Screenshots and diagrams go a long way — paste directly from clipboard

Cite your sources — use the quote block for attributed content

Tag the game engine, software, or tools this applies to

✗ Avoid copying documentation verbatim — add your own insight

✗ No promotional content or self-advertising

Template to copy

## The Problem
[Describe the situation or challenge]

## The Solution
[Explain your approach]

## Key Steps / Settings
- Step 1
- Step 2
- Step 3

## Watch Outs
- [Common mistake or gotcha]

## Further Reading
- [Link label](URL)

Becoming BetterGame Developers Together

Have Something Worth Sharing, or a Topic Suggestion?

Becoming Better
Game Developers Together