PixelWar: Sovereign Canvas
Inspiration
What if every pixel mattered?
We were inspired by collaborative pixel worlds like Reddit's r/place and classic strategy games such as Civilization, Age of Empires, and Clash of Clans. Instead of creating another multiplayer game with isolated matches, we wanted to build a persistent living world where every player permanently shapes history.
At the same time, we wanted to showcase how modern cloud architecture can power massive real-time experiences. PixelWar demonstrates that a scalable backend and efficient database design are just as important as engaging gameplay.
What it does
PixelWar: Sovereign Canvas is a persistent real-time multiplayer strategy game where every player shares one giant pixel world.
Players can:
- ๐ฐ Claim and expand territory
- โ๏ธ Attack rival civilizations
- ๐ค Form alliances
- ๐ฐ Trade resources
- ๐ Research new technologies
- ๐ฏ Complete missions
- ๐ Explore a continuously evolving world
Every action immediately updates the shared world, allowing players to influence the same persistent map in real time.
The game also features AI-controlled civilizations that expand, defend their territory, and react to changing conditions, making the world feel alive even when player activity is low.
How we built it
We designed PixelWar as a modern full-stack application focused on scalability and real-time synchronization.
Frontend
- Next.js 15
- React 19
- TypeScript
- Tailwind CSS
- shadcn/ui
- Framer Motion
- PixiJS for rendering the world
- Zustand for state management
Backend
- Express.js
- Node.js
- REST APIs
- WebSockets for real-time updates
Database
- DynamoDB Local
- Single-table design
- Chunk-based world partitioning
- Optimized access patterns
- GSIs for efficient queries
Core Systems
- Territory management
- Resource economy
- Combat engine
- Technology tree
- Mission system
- Alliance system
- Marketplace
- AI civilization engine
- Demo mode
- Live notifications
The project follows a modular architecture with separate controllers, services, models, middleware, and WebSocket layers to keep the codebase maintainable and extensible.
Challenges we ran into
Building a real-time persistent multiplayer game presented several interesting engineering challenges.
Some of the biggest challenges included:
- Designing a scalable world model without scanning the entire map
- Keeping real-time updates synchronized across connected players
- Modeling a large pixel world efficiently using DynamoDB
- Connecting multiple gameplay systems such as combat, research, missions, and trading without tightly coupling them
- Creating believable AI civilizations while keeping the implementation lightweight enough for a hackathon
- Balancing gameplay mechanics within limited development time
Every challenge pushed us to simplify where necessary while keeping the architecture ready for future expansion.
Accomplishments that we're proud of
We're especially proud of:
- Building a persistent shared multiplayer world
- Implementing a scalable DynamoDB single-table design
- Creating interconnected gameplay systems instead of isolated features
- Designing a clean, modular architecture that can grow beyond the hackathon
- Implementing real-time gameplay with WebSockets
- Creating a polished pixel-art inspired interface
- Building a functional demo mode that showcases the game's core mechanics instantly
Most importantly, PixelWar is more than a collection of screensโit is a fully interactive prototype with real gameplay systems working together.
What we learned
This project taught us that building real-time multiplayer applications is far more than simply rendering graphics.
We learned about:
- Event-driven architectures
- Real-time synchronization
- WebSocket communication
- DynamoDB access-pattern-first database design
- Modular backend architecture
- State management for interactive applications
- Designing gameplay systems that remain maintainable as complexity grows
Perhaps the biggest lesson was that successful multiplayer systems depend on thoughtful architecture just as much as good gameplay.
What's next for PixelWar: Sovereign Canvas
This hackathon MVP is only the beginning.
Our roadmap includes:
- Massive persistent online worlds
- Fully autonomous AI civilizations with diplomacy
- Dynamic weather and natural disasters
- Territory influence and political systems
- Fog of war
- World timeline replay
- Seasonal events
- Guild wars and tournaments
- Advanced resource economy
- Cross-platform multiplayer
- Cloud deployment on AWS
- Large-scale performance optimization
- Mobile support
- Community-created maps and events
Our long-term vision is to transform PixelWar into a living online strategy platform where every player's actions permanently shape a shared digital world.
Built With
- aws-sdk-v3
- bcrypt
- dynamodb-local
- express-rate-limit
- express.js
- framer-motion
- helmet
- jest
- jwt
- next.js-15
- node.js
- pixijs
- react-19
- rest-api
- shadcn/ui
- supertest
- tailwind-css
- tanstack-query
- typescript
- vercel
- websockets
- zod
- zustand
Log in or sign up for Devpost to join the conversation.