GameShipKit：打造 63 款免費瀏覽器遊戲開發工具的心得

A year ago I could not write code. I did not even know what a game engine was.
Today I run GameShipKit, a set of 63 small browser tools for game developers.
I built all of it by describing what I wanted to an AI and testing the result. Here is what that taught me.

Why small tools

Every time I made a game I hit the same small jobs.
Turn a drawing into a sprite. Try a hit-stop value. Make a fire effect.
Each job is too small for a big program, but it still eats an hour.
So I started making one tool for each job.

Four tools I use the most

1. Image to Pixel Art

A plain resize turns art into blurry mush. This tool keeps the strongest colour of each pixel instead.

1. Drop a drawing, a 3D render or a photo.
2. Pick the width, like 32 or 64 pixels.
3. Lower the colour count and keep "Remove stray single pixels" on.
4. Download the PNG.

Try Image to Pixel Art

2. Hit Feel Designer

Hit a test dummy and tune what makes a hit feel good.

1. Start from a preset like Arcade or Heavy brawler.
2. Press J, K and L for light, heavy and critical hits.
3. Move the "Juice amount" slider until it feels right.
4. Turn "Juice" off to compare. The difference is huge.
5. Download the settings as JSON and the hit sounds as WAV.

Try Hit Feel Designer

3. Particle Effect Builder

Fire, smoke, explosions, sparks, coins and more, live in the browser.

1. Pick a preset.
2. Change the particle shape, count and colours with sliders.
3. Export a looping sprite sheet that works in any engine.

Try Particle Effect Builder

4. 2D Character Rigging

Turn one character image into bone animations.

1. Drop one character image.
2. The tool places a skeleton. Drag the joints to fix them.
3. Pick a motion like idle, walk, attack or hurt.
4. Export a sprite sheet or a GIF.

Try 2D Character Rigging

Rule 1: everything runs in the browser

No sign-up and no upload. The files stay on your own computer.
This made the tools simple to build and simple to trust.
It also means there is no server cost, so the free tools can stay free.

Rule 2: test the export in the real engine

Many tools export straight to Godot 4 or Unity.
At first I only checked that the file looked right. That was a mistake.
When I finally opened every export in Godot 4.7 and Unity 6.3, I found real bugs:

• A generated Unity shader failed to compile. A loop variable had the same name as the shader input.
• Inventory icons were cut from the wrong place. The importer read the scaled texture size instead of the source size.
• A wave spawner spawned zero enemies. The prefab list was built too early and came up empty.

None of these showed up in the browser. All of them would have broken someone's project.
Now no export ships until it runs inside the engine.

Rule 3: AI writes the code, I check the behavior

The AI is fast, but it is confident even when it is wrong.
My job became writing clear requests and checking what actually happens.
I cannot read every line, so I test every feature by using it.

What is next

I am adding tools that people ask for.
If there is a small game dev job that keeps eating your time, tell me in the comments.
I might build it next.

https://gameshipkit.com