Exclusive Races/Classes in Dragon: Why the Angst?

[slwoyach]

I disagree about such a blatantly broad (and in my opinion demonstrably incorrect) statement, but mostly I'm laughing.. largely because my 1e games included the cavalier, the ninja and the anti-paladin.

The anti-paladin was the only one of those classes that was a Dragon class, and it wasn't unbalanced at all. The OA ninja also wasn't unbalanced, I could see someone wanting to play one even though I wouldn't. The cavalier doesn't count because it came from the book that must not be named.

 

[wayne62682]

On the D&DI for Mac stuff - I have both a Mac and a PC since I'm a programmer so I'm good, but as I see it the problem a lot of Mac users have is that WotC took the lazy way out and gave the finger to anyone not using Windows; I realize that Windows has the market share but anyone with common sense would have figured that for an application that's not limited in use, using .NET 3.5 and WPF is not a good idea - if they were not a game company and making software that requires Windows due to some feature (e.g. it's an add-on to software that's already Windows only, such as QuickBooks) then it's understandable, but they should have either: A) Not used WPF, so the CB could run via Mono, B) Used Java or something that's cross-platform, or C) Make the whole damn thing web based so it's platform-neutral.

Instead, they chose the lazy choice of using "kewl" features of .NET that aren't necessary (a WPF interface wasn't needed) and therefore require Windows as a choice - now I am a .NET programmer myself so I understand if they had in-house talent who already knew .NET, but again there was no need to use Windows-specific flashy features like WPF. If they provided and allowed for a way to access the information that Character Builder does, then it wouldn't be that bad since somebody else could make a Java version of it, but we all know that they would sue anyone who tried that.

 

[Mustrum_Ridcully]

On the D&DI for Mac stuff - I have both a Mac and a PC since I'm a programmer so I'm good, but as I see it the problem a lot of Mac users have is that WotC took the lazy way out and gave the finger to anyone not using Windows; I realize that Windows has the market share but anyone with common sense would have figured that for an application that's not limited in use, using .NET 3.5 and WPF is not a good idea - if they were not a game company and making software that requires Windows due to some feature (e.g. it's an add-on to software that's already Windows only, such as QuickBooks) then it's understandable, but they should have either: A) Not used WPF, so the CB could run via Mono, B) Used Java or something that's cross-platform, or C) Make the whole damn thing web based so it's platform-neutral.

Instead, they chose the lazy choice of using "kewl" features of .NET that aren't necessary (a WPF interface wasn't needed) and therefore require Windows as a choice - now I am a .NET programmer myself so I understand if they had in-house talent who already knew .NET, but again there was no need to use Windows-specific flashy features like WPF. If they provided and allowed for a way to access the information that Character Builder does, then it wouldn't be that bad since somebody else could make a Java version of it, but we all know that they would sue anyone who tried that.

Pah, the Mono developers just need to get off their lazy asses and implement WPF on Mono. I mean, they are porting Silverlight, so why not WPF?

Mustrum "Not really believing that the mono developers are lazy, but really wished they or M$ would do that" Ridcully