Clunk
Open Studio
Custom game asset work

When your game needs an asset,
we follow it to the handoff.

Create a new asset, inspect what you already have, or sort out the last step into your engine. Start with a written scope and separate what is possible from what still needs checking.

Draft an inquiry Explore the product
Scope before deliveryPrice and timing follow the inquiry
CUSTOM WORKFLOWINQUIRY ONLY

From requirements to handoff

  1. 01Collect constraints
  2. 02Set the scope
  3. 03Verify with files
  4. 04Pass on the next step

We do not mark an engine or result as checked until it has been checked.

WHAT CAN YOU HAND OFF

Choose one clear lane
and start small.

Use Clunk's product directly, or narrow the scope around your project's constraints.

01

Create a new asset

Make a 3D model, sprite sheet, or 2D image for your game and check the file before handoff.

  • Shape the style from references
  • Confirm GLB, glTF, PNG, or another needed format
  • Record provenance, licensing, and the file fingerprint
Create in Clunk
02

Inspect or repair a file

Open a GLB or glTF, measure polygons, materials, dimensions, and structure, then keep the original separate from any new file.

  • Measure facts from the actual file
  • Separate blockers from warnings
  • Return a new file and its inspection result
Open the inspector
03

Connect it to a game

Match the file contents to your project and document the engine import path and a runnable example.

  • Confirm where the actual file goes
  • Record engine and version differences
  • Add MCP or API guidance when it helps
See connection options
HOW WE WORK

Short inquiry,
traceable handoff.

We do not promise a large package first. Confirm one asset or a small set, then decide what comes next.

Useful details to bring

  • Target platform and engine version
  • Style references or links
  • Required file formats and quantity
  • Commercial-use and licensing requirements

An inquiry does not confirm production, price, or delivery dates. Payments are not open right now.

  1. 01

    Collect constraints

    We take the game, engine and version, file count, and reference links.

  2. 02

    Set the scope

    We separate create, repair, and integration work from anything needing more evidence.

  3. 03

    Verify with files

    The handoff includes file contents, measured facts, and remaining limits—not only a screenshot.

  4. 04

    Pass on the next step

    We deliver the agreed files, inspection result, and integration notes.

Product

Solve product-sized problems in the product

Turn a public asset, try the creator, or run the inspector first. Bring only the work that needs a project-specific scope to the inquiry.

Need assets for your game?

Tell us what you need to create, repair or bring into your engine. Start with one asset or a small set so we can discuss a concrete scope.

This is a project inquiry. Scope, feasibility, price and delivery dates are not confirmed by sending it.

Payments are currently unavailable during beta.

Draft a project inquiry
No mail app? Copy this template

Copy the fields below into your email and send it to junsuopar@gmail.com

Game / project:

Need (asset creation / repair / integration):

Engine and version:

Files, quantity and format:

Style reference links:

Preferred timing and budget (optional):

Commercial use and license requirements:
Custom work

Tell us the scope for your project

Draft an inquiry