I built this speculative mineral cabinet to simulate ultraviolet fluorescence and light-wavelength transitions directly in the browser inside a clean interactive UI.

Users can flip the cabinet lamp between 5500K daylight and 365nm longwave UV to watch dull, grey stones instantly catch fire. The system catalogs seven fictional specimens from Verdigrite to Duskbloom mapping out their host lattices, trace metal activators, emission wavelengths (from 416nm cold violet to 640nm rose pink), and seam localities. If you switch the lamp back to daylight, the borrowed photon energy cuts off immediately, while specimens like Sporewort hold a brief half-second phosphorescent linger before going dark.

Everything runs on the client side using JavaScript, CSS, and HTML5. The stone visuals, wavelength states, and spectrum plots render locally in the browser without relying on heavy external assets or server calls. The page updates the crystal glow, the three step photon excitation breakdown, and the spectral chart in one pass. I even included a control specimen called Nullstone with zero trace activators. So when someone flips on the UV lamp, it stays completely dark and inert instead of faking a glow.

The ragebaiting part was to format and structure out the mineralogy lore and wavelength data so it felt clean and fast. Putting the activator traces, nanometer readings, and locality codes right beside each stone makes it easy to read the numbers while looking at the crystal glow. No distractions. Showing the emission spectrum chart at the bottom also helps visitors see where every specimen sits on the visible band before cutting the lamp.😊

Excellent design visuals. 🔥 👍

$15,000 from one browser game takes 1 to 15 million plays.

I did the math because my first web game, built with Claude Code, went live on CrazyGames today.

Bolt Pit is a Three.js arena shooter. It has earned $0 so far, because CrazyGames keeps ads off during the Basic Launch test, which runs until November 5.

Only games with good numbers get a Full Launch, and that's where the ad revenue share starts.

The formula: Revenue = sessions × ads per session × eCPM ÷ 1,000 × your share

eCPM is what advertisers pay per 1,000 ads. CrazyGames allows at most one midgame ad every 3 minutes. The share isn't public, and reports range from 40% to 60%, so I used 50%. The rest are my assumptions, based on reported ad rates:

Low: 1 ad per session, $2 eCPM = $1 per 1,000 plays. You need 15 million plays. Mid: 2 ads, $5 eCPM = $5 per 1,000 plays. You need 3 million plays. High: 3 ads, $10 eCPM = $15 per 1,000 plays. You need 1 million plays.

One developer reported about €1.20 per 1,000 CrazyGames plays across eight older games. That's the low case, so I plan around the middle at best.

Is 3 million plays realistic?

CrazyGames reported 320 million play sessions a month this October. Poki says it has 100 million players a month. The players exist. Retention and session length decide which line you land on.

That's the bigger reason I'm here. I have Unity games in progress that were meant for the App Store. On the App Store, I'd only find out if people come back after paying for players.

So the new plan is web first, App Store later:

Launch on CrazyGames and Poki, where test players are free.

Tune retention and session length on real data.

If a game becomes a hit on the web, take it to the app stores.

Both portals' exclusivity rules cover only the web, so the app stores stay open.

I'm also skipping CrazyGames' exclusivity bonus. It pays 50% more for two months if your game stays off other web portals, and I want to test on Poki too.

Getting a Claude Code build accepted took six fixes, including a static build, relative paths, no Google Fonts and cutting the size from 20.5 MB to 12.4 MB. One known bug is still live: on landscape phones the start button sits below the fold.

I'll post the real numbers as they come in. Play it here: https://crazygames.com/game/bolt-pit

what was in the 8 MB you cut?