Miscellaneous 5.2 bugs

[mollymillions]

Tested with EQEmu 5.2 and MW_051_052_alpha1 (with the 5.2 updates). Most are obvious and not important, some have been mentioned elsewhere or with slightly different symptoms.


Sewing kits. I tested combing two spiderling silks in some sewing kits and found that on the first use the sewing kit will work, but the components remain in the kit, and the kit will become unusable. All subsequent combine attempts, regardless of the components used, will give the "You cannot combine these items in this container type!" warming and the items will be destroyed (except for spiderling silks which will not be destroyed).

Mend does not work - Zone.exe gives the following error:
Unknown opcode: 0x007a size:0 Client:Mildew

Some Guild Trainers say "String(0) not found" (or something similar) after closing the training window (tested with the Monk guild trainers in Freportw). May be DB related?

Zone.exe gives the following error when any client connects (probably DB related):
[Error] Warning: Invalid PlayerAA_Struct size found in database (????)

Closing the loot corpse window while the "Loot No Drop Item?" dialog is still open causes the mouse to become bugged (cannot select target, etc until zoning). Zone.exe and World.exe do not show any errors but the chat window displays:
Error: Corpse::LootItem: BeingLootedBy != client

Bind wound does not work and if you have bandages available, the mouse pointer will become bugged (cannot select a target, etc until zoning). The following error is displayed in the chat window:
MOVE ITEM FAILED IN CLIENT APPLICATION
And zone.exe displays the following error:
[Error] Size mismatch for Bind wound packet
0: F3 00 00 00 00 00 00 00 |

[Edgar1898]

Sewing kits. I tested combing two spiderling silks in some sewing kits and found that on the first use the sewing kit will work, but the components remain in the kit, and the kit will become unusable. All subsequent combine attempts, regardless of the components used, will give the "You cannot combine these items in this container type!" warming and the items will be destroyed (except for spiderling silks which will not be destroyed).

Mend does not work - Zone.exe gives the following error:
Unknown opcode: 0x007a size:0 Client:Mildew

Some Guild Trainers say "String(0) not found" (or something similar) after closing the training window (tested with the Monk guild trainers in Freportw). May be DB related?

Zone.exe gives the following error when any client connects:
[Error] Warning: Invalid PlayerAA_Struct size found in database (????)


I fixed all these tonight, I'll get the rest fixed later. BTW Thanks for the nice bug report, I wish more people realized that the more they help out with reporting the bugs, the faster (much faster) the bugs are fixed.

[Nightcrawler]

I dont know if this is a bug probably crating a character Val Shir and then joining game crashes whit eroor msg vanil shir zone was not found in everquest foulder?

btw. hi im new in here

If i find any suspicious stuff il post it here.

[haecz]

i just went to cobaltscar. ran around some..
then went down to the water, at the seashell-houses..
and i found a 'oven' in one of them,,..
i clicked on it and crashed.

8)

edit: (on shawn's server btw)

[Edgar1898]

Nightcrawler:
Nah, that just means you need to get the zone file from the everquest patcher.

[Eglin]

Also zone.exe gives these errors:
[Status] Error exporting var: Perl runtime error: Can't modify concatenation (.) or string in scalar assignment at (eval 8728) line 1, at EOF
even with empty quest and plugin directories (and no files with a .pl extension exist in the EQ directory or sub directoies).

change this line, and bob's your uncle.
std::string temp = "wp";

[Trumpcard]

Thanks for finding that... the spam was obnoxious!

[Lurker_005]

There are issues with passing text in Perl scripts. e.g.
quest::say('Hello, ' . $name . '.');
or
quest::say("Hello, $name \.");
Should work correctly but the text will be truncated at the comma and the remaining text will have all of the spaces removed.


I know that the qst format had problems with commas. And if I understand how things work, the say command and text is still passed back and processed by parser.cpp where it parses the say text, finds the comma and treats it as an iterator or something. Plus wouldn't perl have already evaluated any escape strings like \,

[farce]

well i was trying to fix this earlier.. and turned on debugging for it. I noticed that the Parms: output was fine, and only the after: was jacked up when you had commas.

So I had the idea of just using the data it showed in Parms: instead of after:

The result is that the 'groups of commands' are still seperated, but the text is unmangled.

Codewise, just change all references to arglist[0] to parms.c_str() in Parser::ExCommands() in file parser.cpp

farce

[mollymillions]

Cheers Farce.
From my experiences embedding VBScript in VB apps i felt that there would be a simple solution for this oversight.

[Lurker_005]

Great fix, Thanks for finding it!

[D_Skywalk]

I send some bugs reports and anyone said thanks :cry:

Cu, mollymillions ;)