Reply to thread

Message

<blockquote data-quote="Feaelin" data-source="post: 308529" data-attributes="member: 1614">On that note...Something I've been wondering about is whether we need to apply some &quot;organizing&quot; to the various additions being made.&nbsp; Everyone is (understandably) working on whatever interests them, or they need for their character/campaign(s).&nbsp; That makes perfect sense.&nbsp; However...how can we avoid &quot;duplication of effort&quot;?&nbsp; I would say, everyone could just announce what they're working on, and others could hold off on those components that someone else&nbsp; 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. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" />.&nbsp; Any thoughts on organizing the data, other than just dumping everything into the database or the e-tools directories?&nbsp; When I get a FRRaces package from source A, and one from source B, is where I can see there being problems.&nbsp; If I spot a mistake in one, admittedly I can fix it pretty quickly, but the &quot;appropaite&quot; thing to do is also let the package author know so he can fix his package (for the benefit of others).&nbsp; The problem is, I don't see a ready way to identify the package authors. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" />...I want to know who to blam...er, praise! <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink&nbsp; &nbsp; ;)"&nbsp; data-smilie="2"data-shortname=";)" />(Hmm. I have lots of questions here, I think I'll pile them up, and yall sort 'em out. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink&nbsp; &nbsp; ;)"&nbsp; data-smilie="2"data-shortname=";)" />Lastly: What happens if I import two different versions of a the same ET Helper set?&nbsp; 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.&nbsp;&nbsp; Do I need to have them completely delete the prior set before importing the new one?&nbsp; Will duplicate records be ignored or duplicated?</blockquote>

[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]

Verification