Reply to thread

Message

<blockquote data-quote="Zulithe" data-source="post: 2534774" data-attributes="member: 4708">What I don't like about eTools is that, from what I can tell by the way their store is setup, you MUST buy the 3.0 dataset (as it is part of the eTools &quot;core&quot; product) and the 3.5e dataset is a seperate product which costs extra.I would prefer to just buy eTools bundled with the 3.5 dataset and not have to pay for the 3.0 dataset as I will never use it.Another thing I noticed when I was using eTools at a friend's house, is that it takes a while to &quot;import&quot; datasets. Depending on the size of the dataset, anywhere from a couple minutes to nearly 15mins or more (probably a LOT more on slower PCs; we used a AMD 2200+ based machine) Also, each dataset must be imported seperately (from what I could find), and if you are working with multiple settings (say, 3.5 and a seperate one for Eberron) then you'll need to import it to BOTH which doubles the time it takes.</blockquote>

[QUOTE="Zulithe, post: 2534774, member: 4708"] What I don't like about eTools is that, from what I can tell by the way their store is setup, you MUST buy the 3.0 dataset (as it is part of the eTools "core" product) and the 3.5e dataset is a seperate product which costs extra. I would prefer to just buy eTools bundled with the 3.5 dataset and not have to pay for the 3.0 dataset as I will never use it. Another thing I noticed when I was using eTools at a friend's house, is that it takes a while to "import" datasets. Depending on the size of the dataset, anywhere from a couple minutes to nearly 15mins or more (probably a LOT more on slower PCs; we used a AMD 2200+ based machine) Also, each dataset must be imported seperately (from what I could find), and if you are working with multiple settings (say, 3.5 and a seperate one for Eberron) then you'll need to import it to BOTH which doubles the time it takes. [/QUOTE]

Verification