Halp? Bag List Glitch

[hlcounterstrike]

I'm getting a glitch on my lowbie where the bag list is scrolled way up to the point that I can only see my equipped armor. Any possible ways to fix this on my end?

 

[J-M v2.5.5]

This is caused as follows:
Suppose you have one character with a lot of stuff equipped (bag, quiver, spellbook, weapons strap, two magic rings, shield, armor, helmet). Let's say you scroll all the way down in your inventory menu now.
If you change your character now to a character with way less bags (so that there is no scrollbar visible), the scrollbar is actually still positioned all the way down, but because you can't see it (due to not having a lot of items) you can't scroll up.

Solution: reconnect with character with lots of gear, scroll up. Hope this made sense.

 

[hlcounterstrike]

Ah, yeah that makes sense. Thanks for the troubleshooting

 

[Thothie]

Ya really need to close half-life before switching characters or servers. Bad things can happen.

 

[The Man In Black]

I fixed quite a few of the bugs with switching characters. Didn't know this was another. Got any more that need attention?

 

[Thothie]

So much weird stuff happens, even on a listen server, that I'm not sure where to begin. All setvard's in player_main and it's sub scripts remain between character changes. Player hp/mana do not update properly. No doubt, since the shared bits of code do not re-initiate in sync, there are many more problems on a dedicated.

Then there's all the stuff that goes wonky only "some of the time" and tis hard to reproduce. :\

Thus why I always recommend shutting HL down before changing characters or switching servers. Client and server just don't stay in sync, and it's really hard to predict what all may happen as a result. Tis one of the things I loathe about the shared script system - it's much more dynamic, but it'd be nice if it didn't share by default, and I think the whole server<->client script system tag's ([client], [shared], [override], and #scope, for instance) often work incorrectly - as demonstrated by our "split script" issues.

Eliminating those scripts that are not equipped and active would go a long to fixing that, I suspect. Beyond that, all I can think of is a more thorough resetting of client data, but I'm not sure where to begin there.

 

[The Man In Black]

memset( pPlayer, 0, sizeof(pPlayer) ) ?