Reply to thread

Message

<blockquote data-quote="Janik" data-source="post: 433844" data-attributes="member: 8033">I actually did consider sharing the data between campaigns but decided against it for a few reasons:1. Each time the user creates a new spell/feat/etc., there would need to be a prompt asking &quot;Do you wish for this spell to be visible in Campaign A, B, C...&quot; which would be slow and annoying. The alternative is - you add a spell in Campaign A and it is automatically in all the campaigns, which is just as annoying if you only wanted the spell in Campaign A.2. What if in Campaign A you use the regular Fireball spell, but in Campaign B you want to change the Fireball description to add something about wild magic for example (let's say Campaign B has wild magic but not A)? You'd have to create two spells, call them both Fireball, and set the correct one visible for each campaign - again, annoying to the user.3. Odds are that there won't be much overlap between different gaming worlds, and none at all if you use a different d20 game in a different campaign. If you're running more than one group in a single campaign world, it would perhaps be easier to keep all the PC's groups in the same campaign rather than make 3 campaigns.4. If you do want to copy the spell from campaign A to campaign B, the import/export functions make it pretty easy. It's an extra step, but automatically including the spell in all campaigns also requires an extra step when you don't want it.So that's why the data is redundant in DM Genie. Its not really from laziness, as it wouldn't have been too hard to implement, but I think it would make the program harder to use and/or more confusing to the end user.</blockquote>

[QUOTE="Janik, post: 433844, member: 8033"] I actually did consider sharing the data between campaigns but decided against it for a few reasons: 1. Each time the user creates a new spell/feat/etc., there would need to be a prompt asking "Do you wish for this spell to be visible in Campaign A, B, C..." which would be slow and annoying. The alternative is - you add a spell in Campaign A and it is automatically in all the campaigns, which is just as annoying if you only wanted the spell in Campaign A. 2. What if in Campaign A you use the regular Fireball spell, but in Campaign B you want to change the Fireball description to add something about wild magic for example (let's say Campaign B has wild magic but not A)? You'd have to create two spells, call them both Fireball, and set the correct one visible for each campaign - again, annoying to the user. 3. Odds are that there won't be much overlap between different gaming worlds, and none at all if you use a different d20 game in a different campaign. If you're running more than one group in a single campaign world, it would perhaps be easier to keep all the PC's groups in the same campaign rather than make 3 campaigns. 4. If you do want to copy the spell from campaign A to campaign B, the import/export functions make it pretty easy. It's an extra step, but automatically including the spell in all campaigns also requires an extra step when you don't want it. So that's why the data is redundant in DM Genie. Its not really from laziness, as it wouldn't have been too hard to implement, but I think it would make the program harder to use and/or more confusing to the end user. [/QUOTE]

Verification