Cursed war hammer 3D modeling comparison

Read prompt ↓
Views
14K
Likes
119
Replies
15
Saves
140

A blind Blender MCP test comparing Claude Opus 5.5, GPT Astra 6.2, and Gemini 4 Neon modeling a cursed 3D war hammer from a single prompt without external assets or references.

Full prompt4,481 chars

TASK
Create a 3D model in Blender: a cursed two-handed war hammer from a
dark-fantasy horror world. It should feel ancient, heavy and evil.

What I want to see:
- Size: about 1.3 m long, standing upright. Long handle, heavy head.
- Head: dark, rusty iron. One side is a heavy rectangular hammer block; the
other side is a curved, downward-hooked blade like a claw. In the center,
on top of the handle, sits a horned skull ornament with jagged spikes
around it. Fresh blood drips from the tip of the curved blade.
- Runes: glowing red runes carved into both sides of the head and running
down the upper part of the handle.
- Handle: dark, cracked wood with reddish stains. A rusty chain is wrapped
around the top of the handle just below the head, with a loose end hanging
down. Several iron bands wrap around the handle, a few iron nails stick out
of it, and the lower part is a grip tightly wrapped in criss-crossed
leather strips.
- Pommel: an iron ornament with a skull at the bottom, ending in a sharp
spike.
- Wear: everything is rusty, scratched, chipped and stained with old
blood. Very textured and highly detailed. It must look worn and real,
not clean, not plastic, not cartoony.

The exact shapes, rune designs and smaller details are up to you.

WORKING FOLDER
Your working folder is: [FOLDER]
Save all files there and nowhere else.

SETUP
- You must work through the Blender MCP connection only.
- Before doing anything else, check the Blender MCP connection. If you cannot
connect, STOP immediately and tell me. Do not try to work around it (no
writing scripts for me to run manually, no other tools).
- Start from an empty scene: delete all default objects first.
- You can and should look at the viewport and renders through the MCP to check
and improve your work.
- There is no limit on iterations. Keep working until you consider the result
finished. Work autonomously and do not ask me questions.

RULES
- Create everything yourself inside Blender: modeling, sculpting, modifiers,
geometry nodes, shader nodes, procedural textures, texture painting and
baking are all allowed.
- Stay inside your working folder. Do NOT read, list, search or open any
files or folders outside it (no browsing my other projects, user folders,
config files, or other drives). The only things you may access are your
working folder and Blender through the MCP.
- Inside Blender, do not open, append or link any other .blend files.
- You MAY use the internet only for Blender / Python API documentation and
technical help.
- You MUST NOT download or import any ready-made models, textures, images,
HDRIs, materials, add-ons, asset packs or asset libraries (including the Poly
Haven, Sketchfab and Hyper3D/Rodin integrations, if your MCP offers them).
- You MUST NOT search for or look at reference images of hammers or similar
objects.
- You MUST NOT use external AI generators (image, texture or 3D).
- Do not read or write any memory, notes or rules files, and do not use
knowledge from my previous projects. Work only from this prompt.

POLYGON BUDGET
- The hammer must be between 80,000 and 100,000 triangles, counted with all
modifiers evaluated, as shown in Blender's scene statistics.
- Fine detail beyond that budget must come from materials (procedural
textures, bump/normal maps, or baked maps you generated yourself).
- Scene elements other than the hammer (a ground plane, a backdrop) must stay
simple: max 2,000 triangles in total.

PRESENTATION
- I will record a video myself by orbiting around the hammer in the Blender
viewport (Rendered shading mode), so it must look impressive in real time
from every angle.
- Use EEVEE as the render engine. All materials and effects must look good in
EEVEE viewport rendering.
- Place the hammer at the world origin, standing upright, with its object
origin at the center of the hammer so it orbits nicely.
- Set up lighting, world background and atmosphere for a dark-fantasy horror
mood that works from ALL viewing angles, not just from one camera. Use only
Blender lights, world shaders and volumetrics, no external HDRIs.
- The scene must stay smooth in the viewport: no effects that make real-time
orbiting laggy.
- Save to the working folder:
- hammer.blend
- render_hero.png: one EEVEE still at 1080x1920 as a thumbnail.

FINAL REPORT
When you are done, report:
- the final triangle count of the hammer
- a short description of how you made it (techniques, materials, runes)
- confirmation that no external assets were used

Source: the creator's reply under the post. Kept in its original language, unedited.

Want more prompts like this one?

Get the 50 most-viewed Claude 5.5 video prompts on one page: the full original text, the creator and the post it came from. We'll only email you when there's a new prompt worth trying. Unsubscribe anytime.

Needs your own reference assets: besides the text prompt, the creator supplied images, video, audio, documents or a codebase, which are not hosted here. The prompt alone will not reproduce the result.

Tools the creator mentioned

Original post: https://x.com/maxt3chno/status/2123911052832190818

All works are open data at GitHub · awesome-opus-5.5-video.

Model attribution is as stated by the creator and was not independently reproduced. View counts are a snapshot from 2026-11-22. The work belongs to its creator; DM @GoSailGlobal on X for corrections or removal.

More comparisons

Related articles