Reply to thread

Message: <blockquote data-quote="EricLeaf" data-source="post: 468264" data-attributes="member: 6437">More than likely that is it. There were 2 versions of that, and it was translated into a number of other languages, it being pokemon and all. You can see all this info at Fluid's website, I just mentioned it because it was what Fluid did prior to MT, and seeing that and the CharGen demo should illustrate what Fluid does and then compare that to what the fans screamed for and you get eTools. Satisfying no one.Instead of becoming more graphical than Core Rules, it ended up being less graphical. With only some minor skinning ability and tool icons.I'm not the best with dates, so I'll do this all with relative dates. PHB was released at GenCon (2000?) a few month before that CharGen demo was done. MT work began at or shortly after that GenCon, I began work on the mapper September 2000.Shortly before GenCon 2001 the mapper is dropped, and then a few months later the entire project is dropped. At about the time Eric Noah was test driving his sneak peak version, it was completely changed by the removal of the mapper. Mid September I was no longer working for Fluid, a few months later the other programmer (co-owner) is no longer working for Fluid (although still an owner). Then December Ryan Dancy gets a reduced project plan okayed and I start a (at that time) 2-3 month contract to clean it up and release it as is. This later evolved into a 6 month clean up, beta test and minor feature addition (namely the table editor and all the generators).From the cut mapper to when the project came back, I expect it was Ryan working hard to bring something from it. The opposing force was Valterra whom I sure you know.From what I know he wasn't in the software department at that time, having been drummed out in embarrassment (some legal problems with the Dragon Archive I hear) by Bill Dugan. But after Dugan and Bishop left, there was no software department (almost) so Valterra got back into it. But that is just a guess.</blockquote>

Verification