Comments on: Object-Oriented Programming Concepts in Java, Explained with D&D

By: Aliza

Aliza — Thu, 17 Dec 2009 00:05:22 +0000

Um, you picked a bad example — if “vampire” and “humanoid” contain mutually exclusive attributes, then “humanoid” and “undead” have been implemented wrong, since a vampire dragon and a vampire human still retain certain features of their original type.

By: CurtainDog

CurtainDog — Sat, 18 Jul 2009 04:41:13 +0000

@Andy – you’re breaking the rules of the game. There ain’t no such concept as an IElf – that should be your red-light that your model is wrong.

@prgmrgirl – the state pattern is what you want. There’s no reason to treat race as an immutable, think Polymorph* spells. It also makes it trivial to create arbitary combinations of two or more races, and also handles transforms into zombie or lich forms.

@OP – sort of but not quite. Think about the information you put a character sheet. Everything you fill in is a variable. Note that this includes the race of the character, i.e. race is just a field in the character object.

By: What Role Playing Games Can Teach You About Business « Charleen’s Chateau

Tue, 14 Jul 2009 18:02:48 +0000

[...] led to further links like Everything I Know I’ve Learnt (sic) From D&D and Object-Oriented Programming Concepts in Java, Explained with D&D – of which that latter one will prove VERY useful in about a month when I start my Java [...]

By: prgmrgirl

prgmrgirl — Tue, 30 Sep 2008 15:52:11 +0000

That’s just too awesome! Gratz on grabbing onto the concepts! I’m working on creating a character generator as a way of honing my OOD skills. I have to agree with Andy: you’d end up with literally hundreds of classes. I’m currently looking at the Decorator or Factory pattern to see if those might be a better way to go.

By: Anonymous

Anonymous — Wed, 09 Jul 2008 15:04:35 +0000

Not until you realize that Elf should just be a particular instance of the Race class

By: Andy

Andy — Mon, 19 May 2008 19:03:29 +0000

Elf (and Half Elf) should both implement the interface IElf. Drow implements it by inheriting Elf, and Half Elves must implement it themselves. Thus, a sword that works only for an Elf is in fact usable only by an object that implements IElf.

just as Dwarves should implement IDwarf, etc etc. This allows proper extension and flexibility.

it all breaks apart when you realise that you have to create a new class for every combination of templates you’re using.

Java fails, try Lua or Perl.

By: Sandrinnad

Sandrinnad — Mon, 21 Jan 2008 07:11:34 +0000

So by playing with D&D I’m actually refreshing my OOP skills….

Excellent!