Mark CMG
Creative Mountain Games
You mean except Star Wars?
Yes, as I have posted thus far, SW was mentioned as a jumping off point for the entire idea. Did you read my previous posts or come in mid-conversation? Maybe you're joining in without all the information and that's why this is confusing you.
Which would be benefitable to the IP holder, since that means a better deal and more controll for him.
That's one way of looking at it. Is control what you want when you get into a licensing deal with someone because you don't have expertise in a market sector in which they are absolutely the top dog and seemingly have a sense of how to properly handle valuable IP like SW?
It's not as if the D&D enginge would really increase sales of a HP RPG much beyond what it would sell with any other engine.
You don't think so, the SW folks do think so. I guess you and the folks in charge of the SW IP will have to agree to disagree. And to repeat, again, one more time, we're discussing a game engine by the same people as those who make D&D not the D&D engine per se. In further exchanges, please proceed with that understanding.
An own engine also has the advantage of being able to be customized to the IP. With the D20 versions it was a bitter pill to swallow because the D20 market was so big that using an unsuited enginge was still more feasible at the end. And even then many D20 version enventually included so many alterations as to be hardly recognizable.
d20 was a "thick" underlying engine. I was suggesting something much thinner, some core mechanics and some terminology that can crossover, something designed specifically to work with multiple IP overlays (the design idea behind the d20 system was originally that those adopting it would be specifically supporting D&D and driving D&D core book sales). You may have missed the previous post(s) where I suggested they design a specific engine for this purpose, a thin one. Could you, perhaps, go back and check out those posts to avoid raising issues already covered?
Last edited: