talmar
First Post
To answer the questions at hand as directly as I can:
quote:
--------------------------------------------------------------------------------
1. Will they support this product if WOTC pulls out? Actually, Scot said something that probably sheds some light on this. He said somewhere that as a company, they have to spend their time on things that bring in the cash and can't afford to partake in a Labour of Love, despite their personal feelings on the subject, so I imagine that this is a no.
--------------------------------------------------------------------------------
If WotC pulls out, Fluid will continue to support eTools. I love the product and want Fluid to keep adding to it as best as possible.
But as a qualifier to that, Fluid could not build the eTools version of Sword and Fist without WotC’s agreement.
In this case, I would first go to WotC and try to get their permission to do so. If they truly had no more interest in supporting 3E thru software, I don't think they would reasonably withhold their permission. That is to say, I don’t think they are the evil corporate beastie that we all like to paint them as. For sure, they make some high level corporate decisions that make our life difficult, but WotC wouldn’t intentionally clamp down on the third party support of a product the fans were really into.
quote:
--------------------------------------------------------------------------------
2. Will they release the code/ show people how to modify the code if they can't support it? That would be a very useful alternative to number 1, above.
--------------------------------------------------------------------------------
If for some reason Fluid can no longer support eTools, we will release a fair portion of the code.
There are two qualifiers to the term, “fair portion.” First, WotC, thru contractual agreement, owns a certain part of the code – the object code. Fluid retains ownership of the source. I could not release the object code w/o their permission. Second, I will not release any source code that is in use for another Fluid project. That is to say, much of the low-level routine stuff is a collection of libraries we rely on from project to project. I won’t give away our trade secrets, as it were.
But if it did come to this – what we released would be substantive. Enough for the community to support eTools very effectively. (and btw, someone asked earlier – its C++).
quote:
--------------------------------------------------------------------------------
3. Will WOTC take legal action against those making hack patches to include non-SRD material (i.e. Oriental Adventures, Forgotten Realms, etc.)
--------------------------------------------------------------------------------
I cannot speak for WotC legal, but if you play nice-nice, I think you are safe.
I’ll will provide an educated guess on this matter. Let’s take Monsters of Faeurn for example. Right now – in version 1.0 of eTools - you can build all the content from Monsters of Faerun. You build a bunch of .rac files, then a bunch of .mon files.
I fully expect to see this content somewhere on the web within 2 weeks of ship date. And not as a ‘for sale’ item from WotC. Same goes for encounter tables and character sheets and etc.
Now if someone were to try and make a profit on ET MoF? Or if they trumpeted it around like, “Look! I am an official provider of D&D content! I built Monsters of Faerun! Click on this D&D logo to download the official version!” Then sure – yer gonna get a cease and desist from WotC.
But if you build it for your own campaign and offer it on your web site (or even EN World) for free, I think you are fine. WotC knows what eTools is capable of, and they want to see the community build it up because it of course promotes sales.
So I hope this answers the questions.
This is the kind of news most people have wanted to here.