Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon 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 Next
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!
Twitch
YouTube
Facebook (EN Publishing)
Facebook (EN World)
Twitter
Instagram
TikTok
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
The
VOIDRUNNER'S CODEX
is coming! Explore new worlds, fight oppressive empires, fend off fearsome aliens, and wield deadly psionics with this comprehensive boxed set expansion for 5E and A5E!
Community
General Tabletop Discussion
*Geek Talk & Media
E-TOOLS > Development of the Tool > Productive Comments Only
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="Feaelin" data-source="post: 308529" data-attributes="member: 1614"><p>On that note...</p><p></p><p>Something I've been wondering about is whether we need to apply some "organizing" to the various additions being made. Everyone is (understandably) working on whatever interests them, or they need for their character/campaign(s). That makes perfect sense. However...how can we avoid "duplication of effort"? I would say, everyone could just announce what they're working on, and others could hold off on those components that someone else is covering, but I've all too often seen such announcements, and the person ...run out of time or for some other reason not get it done.</p><p></p><p>Also, I've been madly downloading the various submissions so far, and I'm having a tough time figuring out how to keep track of it all. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" />. Any thoughts on organizing the data, other than just dumping everything into the database or the e-tools directories? When I get a FRRaces package from source A, and one from source B, is where I can see there being problems. If I spot a mistake in one, admittedly I can fix it pretty quickly, but the "appropaite" thing to do is also let the package author know so he can fix his package (for the benefit of others). The problem is, I don't see a ready way to identify the package authors. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" />...I want to know who to blam...er, praise! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p>(Hmm. I have lots of questions here, I think I'll pile them up, and yall sort 'em out. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p></p><p>Lastly: What happens if I import two different versions of a the same ET Helper set? For example, I plan to be doing a set for my home-brewed campaign setting, which I'll give to my players, but since I doubt that I will get it done in one version, I'll release multiple versions, each probably having a superset of the prior release's data. Do I need to have them completely delete the prior set before importing the new one? Will duplicate records be ignored or duplicated?</p></blockquote><p></p>
[QUOTE="Feaelin, post: 308529, member: 1614"] On that note... Something I've been wondering about is whether we need to apply some "organizing" to the various additions being made. Everyone is (understandably) working on whatever interests them, or they need for their character/campaign(s). That makes perfect sense. However...how can we avoid "duplication of effort"? I would say, everyone could just announce what they're working on, and others could hold off on those components that someone else is covering, but I've all too often seen such announcements, and the person ...run out of time or for some other reason not get it done. Also, I've been madly downloading the various submissions so far, and I'm having a tough time figuring out how to keep track of it all. :). Any thoughts on organizing the data, other than just dumping everything into the database or the e-tools directories? When I get a FRRaces package from source A, and one from source B, is where I can see there being problems. If I spot a mistake in one, admittedly I can fix it pretty quickly, but the "appropaite" thing to do is also let the package author know so he can fix his package (for the benefit of others). The problem is, I don't see a ready way to identify the package authors. :)...I want to know who to blam...er, praise! ;) (Hmm. I have lots of questions here, I think I'll pile them up, and yall sort 'em out. ;) Lastly: What happens if I import two different versions of a the same ET Helper set? For example, I plan to be doing a set for my home-brewed campaign setting, which I'll give to my players, but since I doubt that I will get it done in one version, I'll release multiple versions, each probably having a superset of the prior release's data. Do I need to have them completely delete the prior set before importing the new one? Will duplicate records be ignored or duplicated? [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Geek Talk & Media
E-TOOLS > Development of the Tool > Productive Comments Only
Top