In Brief:
- Pixels intends to publish the source code behind its browser-based game client, opening the door to outside contributions while the studio keeps the final say on approvals.
- Feature proposals will be decided by player votes, but voting weight will depend on token and NFT holdings instead of a one-player-one-vote system.
- The backend release still to come is expected to reshape gameplay mechanics and enable private instances.
Pixels prepares for open-source release
Pixels plans to open-source its game client this week, seeking broader community involvement while the studio holds onto oversight. The plan was confirmed on social media by founder Luke Barwikowski, who noted that the server code would arrive at a later point.
“The @pixels_online frontend will soon be open-sourced (this week?),” Barwikowski wrote. While users will get input on new features, the governance approach still needs more experimentation. To keep every change under human review, the studio intends to cap how many contributions are merged each month.
Under this model, players cannot directly alter the live game on their own. Developers will instead evaluate proposals from the community, checking for security and compatibility before anything is folded into the official codebase.
Voting power and governance
Three types of economic participation will set voting weight: PIXEL tokens held in wallets, land NFTs, and PIXEL staked via the game’s contract. An account sitting on 25,000 PIXEL, for instance, would carry 25 units of voting power — a rate of one vote for every 1,000 unstaked PIXEL.
Notably, Pixels’ governance leans toward asset ownership rather than a purely democratic vote. Those holding tokens, land, or staked positions will shape the development roadmap more heavily than players who own none of these assets.
Open-source features
According to Barwikowski, the released repository will contain meaningful parts of the game — including character behavior and event handling — rather than just a bare interface. That gives external developers room to improve the experience, whether by refining controls or reworking inventory systems.
Even so, a modified client won’t touch the official economy or game state, since server-side validation blocks any attempt to grant resources or skip progression illegitimately.
Backend implications
The backend release is set to carry far more weight. That code could touch player inventories, crafting, and quests, raising the prospect of private server instances or game forks. Sensitive pieces such as player data and anti-cheat systems, however, will stay protected.
As the studio moves toward a more open development style, the exact mechanics of this governance experiment remain a work in progress. Much will come down to the licensing, how proposals are handled, and whether community votes end up advisory or binding.