Blockland Player Database

The Blockland Player Database is a central repository of Blockland user data drawn from community archiving efforts like Greek2Me’s statistics, DaProgs’ BLID lookup, Blockland Glass, and other collections that had been gathering player history on their own. The goal was simple but ambitious: pull those fragmented sources together into one place the community could actually use.

I built it as a platform to collect and preserve historical username data for Blockland, a brick-building game with a long-running modding scene. What made the project interesting was not just the database itself, but how the data got there. I had no real infrastructure for harvesting player records at the start, so I had to get creative. That meant working closely with popular server hosts who already sat on valuable data, collaborating with modders who had built their own collection systems, and in some cases scraping public sources or building direct integrations to pipe information from their platforms into mine.

Over time, those efforts compounded. BLDB became the largest consolidated dataset in the community’s history, and it still serves mainly as a portfolio piece: proof that resourceful engineering and community relationships can stand in for a big budget when the problem is messy and distributed.

The site exposes an API so developers can query the database from gamemodes, tools, and other applications. Other services in the ecosystem have leaned on it too; BLHost’s player search, for example, hosts its own records and falls back to BLDB when a player is not found locally.

Work

• Database design and long-term data aggregation
• Custom integrations with community platforms and server hosts
• Public API for querying historical player data
• Web application for search, lookup, and exploration

Context

Blockland’s player history was never stored in one official place. It lived across Slayer-powered stats gamemodes, orbsRTB, Glass services, and the ad hoc history logs from admin tools that people ran for their own servers. BLDB treated that fragmentation as the core problem and spent years turning it into a single, queryable archive.