Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="Matt Thomason" data-source="post: 8908292" data-attributes="member: 6777331">And you know, there's a commonly-used trick to get around the viral nature of Open Source licensing that applies here.Hypothetical: I'm writing a VTT, but want to include some functionality from an open-source library that requires anything using it also be open-sourced.  I do not wish to open-source my VTT.So:1) I release my completely closed VTT without said functionality.2) I create a separate program that performs that functionality with the open-source library, and open-source that.3) I build interfaces between my VTT and my open-source program allowing the former to communicate with the latter, e.g. via Named Pipes.I see a potential way to achieve that with the 1.2 license's restrictions on VTTs, too.1) Release the bells-and-whistles VTT, but it doesn't have 6e rules.  Include a system within the VTT to read a text file of rules.  Probably something like XML.2) Release, under the OGL, your new static text file of rules and game data.  This file does nothing by itself, it isn't "dynamic", it doesn't display graphics, it doesn't do anything.  It's just a text file that translates the SRD language from human-readable into machine-readable.3) End users combine the perfectly legal 1) with the perfectly legal 2).Obviously, do NOT do this without getting proper legal advice to ensure it is 100% legal first.And, disclaimer, I absolutely do not support or intend this to be used in an illegal manner, only to legally comply with WotCs OGL 1.2 and the new VTT policy.Also, this is very similar to the idea of creating a system-neutral sourcebook for your world that requires no license whatsoever, then a 5e supplement with stats+rules under the OGL, a Savage Worlds supplement under their license, and so on.</blockquote>

Verification