Didn't see a forum specifically for discussing the licenses surrounding the logo and/or OGL, so I'm putting this here.
Have a couple of projects in the works. The first is simply a rewrite of an adventure I already have for sale under OGL. Putting out a Pathfinder compatible version of it, and I don't see an issue there.
The second project, however, is an alternate rules system for magic for d20/OGL and I'd like to make it compatible for use with Pathfinder. That said, it's a fairly dramatic revamp of how magic and spellcasting work, taking a much darker and more dangerous slant on things.
Use of the compatibility logos requires that the products maintain compatiblity with Pathfinder. My question is, how far outside of the default ruleset can you get and still be considered compatible? My system would work with Pathfinder, but all of the rules regarding how spell casting works (memorization, spells per day, spells that can be cast, classes that can cast) are altered.
You can drop these new rules into the game rather seamlessly, but I want to know whether this is still considered a product that is "compatibility" for purposes of the license.
Thoughts?
Chief Technical Officer
|
...My question is, how far outside of the default ruleset can you get and still be considered compatible? My system would work with Pathfinder, but all of the rules regarding how spell casting works (memorization, spells per day, spells that can be cast, classes that can cast) are altered.
You can drop these new rules into the game rather seamlessly, but I want to know whether this is still considered a product that is "compatibility" for purposes of the license.
There's definitely not a distinct line between "compatible" and "not." I don't think it's even possible to discuss whether a specific change would make something incompatible, as the amount that's changed also comes into play. For example, you might be able to change A, B, or C, and still have a compatible product, but if you changed A, B, *and* C, you might not have Pathfinder anymore
For that matter, even the way you present it factors in—if you made a whole big new rules component, but presented it as an option that works alongside the exiting system, that would make it more compatible than if you said that your system changed everything for everyone.
In general, I'd ask yourself this: If an average Pathfinder RPG player picks up your product, will he say it doesn't feel like Pathfinder anymore? Or if he picks up a Pathfinder RPG-compatible adventure, would he have a lot of difficulties using it in conjunction with your product?
In general, I'd ask yourself this: If an average Pathfinder RPG player picks up your product, will he say it doesn't feel like Pathfinder anymore? Or if he picks up a Pathfinder RPG-compatible adventure, would he have a lot of difficulties using it in conjunction with your product?
Thanks, Vic. Those are excellent points, and you've brought it home in this final paragraph. It gives me something to think about. It will certainly feel like Pathfinder, and by and large you could pick up a Pathfinder RPG-compatible product and use it with little difficulty, but things like the spells available to monsters and NPCs, and how they are cast, would be different and have to be adjusted on the fly or taken into consideration ahead of time.
Good food for thought there, and I appreciate the repy.
|
Chief Technical Officer
|
...by and large you could pick up a Pathfinder RPG-compatible product and use it with little difficulty, but things like the spells available to monsters and NPCs, and how they are cast, would be different and have to be adjusted on the fly or taken into consideration ahead of time.
Good food for thought there, and I appreciate the repy.
I'd also say that putting effort into a "how do i use this with other stuff" section would add to compatibility as well.