A useful Sprunki original character starts with a small design brief: one recognisable silhouette, a limited colour plan and a clear sound role. Open Sprunki OC Maker to explore the controls actually available, then use the practice notes to record your decisions. The brief remains useful even when a desired feature is not provided by that particular tool.
Jump to a section
Write your original character brief
Use the maker's available controls, then note the working name, silhouette, palette, sound role and asset sources. Keep unimplemented ideas separate from the current draft.
“OC” means an original character idea; it does not automatically mean a playable mod, an exported sprite sheet or an audio generator. This guide separates the concept you design from the functions a browser maker implements. It also keeps your own invention distinct from existing character profiles and fan interpretations.
Start with a role rather than a long biography
Write one sentence describing what the character contributes, such as a soft repeating pulse or a short answering phrase. This is a design goal, not a claim that the tool can generate that sound. You can develop the audio later with suitable tools and material you are allowed to use.
The sound-role guide provides practical categories: beat, effect, melody and vocal. Pick the role that helps your idea, but do not treat the categories as rigid limits. A character may serve more than one role; choose a primary one so the first draft has a clear purpose.
Give the silhouette one readable feature
Choose one feature that remains visible when the design is small: a distinct head shape, an asymmetrical accessory or a simple outline change. Begin with that feature before adding details. If the character is only distinguishable by tiny marks, it may become hard to recognise in a compact game stage.
Use the character directory for comparison and vocabulary, not as a set of parts to copy without thought. You can notice that a design is easy to recognise without reproducing its entire face, costume and name. Write how your draft differs in shape or function rather than claiming novelty merely because you recoloured a familiar figure.
Choose a restrained palette with a purpose
Try one main colour, one supporting colour and one accent. This is a starting exercise rather than a fixed rule. Assign the accent to the feature you want people to notice, then check whether the figure is still readable against the background you plan to use. A colour that looks clear on white may disappear on a similarly coloured stage.
Do not rely only on colour to identify an important state. A changed outline, symbol or expression can make a state easier to distinguish. Write the intended visual difference in plain language. If the maker lacks the control needed to express it, keep the idea in the brief instead of claiming that the current draft already implements it.
Inspect the maker before promising an output
Open the maker and list the controls you can actually use: the available choices, any randomisation, any reset action and any visible save or export function. Test a small change before building the complete draft. The presence of a character preview does not prove that the tool exports editable art, animations or a playable game.
If an export control exists, try it and inspect the resulting file or image. Record what was saved and what was not. A screenshot can document a visual concept, but it does not contain a sound assignment or interaction logic. The Scratch project guide explains why editing a project is a separate workflow from using a finished player.
Make a brief another creator could understand
| Field | Useful entry |
|---|---|
| Working name | A name you can change after checking for confusion |
| Shape | One distinctive outline feature |
| Palette | Main, supporting and accent colours with their purposes |
| Sound role | The job the sound should perform |
| Interaction | What should happen when selected or removed |
| Unimplemented ideas | Features that remain sketches or notes |
| Sources | Origins of any art, sound or project you used |
Be specific enough that a collaborator can tell what is an instruction and what is a preference. “Use a brief accent when selected” is more actionable than “make it cool.” Label an example as an example; do not present a sample name or role from this guide as established Sprunki lore.
Design state changes as readable differences
If your concept has two states, decide what changes and what stays recognisable. You might preserve the silhouette while changing an expression or accent. That gives the viewer a connection between the two drawings. Avoid adding a second state solely because you assume every original character needs one.
For a darker concept, describe the intended presentation and choose it deliberately. The horror guide separates visual changes from story claims. A state sketch is not proof of a canonical event, and a drawing of an alternate form does not mean the current maker or game can switch to it.
Test the draft at the size and context you need
Look at the design as a small thumbnail and against the intended background. Can you still identify the main feature? Does the accent compete with the face? Change one thing, compare again and keep the version that communicates your idea more clearly. Record the reason so the next revision does not accidentally undo the improvement.
If the character is intended for a mixing stage, ask what happens when several characters appear together. The beginner mixing guide provides a small arrangement context, while the mod selection guide helps you find contrasting visual examples to study. Inspiration should lead to a design decision, not an unsupported claim of ownership over borrowed material.
Keep asset origins and sharing limits visible
Record whether each asset was drawn or recorded by you, supplied by the maker or obtained from another source. Keep the relevant source link and usage conditions with the draft. Do not describe a generated combination of supplied parts as wholly hand-drawn, and do not assume that adding a credit automatically resolves every reuse restriction.
If you later build a playable project, the mod creation guide is a separate next step. Test the sound and controls independently of the concept art. A finished OC brief is already a useful outcome; it should not be advertised as a released game until an actual playable result exists.
Finish with one clear concept and a next action
Copy the brief, preserve the visible draft using the tool's real capabilities and list one next action: simplify the silhouette, revise the palette, source a sound or implement a selection response. The practice checklist helps track these decisions but does not generate art or audio and does not certify originality.
The maker and catalogue links above identify the tools and examples used by this guide. The design exercises are editorial suggestions rather than official character rules. You have completed the task when the concept is understandable, its current implementation is honestly described and its source notes travel with the draft.