I run a tiny private multiplayer alpha built on Minecraft Java. Before asking more people to test it, I audited the application page because several visitors reached the form but nobody submitted it. The audit found two avoidable funnel failures.

First, the post-submission referral panel had a native hidden attribute, but an author .panel { display: grid; } rule still made it visible. Visitors could see "Application received" before doing anything. I had assumed the attribute would always win. The fix was an explicit [data-alpha-referral-panel][hidden] { display: none !important; } rule plus a browser test that checks both the DOM property and computed display value.

Second, the mobile form started 1,098 px from the top because the pitch and a large proof image came first. I shortened the mobile introduction, kept the real world image for desktop and link previews, and moved the form start to 481 px. I also changed free-text availability to four clear choices and detect timezone silently, while keeping the founder-vision answer and CAPTCHA.

It is too early to claim a conversion win: the verified result is still zero new applications since the fix. My next question is what minimal funnel events other developers would measure here without adding invasive analytics. At present I can distinguish a page request, full asset/API load, CAPTCHA load, and a real submitted application from server logs.

The secondary playtest ask, for anyone who also owns Minecraft Java: Neviroth is testing whether three founding players having concrete authority—founding kingdoms, naming places, building landmarks, and changing progression or economy—creates better long-term investment than treating them as ordinary bug reporters. Alpha access is free, unstable by definition, and every application is reviewed manually.

Live page and founder application: https://neviroth.net/community/alpha/apply?src=programming_dev_gamedev&campaign=alpha-social&ref=ed5372cdb30c&content=alpha-funnel-postmortem

I am building Neviroth, an independently run persistent multiplayer project built on Minecraft Java rather than a standalone game. I am at the point where I need to test a design choice, not just server stability: should early players be ordinary testers, or should they have enough authority to create the world future players inherit?

The current approach is the second one. Up to three founding testers can establish the first kingdoms, name places, build roads and landmarks, create traditions and rivalries, and give feedback that can directly change claims, economy, progression, events, and community rules. I want their influence to be concrete and persistent instead of the vague promise that players can 'shape development.'

The playtest needs to answer three questions: does founding a kingdom create a compelling long-term goal, which progression or economy decisions need player input first, and does the one-minute application set honest expectations for a small alpha? The world is live now. Players need to own Minecraft Java; access is free, every application is reviewed manually, and testers should expect bugs, balance changes, restarts or rollbacks.

I would value developer feedback on that founder model, and I am also looking for the three players who want to test it from inside the world.

Actual alpha-world map and founder application: https://neviroth.net/community/alpha/apply?src=lemmy_indiegamedev&campaign=alpha-social&ref=53b47278ef52&content=founder-influence-playtest