Players: split and merge
One mascot per player. Duo splits off a new friend when a player joins and two of them crash back into one when a player leaves; Nucli pops an electron out, or swallows one. Each player can be present (a controller Nucleus can see), assigned (placed on a screen, holding a controller) or active (their game is running). Try the buttons, or click a mascot. Several clicks in a row run faster. Press 1 to 8 on your keyboard to press a button as that player.
- Present Nucleus sees the device. Duo looks around; Nucli's electron is hollow.
- Assigned Placed on a screen. Duo holds the player's device, ready; the electron fills in.
- Active Their game is running. The Duos hop to a shared beat; the electron speeds up with a trail. Everyone active is a party, and even Nucli gets excited.
- Device The small icon next to each player: controller, keyboard and mouse, keyboard only, or mouse only. Duo holds it and Nucli's electron takes its shape; a new device pops in with a jiggle.
- Input When a player presses something, their Duo hops and their device and electron jiggle, like a haptic tap.
Quality pass
Every animation, with what I did to it. The lessons: long holds then a snap, hit stop on the big hit (impact frames tried, then dropped: they read as glitches), Duo bouncy (a bouncy ball), Nucli firm (a basketball), follow-through, and setup, pause, payoff. Everything as it was before is kept in History at the end, all animations and emoji included.
Duo's animations
For the app, the Hub, the website and Discord.
Nucli's animations
For the workbench, the VS Code extension and the CLI.
Loader experiments
Little Duos as loaders. Five tries, with my verdict on each; the winners are used below.
Earlier versions of each loader are folded away in its card. Everything dropped, and every earlier version of this page: History, at the end.
In the product
Loaders and states, ready to drop in. Each is one small SVG with CSS; nothing moves when the device asks for less motion.
Player setup
The player setup example is now its own page: App concept: player setup.
Discord emoji
Static and animated, at Discord's sizes: 22 px in a message, 48 px on their own, 16 px as reactions.
Small and in one colour
Next steps
- Pitch Duo to the Nucleus Co-op maintainers (Discord). Nucli can start in the workbench right away.
- Once they're picked: export the emoji (128 × 128 PNG and GIF, under 256 KB each) and a sticker sheet.
- Workbench: Nucli in the empty Check tab, Test all (progress ring), fixes (toast), failed loads; Duo for Hub loading and the 404 page. Off in the alpha 8 look and when the device asks for less motion.
Historic branding, theming, styles, mascots and animations
Everything tried and dropped, and why, with every earlier version of this sheet. Steps 1 and 2 (the first six sketches, then the palettes) are only in the artifact's version history.
What I dropped, and why
Cushy (the couch) and Pip & Pod (the twins) were cute, but neither reads at 16 px, and the twins double every drawing. Nab (the bug-catcher) says "you made bugs", which is the wrong tone for beginners. Padd (the gamepad) is nearly a generic controller icon and repeats Duo's idea. The palette switcher is gone too: the logo's own colours work everywhere, so each mascot gets exactly one look.
The sheet, step by step
Each is the whole page as it was, animations and all. It loads when you open it.
3. Six concepts, palettes and emoji Three ideas for splitscreen.me (Duo the split window, Cushy the couch, Pip & Pod the twins) and three for the tools (Nucli the atom, Nab the bug-catcher, Padd the gamepad), a palette switcher (splitscreen.me, v3.splitscreen.me, the Nucleus Co-op app, player colours) and the first emoji.
Open it on its own page
4. Two mascots, an animation library Duo and Nucli only, one look each: the first library, loaders, product states and emoji.
Open it on its own page
6. Physics rig, amber Nucli Split and merge for 1 to 8 players with gravity and springs; Nucli in amber with drawn shading.
Open it on its own page
7. Nucli as the Nucleus Co-op logo A red nucleus and green ribbons. Dropped: overfitted to one app.
Open it on its own page
8. Violet Nucli, hook and ribbons His own thing: woven orbits, electron colours, a ProtoInput hook, device-shaped electrons.
Open it on its own page
9. Devices, white eyes, personalities Electrons match the input device; Nucli attentive, Duo the fun one; Duos in sync.
Open it on its own page
10. Nucli with one ring and hands One body, one tilted ring, the hook as an antenna; the first loader experiments. Dropped: a toy.
Open it on its own page
11. Nucli: proton cluster and loupe A jeweller's loupe and a cluster of protons. Dropped: making too much of himself.
Open it on its own page
12. Quiet Nucli, the hula hoop One calm nucleus, faint orbits, comet-trail electrons, shy.
Open it on its own page
13. 3D turns, calm joins Duo turns as a ball; the carousel in depth; controllers drawn as gamepads.
Open it on its own page
Before the quality pass The library and loaders just before the audit, between steps 13 and 14.
Open it on its own page
14. Quality pass and impact frames The audit of every animation; impact frames (dropped later: they read as glitches).
Open it on its own page
15. Loaders round 2, a setup screen Ball bounce, two kaleidoscopes, hop-in with a check, the first working player setup.
Open it on its own page
16. App concept: player setup The setup screen in its own tab; a real controller works through the Gamepad API.
Open it on its own page
A concept for player setup in a future Nucleus Co-op. Press a button on a device to join (a real controller works: plug one in and press A), or click Join on a device. The screen splits for each new player and merges when one leaves. Move devices by dragging them, or pick one up (Enter or A) and put it somewhere else. Everything works with a mouse, touch, the keyboard (arrows, Enter, Esc, Delete) or a controller (D-pad or stick, A, B, X, Start).
Nucleus Co-opLeft 4 Dead 2 · Players