Pixel Game Asset Atlas Template

Based on [Game Theme: {argument name="Game Theme" default="Demon Slayer/Tanjiro"}], create a high-completion, high-information-density, series-publishable "Pixel World Asset Atlas".

This is not a regular pixel illustration or a single game scene image, but a "2D pixel game asset overview map" for game development, art design, level design, and visual proposals. The image needs to be like a complete game material instruction board, systematically organizing the core characters, enemies, items, terrains, scenes, mechanisms, Boss, and decorative elements required for [Game Type: {argument name="Game Type" default="Side-scrolling Action"}] into one image, forming a clear, professional, reusable game asset atlas.

[Basic Settings]
Theme Worldview: [Game Theme]
Game Type: [Game Type]
Era Background: [Era Background]
Protagonist Identity: [Protagonist Identity]
Enemy Type: [Enemy Type]
Main Scene: [Main Scene Environment]
Overall Style: [Style Direction, e.g., {argument name="Style" default="16-bit Retro Arcade Pixel Style"}]
Main Color: [Main Color]
Auxiliary Color: [Auxiliary Color]
Accent Color: [Accent Color]
Aspect Ratio: [Aspect Ratio, Landscape 4:3]
If not filled in, automatically match the optimal solution based on the game theme.

[Overall Image Requirements]
The image uses a landscape large canvas with a light or low-interference background, overall resembling a game development asset table, pixel setting collection spread page, or instruction manual-style resource directory. All elements should be 2D pixel art sprites with unified pixel density, clear black or dark outlines, limited color steps, and retro game texture. Do not generate realistic photography style, 3D rendering style, thick paint illustration style, or movie poster style. The focus is on "system completeness, clear classification, rich resources, and strong development potential."

[Layout Structure]
The entire image uses a modular grid layout with fine lines dividing different resource areas. Each area needs a numbered title and short classification label, with the overall reading path from left to right, top to bottom. The layout should have the orderliness of instruction manuals, game development documents, material atlases, and setting boards. Information density should be high but not chaotic; elements within each module should be equidistantly arranged, maintaining clear readability.

[Required Modules]
1. Player Character Module: Display complete action frames, including standing, walking/running, jumping, etc. Action frames should be arranged horizontally, like a game sprite sheet.
2. Enemy Unit Module: Design various enemies, including normal, ranged, heavy, elite units, etc.
3. Weapons and Items Module: Display melee, ranged, projectiles, effects, pick-ups, etc.
4. Basic Terrain Block Module: Display ground, walls, platforms, corners, different material blocks.
5. Natural/External Scene Resource Module: Display trees, grass, rocks, obstacles.
6. Building/Base/Camp Resource Module: Display doors, windows, walls, ladders, camp facilities.
7. Special Terrain Module: Display bridges, water bodies, cliffs, cave entrances.
8. Indoor/Underground/Facility Resource Module: Display pipes, consoles, metal doors, equipment.
9. Boss / Encounter Resource Module: Display large Bosses, special vehicles, giant mechanisms.
10. General Decoration and Interactive Elements Module: Display ladders, ropes, signs, switches, mechanisms.

[Visual Detail Requirements]
All resources need to maintain unified pixel size logic and worldview consistency. Proportions should be clear. Action frames need to reflect continuity; terrain blocks should be tileable; items and mechanisms should have functional recognizability; Boss elements need to have a sense of oppression.

Machine-translated — the original is what produced this result.

✨ Generate Save Copy prompt Share Original post Open in Hitboard