As the subject says, do I need a specific license... or am I good under OGL?
I'm not 100% on the license, as long as you don't use any specific names like Eoxian Boneship you should be good under OGL.
I'm also a software engineer...if you need a hand I'd be willing to lend what help I can. As long as it's not Java.
I'm not 100% on the license, as long as you don't use any specific names like Eoxian Boneship you should be good under OGL.
I'm also a software engineer...if you need a hand I'd be willing to lend what help I can. As long as it's not Java.
I'm coding in C# or at least what I know of it. I've done C++ and Python as well before, but I am most familiar with C#. In hindsight, I probably should have used an SQLite database for storing the tables, but I'm already into the thrusters... so no turning back now. =)
Also, I'm just using the mechanics, so no IP infringement.
You should be good then. You might want to put the compatibility license somewhere in a Help or About menu.
Java's my only restriction...super hate Java :) PM me if you want any help!
Chief Technical Officer
|
| 3 people marked this as a favorite. |
When it comes to the Pathfinder or Starfinder, our intellectual property generally falls into two categories: Open Game Content (generally game mechanics) and Product Identity (generally setting material, trademarks, artwork, and other non-mechanical stuff).
Anything we've declared as Open Game Content in our products is available for use under the Open Game License; anything we've declared as Product Identity is not available under the OGL. In most of our products, you'll find the statements of OGC and PI on the title or credits page at the front of the book. Note that these statements occasionally vary from product to product, so you'll need to check the individual statements in each product you wish to draw from.
If you are a noncommercial user, you may be able to use some of our PI by way of our Community Use Policy, which you can find at http://paizo.com/paizo/about/communityuse. If you are a commercial user, our PI is not available for your use without a specific license.
To use Open Game Content in your own projects, you need to use the OGL, which you can find in any OGL product. The OGL itself tells you how to use it. Please note that the OGL is Wizards of the Coast's license, not Paizo's, and so I can't provide any advice about its suitability for your use. You may wish to consider speaking with an intellectual properties legal specialist.
Note that the OGL specifically restricts you from using "any ... trademark or registered trademark clearly identified as Product Identity by the owner of the Product Identity", or from "indicat[ing] compatibility or co-adaptability with any Trademark or Registered Trademark in conjunction with a work containing Open Game Content except as expressly licensed in another, independent Agreement with the owner of such Trademark or Registered Trademark." So to indicate that your OGL project is compatible with the Pathfinder Roleplaying Game, you'll need to follow our free Pathfinder RPG Compatibility License, which you can find at http://paizo.com/pathfinderRPG/compatibility; the equivalent license for the Starfinder RPG is at http://paizo.com/starfinder/compatibility. Note that these Compatibility Licenses are applicable only to books, electronic books, and freely available websites. You can still use Open Game Content in a OGL product that's not a book, ebook, or free website, but you can't say it's compatible with the Pathfinder RPG or the Starfinder RPG or use trademarks like Pathfinder, Starfinder, or Paizo in any way; you may, however, use the non-trademarked terms “PFRPG” or “SFRPG."
Um, is there any way for me to get that once you finish, because it sounds awesome. ;-)
Thanks Vic!!
And yes, Cactus there will be!
Well, I'm no expert on licenses... but as a potential user, I would like to suggest keeping in mind that flexibility with the program would be good. That is, it should be coded in a way that would allow expansions later, from new types of ships to new components, attributes, crew roles, and so on.
And, similarly, it should probably be flexible enough to add extra licenses and references if you need to cite additional products... rather than, y'know, a static component you couldn't make bigger if you had to. Programming can be weird sometimes, so I think it's probably best to keep that in mind.