scribespell for one level

[trevius]

You don't have to redo your entire DB every time that you update. Just make sure that you run the SQL updates in the /utils/sql/svn folder for all revisions after the o e you were already running.

[Randymarsh9]

so what rev is this in? I updated everything but I didn't see anything talking about scribespells

[trevius]

AndMetal put it in on R732:

==07/01/2009==
AndMetal: quest::scribespells can now accept minimum level as a 2nd argument. Examples: quest::scribespells(60,60) will scribe just level 60 spells, quest::scribespells(75,71) will scribe spells from 71 through 75.
AndMetal: Ditto with #scribespells, quest::traindiscs, & #traindiscs.
AndMetal: quest::scribespells & quest::traindiscs will now return the amount of spells/disciplines that were scribed/learned (an optional way to verify success or failure).
AndMetal: #scribespells & #traindiscs will limit the max level to whatever the rule Character:MaxLevel is set to, unless you have GM Mode turned on, in which case it's limited to 255 (uint.

[Randymarsh9]

that's odd. I updated all of the things and restarted my server but the quest and command both don't work.

[Randymarsh9]

For the Rev732 one it just says

INSERT INTO `rule_values` VALUES ('1', 'Spells:SacrificeMinLevel', '46', 'First level Sacrifice will work on');
INSERT INTO `rule_values` VALUES ('1', 'Spells:SacrificeMaxLevel', '69', 'Last level Sacrifice will work on');
INSERT INTO `rule_values` VALUES ('1', 'Spells:SacrificeItemID', '9963', 'Item ID of the item Sacrifice will return. Defaults to an Essence Emerald.');

[gaeorn]

The SQL update, if any, doesn't define what code changes may or may not have been implemented in a revision. AndMetal happened to also include sacrifice changes into the same revision.

When you say the command doesn't work, are you getting an error message? Is it silently not behaving as desired? What exactly do you mean by it doesn't work?

I reviewed the code for the command #scribespells and it appears it should function correctly.

[Shendare]

It appears to work properly for me.

For testing purposes, I recently created a mage, did a #level 75, then used #scribespells to get just 71-75 spells.

[Randymarsh9]

well I did #scribespells 70, 65 #scribespells (70, 65) and then in a quest I had #quest::scribespells (70,65) and none of those worked

[Shendare]

Just for clarification, in case it's a punctuation issue you're running into, the #scribespells command must be entered exactly as follows:

#scribespells 70 65

No parentheses or commas.

The quest::scribespells function should be called exactly as follows:

sub EVENT_SAY
{
  quest::scribespells(70,65);
}

No # symbol before 'quest' or space before the parenthesis, and followed by a semicolon.

[Randymarsh9]

It just scribes my spells from 1-70 no matter what

[Shendare]

Then it sounds like you're still running an old version of the server.

After compiling the newer rev, did you copy the new .exe files from the source code's Build directory to your server's main EQEmu directory?

[Randymarsh9]

no i did not

[Shendare]

After doing a recompile, the following files should be copied to your server's main EQEmu directory to complete the update:

src\EQEmuServer\Build\*.exe
src\EQEmuServer\utils\*.conf
src\EQEmuServer\eqlaunch\release\*.exe

Make sure you have shut down all running EQEmu server programs before attempting to copy the files.

[steve]

Originally Posted by Shendare

#scribespells 70 65

I'm just curious why the numbers are used backwards? Is this one of those EU vs US things? Seems like it should be:

#scribespells 65 70 or #scribespells 10 25

Or am I missing something?

[Shendare]

The numbers are reversed because the usage of the command is actually as follows:

#scribespells MaxLevel [MinLevel]

Where MinLevel is optional, defaulting to 1 if omitted.

MinLevel is a later addition to the command, which used to only take MaxLevel and always use a MinLevel of 1.