Saeviomagy
Adventurer
Sure, but there's nowhere written "here's how you actually do it". There are only rules for CREATING a single-spell scroll.Patryn of Elvenshae said:Yeah, I'm willing to buy that; like I said earlier, I'm not entirely sold on the "1 spell / preparation per 'charge'" reading. Perhaps a better way would be to look to wands, which require (at low-levels, anyway) one expenditure of MM (CL1) for 50 charges of MM (CL1).
Well, yes, there are - check the magic item section on scrolls, and you'll see that the vast majority of randomly generated scrolls have more than one spell on them, and the vast majority of those won't have the same spell multiple times.
There are no rules on how to create a scroll with multiple spells upon it - there are examples of scrolls that have multiple spells, so clearly they exist. There's a section that says 'scrolls may be made with multiple spells', but nowhere does it say "here's how you do it..."Could you explain a bit?
Both of us have assumed that it's possible to do, and that we end up combining the price of scribing each spell into a single run of enchanting, and that failing at that run of enchanting ruins the entire scroll.
You've assumed that creating a multiple spell scroll requires each spell on the scroll to be cast during it's creation. You believe that each spell you write out wipes that spell from your memory at the time it is written out - so if you want to write it out twice, you have to memorise it twice.
I agree with that for the purpose of two different spells - however I believe that the same does not apply for scribing multiple copies of a spell - I believe that when you design the scroll, you write up a 'prerequisites' block, including each spell to be on the scroll, and then you must cast each of those during the creation process
Ah, see here's where I got confused. I thought that you were partially breaking up the enchanting process spell-by-spell because, frankly, that's the only way I could imagine it working. Once you've written out each spell, the spell is erased from your mind, and at that point you've succeeded at placing that spell on the scroll.So, no starting out attempting to make a 5 "charge" scroll and ending with a partially successful 3 "charge" scroll. It's an all or nothing affair. My way makes it easier to make a 1 "charge" scroll than to make a 3 "charge" scroll.
Otherwise you're doing a single creation process for the whole thing, and you're back to my process of producing a prerequisites line for the entire item, and emulating any given spell a single time.
Ah, well I sort of messed up my market and base prices there. I was actually talking about a scroll with enough CLWs on it that it would take 1 day to craft - 40.Well, that's not quite true.
An 80 "charge" scroll of CLW would take two days to create.
I prefer my players to make use of feats that they have. Currently most players never scribe scrolls due to the time involved, not to mention the XP costs. Making a multi-part scroll only take a single day makes things a bit more manageable. Not to mention the fact that it lets a 1st level artificer actually use one of his major class features (his craft reserve).Accordingly, the guy making one roll for the entire CLW prereq would need to succeed on either day 1 or day 2, and if he failed, could try once more on day 2. He's got three chances to fail.
Under mine, he'd get 80 chances on day 1 to fail, would get a second shot on the spells he didn't succeed at on day 1 on day 2, and would get a last-ditch attempt on day 2 to complete any he hadn't made yet.
As an example, let's assume he's got a 10% chance to fail any given roll.
Under your methodology, the artificer can make an 80 "charge" scroll ~99% of the time.
Under my methodology, the artificer can make an 80 "charge" scroll ~48% of the time.
At 15% chance of failure, he's successful 98% of the time under your method, and only 20% of the time under my method.
At a 50% chance of failure, he's successful 80% of the time under your method, and is so certain to fail under my method it's statiscally ignorable.
I like the way my numbers work better ...![]()