BrickVerse

BrickVerse is a Meta Game project with a game engine, web platform, and backend services. The public repositories cover the engine and creator experience, the frontend, and the backend behind the platform.

I have contributed in all three repositories. In the frontend, I worked on creator and admin interfaces, world-rating feedback, profiles and social links, forums and Markdown rendering, themes, and browser fixes. In the backend, I worked on the world-rating feedback endpoint, user profiles, response-template tooling, Bimi updates, and theme services. In the game repository, my changes include Forge AI tooling, creator/editor tooling, Windows export and CI fixes, cache/build configuration, and editor actions such as closing a place.

Technology and tooling

• Next.js and TypeScript for the web frontend and creator-facing features.
• TypeScript and Prisma in backend services and database-backed features.
• C# and Godot in the game and creator-tooling codebase.
• GitHub Actions and export scripts for build and release work.

Engineering challenges

Keeping several product surfaces coherent

The project spans a game/editor application, a web frontend, and backend services. A feature such as world feedback or creator tooling has to line up across the UI, API, database, and game workflow. Working across the repositories makes those connections hard to ignore.

Building support tooling that operators can actually use

Admin and support workflows need more than a form. The person handling an issue needs clear state, useful failure messages, reusable response templates, and enough context to act. My frontend and backend work in this area has focused on those details.

Keeping creator tooling shippable on multiple platforms

The game repository includes creator/editor tooling and platform-specific build scripts. Windows export settings, CI changes, and editor work all touch the release path, so even a small build change can have wider effects.

Links

• Game engine repository