Parser.cpp and Embparser.cpp fixes and additions Updated!

[Lurker_005]

Updated 12-31-2003

This applies to 5.3 DR1 or DR2, they both were the same. Both files were missing several commands that were already coded, as well as some other fixes. See http://www.everquestserver.com/forum...?p=63596#63596 for more information.

Updated and expanded Diffs are posted http://www.everquestserver.com/forum...?p=64036#64036

Includes:
Added commands and variables to perl quests
fixed bug with commas in text
fixed quest::faction so it actually worked right
some other minor stuff

[Eglin]

~150:
-	dosub("my_eval", &arg, G_SCALAR|G_DISCARD);
+	dosub("my_eval", &arg, G_SCALAR|G_DISCARD|G_EVAL|G_KEEPERR); //eval/keeperr added for perl bug, ala perlfunc @ fred

-			std::string temp = "wp.";
+			std::string temp = "wp";

[Scorpious2k]

Originally Posted by Lurker_005

< if (mob) mob->CastToClient()->SummonItem(atoi(arglist[0]));
---
> if (mob) mob->CastToClient()->SummonItem(atoi(arglist[0]), atoi(arglist[1])); //might be triggering a pereodic bug Lurker_005
685a686
> \\after adding this I would sometimes get data from an item that this summoned showing up after the text of another quest event

Doesn't changing this risk breaking exsiting quests? I'm not sure I see the problem it is fixing.

[Lurker_005]

Originally Posted by Scorpious2k

Doesn't changing this risk breaking exsiting quests? I'm not sure I see the problem it is fixing.

I checked that this works for quest:summonitem(1001) as well as quest:summonitem(1001,1) Granted I didn't verify that it will not cause problems with the qst format, but it shouldn't.

summonitem is a 2 paramater function with a default for count
Also summoning 5 nonstackable/non-charged items still only results in 1 item