Seeds of Destruction - Bug Tracking
 

This post is created to allow us to track bug reports with Seeds of Destruction. A current list of the known issues for development tracking can be seen here:

http://www.eqemulator.org/forums/sho...774#post185774

If you find a bug that is not already on that list, please post it in this thread (not the development thread linked above) and I will get it added to that list. The list is updated regularly, so check back for current status and updates on bug reports and resolutions.

Last Update - April 29th 2010

Here is a list of some of the known issues/bugs with SoD and what is known about them:
1. Item Links - Item Links (and say links) are not the same between Titanium and SoD/SoF. Hopefully at some point we can add a way for them to be created for each client type and sent so the links appear properly for any client. This isn't as much a client bug as it is a problem between client versions.
2. No Rent Items - Logging out and back in with No Rent items after 15 minutes gives an error of "MOVE ITEM FAILED IN CLIENT APPLICATION".

Unverified Bug Reports:
None at this time.

Other Bugs/Issues:
I have seen 2 types of client bugs so far that seem to be caused by various things. I am pretty sure that in both cases, they should be possible to resolve by sending the client what it is expecting.

1. The Mouselook Bug - There are a couple of odd scenarios that can cause the mouse to get stuck in mouselook mode for about 2 minutes. I think this is just because the client is expecting something it isn't getting. It is better than just crashing when it doesn't get it, at least. At least it eventually recovers on it's own. I think we just need to identify each thing that can cause this and fix them one by one. One of the things I know can cause it is trying to unmem a spell that is higher than your current level, and I think another might be related to the server removing buffs from your character.

2. The Attack/Cast Bug - This bug reminds me of the bug we used to see a lot on previous clients where the client would sometimes get out of order packets and cause itself to be unable to cast or attack or do most things until using /quit or /camp and logging back in. This bug does not seem to recover on it's own from what I have seen so far. So, I think we will need to find the exact cause of this bug and resolve it. It could be something as simple as a missing or bad opcode, or it may be something new to the client all-together.

Resolved Bugs from this thread:
1. Memorized Spells - Loading spells sets now works properly (Thanks Derision!)
2. Apply Poison - Apply Poison should now work properly and no longer give a slot error (Thanks Derision!)
3. Froglok/Vahshir - Now show matching body and head as they should.
4. /who - /who <name> and /whotarget now function properly (Thanks Derision!!!)
5. LoH and HT - The PAL/SK class skills of Lay on Hands and Harm Touch are now AAs in SoD and have been added and appear to function properly.
2. Clicky Fail Bug - Failing a clicky item cast will no longer bug the client. Also, cast bars from item clickies now uses the time from the item not from the spell.

I have encountered two bugs since swapping to SOD.

The first is a completely whacked out bazaar and item linking system. I can not search by category or vendor in bazaar, and items that do show up are wrong priced, unclickable, bad names etc.
Players linking items in chat show up, but the name of the item seems to be missing the first 12 characters or so.

2nd bug is a endless client/window crash on my 58 Shadow Knight after using the spell "Cackling Bones". This might be SOD or might be in general.


**also just found: Tried selling an item to a buyer in the Bazaar. He was paying 400pp. When I sold it, it said "I sold 1 to IBuyer for 1322850327p 1g 6s 8c". It screwed all my platinum count up. Had to log out, upon logging in I had the appropriate money (400pp on my character.

Yeah, the Bazaar is next on my list to fix, probably tomorrow.

Did you crash as soon as you casted Cackling Bones, or after a buff was put on the pet ? (if the latter, that should be fixed in the latest source).

The bug with item links also happens when SoF sees a link sent from a Titanium client. We need a method to translate any links in chat messages if the source and destination are different clients.

Thanks for the bug reports, keep 'em coming :)

Just switched to SoD client for playing on PEQ. Logged into my characters and buffed up. While buffing up had to use Cannibalize AA on shaman for more mana and then when i went to case Quiessence to heal myself my HP would not increase, nor would a direct heal increase my hp (even after zoning around). I believe it updated in the group window, but it didn't update for me.

Yes, it seemed after I cast a buff on the pet is when the crashing started happening. Glad you're on top of that :)

Just like the above post, I also was experiencing odd HP values. For example, if I had Temperance and died then respawned, my HP bar showed something like 4200/5000. 5000 was the value with Temp, 4200 was my actual without temp, and my % hovered around 83 or whatever it was.

Yeah, the HP/Mana/Endurance formulas have changed. It isn't really a bug, which is why I didn't mention it here. It is mentioned in the other issues category for the main SoD development thread. Basically, the client just calculates those stats differently than our server does, and normally it thinks you have more HPs than the server does, which is why they never go to 100%. But, this is just a display bug, as you actually still have the exact same HPs you would in any other client, you just don't see yourself reach 100% like normal.

We already have some ideas for resolving the problem to either match the old clients with the new formulas, or match the new client with the old ones. The first thing we need are the actual formulas for calculating the new HP/Mana/End increase rates and stuff. That will probably take awhile, because they seem to have changed both base stats and also the increase amount per STA/INT/WIS increases.

I compiled the source to revision 1351 this afternoon, copied my character UI files from my SOF folder, and pasted them into my SOD folder. When I logged in my character, I summoned my bots and noticed that the HP bars were huge. I had to stretch out my group box to see them all.

I'm running a Windows server. Thanks for all of your hard work, guys!

Have you tried it on a new character without copying over old files from another client? Many things have changed with the UI, which probably explains why you are having that issue. I copied my character files over, but not the UI ones. You can copy the name_servername.ini files over, but the UI_name_servername.ini file will probably cause issues like you are seeing.

There were quite a few UI changes between SoF and SoD, including changes to the group window to include mana/endurance bars. Try downloading a newer copy of your custom UI from eqinterface.

Here's what I tried:
1) Deleted the UI_Character files
2) /loadskin default
3) Made a new character and spawned a bot
4) Logged into my other server, created a new char, and spawned a bot
5) Recompiled to rev1354, created a new char, and spawned a bot
6) Reinstalled the pre-compiled rev1316 from peq, made a new char, and spawned a bot

Results: The bars in my group window still look blown up on tests 1-5.
The bots wouldn't join my group with rev1316-Bots.

Note: I'm using the default UI that installed with SoD. I just didn't know what all files I needed to copy into new installation to keep all my macros, so I just copied all of them that had my character's names in it.

items - spell scrolls
 

Spell scrolls in SoF and SoD were changed to include an added effect that isn't included on the emulator. Rk. II an Rk. III type spell scrolls have an added effect on live of un-memming the previous version of the spell.

In other words - If you scribe the Rk. III version of the spell from a scroll and have Rk. II in your book, a pop-up box is displayed telling you that the previous version will be replaced in your book. If you click 'Yes' or 'ok' (can't remember which), the Rk. II spell i removed from your spell book and the Rk. III is placed in it's location. - clicking 'no' will cancel the scribe.

I'm not sure if there's a different opcode for each spell or not, and not even sure how to figure that out, but I believe this change is the reason a lot of the spells in the 'items' table of the DB are listed as level 255 when looking at the scroll item, but 'spells_new' shows the correct class/level for the spells. All spells that are grouped along with Rk. II an Rk. III versions seem to be included with this problem.

It would be cool if the #scribespells command would remove previous versions also in order to make spellbooks more 'correct', and prevent filling spellbooks before all spells are memmed. Toons aren't supposed to need the lower versions if you have the Rk. III versions anyways.

Con colors are not correct on the SoD client, things that should be green to a 65 are appearing white. (was running through Lake of Ill Omen when i noticed) And goblins at the entrance area of veksar are green but i believe should be light blue to 65.

That's actually correct. They aren't white, they are gray. Sony added a con level below green way back.

ah didn't know, just felt weird.

I've noticed the following so far:

1. Sometimes I randomly "crash" while zoning... "crash" as in the client just sits there forever.

2. Spent AA count is always at 500

3. Vah shir facial features are not sent correctly. The faces shows correctly but the body doesn't. (Just noticed the same case with frogloks)

4. Bazaar window gets filled with jiberish when doing searchs.

5. When memorizing a spell set, if you do not manually empty your spell bar it will not fill it up.

6. Couldn't get #melody to work, if i'm even doing it right (/melody 1 3 7 8)

7. Sometimes when looting a corpse it will give the invalid item message or something and the corpse will disappear (only disappeared so far in Shadowrest) and force you to stop looting.

8. Summoning my mount does not show a spell cast bar, but it does summon.

9. loot all option doesn't work (only tried it once)

Will give more as i find them.

Thanks for the reports, Iclia! I think if you are playing on PEQ or some other server, it is not yet running the very latest updates. I know for sure that the 500 spent AAs bug should be fixed, and I am trying to work out the issue where some AAs have to be displayed multiple times instead of stacking them all into 1 AA (multi-tiered AAs).

I don't quite remember what causes the face setting issues on Frogloks and Vahshir, but I do remember seeing and fixing that issue on SoF. I am sure we will get it figured out sometime soon.

I think we probably need to add some extra handling for unmeming spells, as it seems that Live has made it so they stay even after death, so it probably isn't handled the same way as it was before. There may be an extra packet for unmemming spells now or something.

You mentioned #melody, but then you example used /melody. Note that the # and / are not the same thing! The / version doesn't work, but the # version should work just fine.

The looting problem may be due to more slot changes on corpses. If so, people may also see where they try to loot one thing, but it actually loots something different.

The loot all option is a new feature and at this point, we are concerned with getting old features working fully before focusing on many new features.

Bazaar stuff probably needs some structure work to be ok again, since they added new fields for searches and stuff.

Clicky items should be giving a cast bar like normal, but it probably depends on what your spell file has for the cast time, not what the item says for the cast time. So, if the cast time in your spell file says it is 0, and the item says it is 5 seconds, then you will see no cast bar, but it will still take 5 seconds before it buffs you.

If you are getting disconnects on zoning, that may be due to normal server load. If you never experience that issue while using Titanium and only do on SoD, then maybe it is an SoD issue, but we will need to isolate the problem more before we can try to fix it if there is an actual issue with zoning.

Never had the connection issue in titanium and yes i am on PEQ.

Also found that tracking players fails.

Disreguard most of my previous post. Spell scrolls in SoD work fine after the items table is updated with 13th floor items (I was using an older copy of PeQ db.). Would possibly help for #scribespells to work as I was describing and skip lower versions or un-mem them as I was mentioning to keep from filling the spell book, but not a big deal.

I've switched entirely over to using the SoD client (I'm on PEQ), and so far everything is really stable and playable, albeit a little buggy in some spots. I'll just post as I find them. Here is stuff I've noticed so far (I briefly looked through the SoF bugs, but forgive me if I have any repeats from there).

-Apply Poison: When my rogue applies poison, he always fails with the message "Error: item not found for inventory slot # or is not a poison." I've only tried with Aching Blood, which is all that was left in my inventory at the time. Let me know if you want me to try out any other poisons.

-Spell Sets: If you already have a spell set memorized, and right click the spell gem book to load a new saved set, it will not remove the current gems, so you stay with the first gem set. If your gems are already empty (i.e. after a death or manually clearing them) then it loads a spell set just fine.

Will post more as I find them.

Tracking has another bug, not sure if it is SoD related. But the tracking window has an option for it to auto update teh tracking list. While this is active i get the message "Ability recovery time not yet met", which means it's trying to track but can't i assume. So either the refresh time on track needs to be lowered or something else...

The tracking auto-refresh, spell set loading and apply poison bug should all be fixed as of Rev1365.

Not sure if this has been attempted to be fixed or not, but on my BST when i click my Legs for pet haste, most of the time it locks up my casting. It doesn't lock up my ability to attack or send my pet, but it does lock up casting and appears to lock up any use of hotkeys period.

Thanks for the report, Wolftousen. Do you know the actual name of the legs you are using when you have this problem, so we can test them? Also, what is the name of the effect you see on the legs and what server are you playing on? Do you happen to have a custom spell file installed from any custom server, or are you running the SoD default one? If the spell your item shows does not match the one the client has, it might cause a bug like that.

When the client gets bugged like that, it would normally be due to it expecting a packet from the server that it never receives. So, we should just need to find why it isn't sending the right response and fix it.

A birdy mentioned to me that there might be another spell slot on top of the AA slot, which might cause issues for the spell code and clickies if true. The server wont send a reply packet for casting if we think you're cheating, we simply return from the function.

Yeah, just saw a post about it in the SoD Dev thread. I had been wondering how that would work out if it was added in, but didn't notice it had been. It will definitely take some looking into. I am sure we can make a work-around for it if needed. Something as simple as a ClientVer check and adjustment to the slot may work. Since clickie items don't send casting packets in SoF or SoD, we could probably just exclude those clients from the slot 10/item check stuff.

I'm playing on PEQ with the base spell file that came with the SoD steam download. The item that seems to cause this is: Leggings of the Khati Sha.

I have been using other clickies: drogmors, ornate bps, and Talisman of the Burrower. Those items have not yet caused this issues.

Thank again for the info. After thinking about it, I bet it is not a problem with the clicky itself. Initially, we had problems with pet buffs causing the client to crash, but Derision fixed that by correcting the pet buff window. I think chances are that the problem is somehow being caused by either pet buffs or the new target buff window feature, or something similar/related. Maybe something special is expected for pet buffs.

When you clicked those legs, did you already have your pet targeted at the time?

Also, I am not currently sure which revision PEQ is running, so the issue you are experiencing may already be fixed in the latest SVN updates.

I will try to test out those legs tonight and see if I can reproduce it.

Just tried those legs clicky on my test server and they seemed to work just fine. Maybe you need to wait until PEQ updates again and try them again.

PEQ is always running a day behind in regards to the changelog, at this point we are current since there are no changes today. I suspect our problem might be due to the newest 13th floor dump I did. Looks like Sony has changed some things in items and we are seeing small problems pop up.

Hmm, I just went ahead and tested this item on PEQ and it worked fine for me... No problems.

Ok, i have been paying more attention when I use those pants. It happened again, but I did not have a target of any kind when i clicked them. Same issues occured after until I zoned.

This has happend in 2 locations as far as I have been paying attention: PoTactics (while buffing at zone in) and LDONs. I haven't ventured outside of that much since i've been back (at least while playing my BL).

Not sure if this is a known bug or not. but sometimes when I move forward with the up arrow key and using the mouse to manuever the character, the character gets flips to the side when I scroll back using the mouse scrolling instead of scrolling back directly behind the character. It does not happen every time though so it's really not a major thing. it usually straighten out when I shake the mouse back into the right position.

Clarification on the error with the BL, if I do not have a target and click the pants, I get the immediate error:

"You must first select a target for this spell!"
"Your spell is interrupted"

But the cast bar appears and keeps going. Ducking, moving or using /stopcast doesn't stop it.

If i have any target at all, the pants work as they should giving my pet the buff. Though my target doesn't change to my pet when i click them.

I went and played around a bit with the mouse scrolling and stuff after posting. I haven't had side scrolling when scrolling out with the mouse. Maybe it's a bug on my computer. I just noticed it a few days ago and thought i should post it.

I haven't noticed any odd camera issues other than it being able to see under the world easier if you are in 3rd person compared to previous clients, but that is exactly how it is on Live still currently.

As for the clicky problem, it makes more sense now I think. Sounds like we may have a problem with interrupting casts. If it doesn't get the interrupt and never gets the finish casting packet(s), it can definitely bug your client like that. So, maybe we just have the interrupt opcode incorrect or something. I will check it out. Thanks :)

EDIT: Yeah, I can duplicate the bug if I don't have a target like you mentioned. I am thinking maybe the client knows to expect the item to cast the spell, but not getting what it expects when it fails. Still investigating.

I noticed the ability harm touch / layhands are missing in SoD. I went and check out on titanium and SoF and it shows up on there in the skill window when you hit on one of the box in the ability tab. I don't see it anywhere on SoD. Not sure about the other classes. I know on live it shows on AA and ability window.

SoD client refuses to reconnect if you're connection to the internet shuts down and restarts. I have my desktop being fed internet from my laptop via cross over cable and dog ripped it out (little prong locks are gone sadly, and thankfully...) and i immediately plugged it back in and watched as my link bar never came back....

Annoying to say the least b/c it caused a wipe...

Wolf, I think any client will do that if the connection is gone long enough. I don't know if you can blame SoD for your dog ripping out the cable! :P

And thanks, robinreg, I will try to check on LoH and HT soon.

I'm pretty sure this is a caveat of windows networking and should affect all clients equally. In my experience, if you loose link on an ethernet port, windows closes all connections via that interface immediately.

I just like to say - when the devs will be looking into the issue above, would you PLEASE consider taking this into account??

http://www.eqemulator.org/forums/showthread.php?t=28603

PLEASE :)