---
title: Asset Physics Rules
category: product
entity_type: skill
price: $15
canonical: https://forgehouse.ai/skills/asset-physics-rules/
lang: en
hreflang_alt: https://forgehouse.ai/tr/skiller/asset-physics-rules/
last_updated: 2026-06-20
---

# Asset Physics Rules

> Apply physics-grounded asset placement rules for 2.5D isometric game maps gravity contact…

A physics-grounded ruleset for placing assets on 2.5D isometric game maps so scenes read as believable instead of amateur. It enforces gravity contact, leaning angles, center-of-mass stacking, spill direction, material-specific effects, and layer hierarchy through a three-layer validation: physical reality, narrative logic, and visual balance, that every asset must pass.

## Use cases
- Validating an asset's placement before adding it to a scene
- Auditing an existing scene for leaning-angle and collision-overlap errors
- Verifying AI- or designer-generated asset layouts against physics rules
- Diagnosing why a map looks random or amateurish
- Designing biome-specific environmental storytelling
- Setting up pivot and collision metadata for imported assets

## Benefits
- Scenes that feel real and immersive instead of cheap and uncanny
- Big QA savings by catching placement errors at edit time, not in review
- No wall-clip exploits from overlapping collision boxes
- Consistent depth and lighting cues that hold up in screenshots and trailers

## What’s included
- A three-layer validation model for physics, narrative, and visual balance
- A material-behavior matrix and asset-definition data schema
- A leaning-angle enforcement validator and collision-overlap detector
- A global shadow-direction component for consistent lighting
- A secondary-asset requirement pattern for environmental storytelling
- A 12-item placement checklist and an anti-pattern catalog

## Who it’s for
Level designers and technical artists building 2.5D isometric maps who want professional, physically believable scenes.

## How it runs
A floating barrel ruins a scene faster than any bug. Every map asset passes three validation layers (physics, narrative, visual balance) before it earns a place:
1. Reads the asset's AssetDefinition ScriptableObject first: pivot (must be bottom-center 0.5, 0), collision box size and offset, material type, placement padding radius, layer tier and the list of required secondary assets.
2. Runs Layer 1, physical reality: does the asset touch the ground (no floating objects, ever), is a leaning object at 55-75 degrees toward the surface it leans on, and does a stacked object's center of mass sit inside the contact surface below it? The LeaningAngleValidator flags anything under 15 degrees as a hard physics violation in the Inspector.
3. Runs Layer 2, narrative logic: why is this object here, who left it, and is every primary asset linked to at least one secondary (a big tree gets rooted ground, mossy stones, a leaf pile)? A random prop with no story connection is rejected.
4. Runs Layer 3, visual balance: density compared to neighboring regions differs by at most one level, repeated sprites carry rotation and scale variance, and every shadow follows the single global light direction enforced by ShadowCaster2D.
5. Sweeps the scene with the CollisionOverlapDetector: any two solid colliders whose bounds intersect (triggers excluded) are logged as errors, and the post-save hook blocks the scene with exit 2 until they are fixed.
6. Closes with the 12-item checklist from the rule file. An asset passes only at 12/12; one fail means reject with root-cause feedback, which is also the gate the game-qa agent runs before any build.

## FAQ
### Is this an automated check or rules I apply by hand?
It's a ruleset you validate layouts against: placement, leaning angle, collision overlap. You can audit a scene whether you built it by hand or generated it; it judges the layout, it doesn't move objects for you.

### Does it actually simulate physics, or is it a set of rules of thumb?
It's grounded rules, like believable leaning angles and no floating or overlapping geometry, not a live physics engine. That's deliberate: the goal is catching the placement errors that make a scene read as amateur, fast, without a simulation.

### Will this make my map look good?
It makes a map look believable, with assets sitting where physics says they should, but composition, lighting, and color are a separate craft. It's also scoped to 2.5D isometric maps specifically.

## Price
$15, one-time, no subscription. VAT included.

Related guide: [A 2.5D isometric game-dev AI workflow with Unity](https://forgehouse.ai/guides/unity-isometric-ai-workflow/)