Quickie15min
I Designed a Multiplayer Game in Java. My Class Hierarchy Exploded.
This talk uses a Bomberman-style Java game to show why inheritance can break down as features grow. It introduces the Entity Component System (ECS) pattern, demonstrating how composition, entities, components, and systems can replace rigid class hierarchies as game behaviors become more complex.
talk.summaryAiDisclaimer
Christos AvramisProdyna
talkDetail.whenAndWhere
Friday, November 20, 14:40-14:55
Room 1 - Thessaloniki
It started with a simple idea: build a small Bomberman-inspired multiplayer game in Java.
Players move. Walls block them. Bombs explode. Easy.
Then the requirements came. Bombs can be kicked. Walls can be destroyed. Crates can move. Some objects explode, others collide, and suddenly the class hierarchy starts growing in every direction.
So what happens when inheritance stops fitting the problem?
In this fast-paced talk, we'll use this increasingly chaotic game to explore the Entity Component System (ECS) pattern. We'll see how entities, components, and systems replace rigid hierarchies with composition, refactoring our game as new behaviours emerge.
No game-development experience required. Just Java, architecture, and a few questionable inheritance decisions.
Players move. Walls block them. Bombs explode. Easy.
Then the requirements came. Bombs can be kicked. Walls can be destroyed. Crates can move. Some objects explode, others collide, and suddenly the class hierarchy starts growing in every direction.
So what happens when inheritance stops fitting the problem?
In this fast-paced talk, we'll use this increasingly chaotic game to explore the Entity Component System (ECS) pattern. We'll see how entities, components, and systems replace rigid hierarchies with composition, refactoring our game as new behaviours emerge.
No game-development experience required. Just Java, architecture, and a few questionable inheritance decisions.