Character Select equipment

[John Adams]

I was adding some logging functions to Login today, and found a few fields that were missing from our Login database. After adding them, I got excited that character Equipment would appear now at Select... however, they still do not appear.

The reason is, there is no query to push World character item appearances to Login, so that has never been implemented. BUT! I did test it with sample data on a character, and items DO appear at Character Select.

This note is to remind me to finish implementing that

CharSelectEquip.jpg

[John Adams]

Guys, correct me if I'm wrong here...

Currently, LoginServer has tables for character equipment `appearances` - that is, it stores 1 record for each equip_type, it's RGB+HighlighRGB, and what slot it's in. Once I get the update working, it would push 1 record for every "visible" slot on a character so they can see what they're wearing at character select... that's the mission.

But here's what just dawned on me. If I have an `item_appearances` table on Login, shouldn't I just need the equip_type value and what slot it's in? And not store (redundantly) all that appearance data? Meaning, my equipment table could merely have character_id, equip_type, and slot. Then let Login go fetch the RGBs from it's own local appearances table.


Then of course, it just now occurred to me while writing this post - how would we handle Admins who make their own items, own appearances, without storing (locally) every item_appearance for each given world, like we do with custom zone names...

Sigh. Where are the big brains when I need them? I'll stick with tackling a normal-case scenario first, then we can expand to custom world items should the need arise.

[Gilraak]

Guys, correct me if I'm wrong here...

Currently, LoginServer has tables for character equipment `appearances` - that is, it stores 1 record for each equip_type, it's RGB+HighlighRGB, and what slot it's in. Once I get the update working, it would push 1 record for every "visible" slot on a character so they can see what they're wearing at character select... that's the mission.

But here's what just dawned on me. If I have an `item_appearances` table on Login, shouldn't I just need the equip_type value and what slot it's in? And not store (redundantly) all that appearance data? Meaning, my equipment table could merely have character_id, equip_type, and slot. Then let Login go fetch the RGBs from it's own local appearances table.

-- This would be the easiest approach and less of a load on mysql. This will also allow an easier time of color changes from dye and such. So pretty much upon login, mysql would fetch the data, read it, then fetch the corresponding data from the table appearances with the id given. Much easier then reading the data from point a, to reread from point b to jump back to point a to display point a.


Then of course, it just now occurred to me while writing this post - how would we handle Admins who make their own items, own appearances, without storing (locally) every item_appearance for each given world, like we do with custom zone names...

-- There isn't really an honest way around this I do believe, I'm not 100% sure you could do it without storing the data. Then again I may have read the question wrong.

Sigh. Where are the big brains when I need them? I'll stick with tackling a normal-case scenario first, then we can expand to custom world items should the need arise.

Hopefully overall my answers are a tad helpful in the direction you want to build. I can be more descriptive when I'm not talking to you in IRC at the same time about the DB Editor (;

[John Adams]

This will also allow an easier time of color changes from dye and such.

Since I have not "played" EQ2 officially for years, I was unaware of there being dyes and such... which then brings an entirely new facet of items appearances to EQ2Emulator in general. Right now, we have no provision for displaying you have BreastPlate of Uberness with a blue dye, while I have it with pink. Same item, right now, 1 appearance. For everyone.

I was *kinda* getting at that in the opening post, but wanted to start simple, then throw the hard questions out after. Since EQ2Emulator itself doesn't support custom tinting, I won't worry about it today - but something to think about in the future.

[John Adams]

Almost done with this (thank you SCAT for the knowledge!)

I think this might inspire me to release a new binary and code, just so other servers can utilize this new feature. I was going to wait for Tradeskills, but they are taking longer than expected.

[ilythor]

OH OH OH!

News Update?!

[John Adams]

Not yet, Jefe... I'll give you the scoop when it's time

[John Adams]

Looks like we got this! Some extensive testing needs to be done next, but we got our world synchronizing with Login to send your player items so you can see them in Character Select.

login_items.jpg

The thing left to do now is handle when players log off, to send any changes before they hit Login again and a few cleanups on some of my hack coding *Done*

This is live on TessEQ2 now!
Please log in, dress up, and check it out! Report issues here.

Known Issues (still):
* If you remove your items, World doesn't know how to tell Login to "delete" an appearance - yet.
* You'll probably have to exit completely and log back in to see changes... right now, /camp is too fast, and World cannot send updates quick enough - yet!!! Working on these issues still.


Ilythor, I'll give you a heads up when the release update is ready. Might still be a while, and might be in the form of ServerPack 1.3. Haven't decided yet.

[ilythor]

Looking good JA, looking real good.

Can't wait for the update, even if it's just for my peace of mind.