roblox-game-marketing-art

Roblox game icons and thumbnails

These are user preferences learned while creating Merge a Farm artwork, not universal rules for every Roblox game. Follow the current request when it differs.

Reference research

Inspect actual images before choosing a direction. A game page's large promotional thumbnail is not its square discovery icon. Inventory pages can contain many historical variants; inspect more than the first visible row when useful. Do not infer authorship, conversion performance or official status merely from inventory ownership. Learn compositions and visual clarity; adapt to the current game's real mechanics.

Useful reference collection: https://www.roblox.com/users/537836346/inventory/#!/places . Pages 1–2 inspected September 2026 show split comparisons, small-to-large crops, players for scale, and close-up crop rewards. Their existence is not evidence of performance.

Visual preferences

• Prefer authentic Roblox promotional renders or staged screenshot appearance. Avoid glossy Pixar-like toy renders, cinematic bloom, over-modelled hair and busy decorative scenes.
• Classic bacon hair should resemble the normal smooth brown Pal Hair accessory: broad curved strips and modest brown highlights, not orange faceted shards. Use the supplied/approved reference for identity.
• Make gameplay or its payoff immediately visible. One clear action or progression contrast beats a collection of unrelated props.
• Keep the background sparse. Baseplate studs should be small, low contrast and close to Roblox's actual surface. Giant rounded raised pegs are a recurring generation error; do not call an approximation exact. For exact fidelity use an actual supplied/Studio surface reference.
• Objects should have sensible rigid geometry. Carrots repeatedly curved inward accidentally: their tips should stay on their own straight centerlines; moving objects together does not mean bending them.
• Faces are intentional. This user liked a mischievous half-lidded toothy grin for the confident character. Use a curious expression when a concept calls for uncertainty; do not silently replace an approved face with wide-eyed cheerfulness.
• Current Merge a Farm baseline: close floor-level framing, two bare straight carrots held in block hands, smooth brown bacon hair, plain large white question mark with black outline, cyan sky, restrained green baseplate. No soil attached to held carrots. The user tried and removed arrows, halos and sunburst rays. Treat those as disfavored defaults, not permanent prohibitions.
• For progression split icons, express the change through imagery without BEFORE/AFTER text when requested. Keep the same recognizable character across halves. Relate wealth to the game's actual economy.

Iteration discipline

Use the imagegen workflow for raster generation/editing. Select the exact version the user identifies, especially when they reattach an older image. Later versions are not automatically preferred.

For narrow edits, preserve camera, pose, composition, identity and untouched objects explicitly. Separate reference roles: edit target vs hair reference vs face reference. Do not import a reference's unwanted background, lighting or other traits.

Inspect outputs for requested changes before reporting success. Common failures: carrots still bent, face drift, character appearing buried after reframing, overly prominent fictional studs, residual arrows/glow. Fix targeted failures rather than redesigning approved elements.

Save versioned images and exact prompts in the project's marketing-art directory, preserving previous versions. Square icons are the default established here; confirm or infer the intended thumbnail aspect ratio from the request rather than stretching a square asset. No upload or publish is implied by making art.

Merge a Farm provenance

Approved baseline lives in the Merge a Farm project at art/marketing/merge-a-farm-icon-v10.png, with its prompt alongside it. Earlier v8 supplies the preferred expression; v9 introduced the preferred hair; v10 combines those and removes rays/glow. This path is project-specific, not a dependency for other games. Read the current game's mechanics before inventing promotional features.