Blog

Live World Memory explained: why AI worlds that remember feel alive — one world, many live apps, one shared state, from Small Phone to maps to roleplay.

A five-layer framework for AI interactive entertainment — inference, generation, world materials, creation protocols, distribution — and why L3/L4 are the missing middle where durable value is created.

From the open-source oh-story-dsh plugin to Neta Studio's living worlds: two takes on the AI creation workstation for novels, dramas, and AI games.

My 2026 take on Bill Gates' Open Letter to Hobbyists. Hint: In the age of AI, a true hobbyist does more than prompt.

China's AI entertainment market runs about a year ahead on go-to-market. Four categories — short drama, mini-games, companionship, interactive worlds — and what each teaches us about engagement and unit economics.

Chris Dixon said come for the tool, stay for the network. AI just solved the tool. This is about what's left to solve — and why the feed might not be the shape the network takes next.

A comprehensive guide to writing effective prompts for Neta Lumina, featuring examples and best practices.

A high-quality anime-style text-to-image model trained by Neta.art Lab on the basis of Lumina2. This technical report covers our training strategy, dataset management, and open-source contributions.

Neta Art XL V2.0 introduces enhanced dynamics, improved anatomy, and the ability to create epic scenes with greater detail and storytelling potential.

Older JRPGs were built around a rhythm — a town, a road, a dungeon, a save point — and that rhythm survives where modern pacing does not. A craft essay on encounter budgets, menu latency and the four-beat loop, with what to copy when you build your own.

Grouping, scoring, the projector, the kid who answers everything, the class that finishes early and the lesson that runs long — eight real questions about running a mini-game in class, answered with the rules that hold up on a Monday morning.

Combat is the default filler of every first RPG. Remove it and the world, the characters and the quests have to carry the game — which is the part that actually makes an RPG good.

A fixed palette, an indexed ramp and a per-sprite palette solve different problems. How to choose, what each one costs you, and why a shared palette across a whole cast makes a game look deliberate.

Automatic photo-to-pixel conversion produces mud for four predictable reasons — noise in, palette out, no grid discipline, and anti-aliased edges. Here is how to fix each one before you convert.

Sixteen by sixteen is the smallest size that still reads as a character. Here are the constraints it imposes, the palette discipline it forces, and the four things you should stop trying to draw at that size.

The real division of labour when a written sentence becomes a playable browser game — what the generator chooses, which four decisions stay yours, and the failure modes that look like the tool's fault but are not.

Why one board a day beats unlimited rounds, what a streak does to a habit, and the twelve variants that changed one rule of the Wordle loop to make a different game.

The whole method for a classroom Jeopardy board — how to pick categories that scale, how to word a clue a full room can read, the value ladder, and the scoring rule you must announce before anyone buzzes.

An honest read on text-to-3D: what a single sentence reliably produces today, the four things it still cannot do, and the workflow where generated geometry genuinely pays off.

Why a .glb ballooned in the first place, and the compression levers to fix it — geometry compression, texture resizing, unused-data removal — in the order that does the least damage.

Quad remeshing for game-ready models — when to remesh at all, the paid remesher vs the free alternative, the workflow order that does not force a redo, and the checkpoints before you unwrap.

The pipeline that takes a written character description and produces a reusable low-poly NPC component — what the generator decides, what you still decide, and how to place it in a walkable world.

A quest marker tells you where to go; an NPC tells you why. What changes in an open world when characters replace icons — and the cheap ways to get there.

How AI NPCs decide what to do — the classic decision layers (state machines, behaviour trees, GOAP), where an LLM genuinely fits, and what an NPC can and cannot remember.

Sixteen neighbours do not mean sixteen tiles. Where the 47-tile blob set comes from, how the 4-bit mask works, and the four bits everyone forgets to set.

Grass is the first thing that makes a low poly scene look cheap or alive. Ten concrete techniques — textures, planes, clumps, cards and colour — with the trade-offs of each.

The 2:1 ratio fixes a lot, and it trips up three things every time: character height, prop footprint, and the height of a stack. How to keep an isometric scene in proportion.

Both are 'blocky 3D' and they are nothing alike to build. How voxels and low poly differ in geometry, workflow, cost and feel — and a straight recommendation per genre.

The tile grid is fine; the read is wrong. The six reasons a hand-built map looks like decals dropped on a floor, and the cheap changes that make it read as terrain.

The pipeline from a raw tileset to a level you can actually walk: cell grid, layers, collision, depth sorting and export — and the four hand-offs where projects break.

A sprite sheet is the same frames as an animated GIF, packed into space instead of time. What the grid, the cell size, the origin and the JSON atlas each decide — and where each one goes wrong.

Slice-by-grid, import strips, origin at the feet. The import step is where a correct sheet becomes wrong — the settings that matter in Unity, Godot and GameMaker, and the three errors that cause all of them.

The hard part of sprite work is not the first character, it is the seventh. Why a cast drifts, what a palette lock actually locks, and the checks that catch a sprite that does not belong.

Every GIF sprite you have keyed out has a halo for a reason. One-bit alpha, palette quantisation, matte colours and the four places a transparent background is lost before your engine ever sees it.

How many frames a walk cycle actually needs, why contact and passing poses carry the whole animation, and why a directional sheet indexes down, left, right, up — not clockwise.

ImageMagick, TexturePacker and a browser canvas each solve the same problem from a different direction. When a shell one-liner is right, when it costs you an afternoon, and where the in-browser tools actually win.

Free is four different promises. A practical guide to finding free sprite assets — and to reading the licence clause that decides whether you can ship them in a commercial game.

VRChat avatars want a single-row frame strip, not a grid. How to pack a GIF into a flipbook texture: strip width, power-of-two sizing, alpha that survives the shader, and loop pacing.