From 961f351ca10bf66c8c764766c9d5d87ed62c551a Mon Sep 17 00:00:00 2001 From: Andrew <72449774+andrewkydev@users.noreply.github.com> Date: Mon, 9 Feb 2026 00:09:27 +0300 Subject: [PATCH] Delete README.md --- README.md | 38 -------------------------------------- 1 file changed, 38 deletions(-) delete mode 100644 README.md diff --git a/README.md b/README.md deleted file mode 100644 index c3392e2..0000000 --- a/README.md +++ /dev/null @@ -1,38 +0,0 @@ -# VexoraDevelopment - -VexoraDevelopment builds high-performance Minecraft: Bedrock server tooling and game infrastructure. - -## What we build -- **Core engine forks** for Bedrock server development. -- **Practice platform modules** (`app`, `platform`, `domain`, `storage`) with clean boundaries. -- **Gameplay systems**: Hub, FFA, Duels, Training, ranks, cosmetics, statistics. -- **Ops tooling**: profiling, diagnostics, structured logging, runtime status commands. - -## Architecture -- `app` - bootstrapping, runtime wiring, command registration. -- `platform` - adapters, services, UI/forms, game-facing integrations. -- `domain` - business logic, managers, use-cases. -- `storage` - persistence layer and data providers. - -## Engineering principles -- Predictable module boundaries. -- Runtime safety first (deadlock avoidance, transaction discipline, watchdogs). -- Observability by default (debug traces, pprof, status metrics). -- Backward-compatible, incremental delivery. - -## Current focus -- Stabilizing world/teleport transaction flows. -- Finishing duel/training lifecycle phases. -- Expanding ranked systems and moderation tooling. -- Improving hub UX, holograms, and cosmetic integrations. - -## Repositories -- [platform](https://github.com/VexoraDevelopment/platform) -- [domain](https://github.com/VexoraDevelopment/domain) -- [storage](https://github.com/VexoraDevelopment/storage) -- [app](https://github.com/VexoraDevelopment/app) - -## Contributing -We prefer focused PRs with clear scope and reproducible test steps. - -If you want to collaborate on gameplay systems, infra, or engine-level work, open an issue or discussion in the target repository.