Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Community
General Tabletop Discussion
*Geek Talk & Media
eTools Patch and Source Code
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="smetzger" data-source="post: 456483" data-attributes="member: 1230"><p>Luke - I know that you are a big proponent of scripting + database. This strategy seems to work good for RPM and it is the most flexible.</p><p></p><p>However, it is possible to do alot without using scripting. Of all the 3e programs released yours is one of the few (and maybe only) that uses scripting. </p><p></p><p>Fluid could have done everything in the database to cover the 3 core books; it may not have allowed for entry of all splatbooks and 3rd party material. But, they could have done this without hardcoding.</p><p></p><p>First off I believe that e-tools has failed. I believe it is for a variety of reasons:</p><p>1) Fluid is a game and graphics company. They had no prior experience with database programming.</p><p>2) WOTC prioritized the wrong things, like sounds and 3d scans and mapping. IMO the character generator should have been the priority with everything else being secondary.</p><p>3) The WOTC person in charge of the project changed frequently.</p><p>4) Hasbro, sold the video game rights out from under Fluid.</p><p></p><p>I think most of the blame falls on WOTC. They are the ones who selected Fluid for the job and they are the ones who mismanaged the project. WOTC doesn't have much excuse for this. They have managed other projects like this (CD Core Rules I & II). Although Core Rules I was pretty bad, Core Rules II was usable.</p><p></p><p>IMO the only thing that was done correctly was using a standard database instead of a custom one.</p><p></p><p>How can WOTC fix this? I think the best thing for WOTC to do is to:</p><p>1) Deliver the long awaited patch</p><p>2) Release clearer software wording for d20 software.</p><p></p><p>Also, if WOTC wanted to be agressive in addressing this issue they could:</p><p>1) Release the source code for e-tools.</p><p>2) Keep an up to date list of OGL and d20 software links on their web site.</p><p></p><p>I don't think that WOTC needs to produce any more D&D software. The 3rd party D&D software industry is really rich with decent software. If they just encourage this industry a little bit everything will be fine.</p></blockquote><p></p>
[QUOTE="smetzger, post: 456483, member: 1230"] Luke - I know that you are a big proponent of scripting + database. This strategy seems to work good for RPM and it is the most flexible. However, it is possible to do alot without using scripting. Of all the 3e programs released yours is one of the few (and maybe only) that uses scripting. Fluid could have done everything in the database to cover the 3 core books; it may not have allowed for entry of all splatbooks and 3rd party material. But, they could have done this without hardcoding. First off I believe that e-tools has failed. I believe it is for a variety of reasons: 1) Fluid is a game and graphics company. They had no prior experience with database programming. 2) WOTC prioritized the wrong things, like sounds and 3d scans and mapping. IMO the character generator should have been the priority with everything else being secondary. 3) The WOTC person in charge of the project changed frequently. 4) Hasbro, sold the video game rights out from under Fluid. I think most of the blame falls on WOTC. They are the ones who selected Fluid for the job and they are the ones who mismanaged the project. WOTC doesn't have much excuse for this. They have managed other projects like this (CD Core Rules I & II). Although Core Rules I was pretty bad, Core Rules II was usable. IMO the only thing that was done correctly was using a standard database instead of a custom one. How can WOTC fix this? I think the best thing for WOTC to do is to: 1) Deliver the long awaited patch 2) Release clearer software wording for d20 software. Also, if WOTC wanted to be agressive in addressing this issue they could: 1) Release the source code for e-tools. 2) Keep an up to date list of OGL and d20 software links on their web site. I don't think that WOTC needs to produce any more D&D software. The 3rd party D&D software industry is really rich with decent software. If they just encourage this industry a little bit everything will be fine. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Geek Talk & Media
eTools Patch and Source Code
Top