UOX3.org

This one should be easy (jinx jinx)

The maximum weight you can carry displayed in the status screen is ALWAYS using a WEIGHTPERSTR modifier of 3.5, no matter the ini setting. This is purely cosmetic however:

When you set WEIGHTPERSTR to 3 for instance, you will get encumbered before the status screen tells you. The discrepancy between the values given by system messages (which seem to be correct) in the lower left of the screen and the maximum weight displayed in status gump, is exactly half STR in this case.

Somebody was using a constant where he shouldnt

edit: oh and by the by, the ini editor screws up the WEIGHTPERSTR, as in "takes away any commas" - turning a value of 3.5 into 35 but leaving 3 as it is. So its not just multiplying it. Keep that in mind if you're using the ini editor at all.

This is partly the fault of the client. Prior to the ML client, the max-weight in the status-window was entirely hardcoded client-side. With the release of ML though, clients can receive a max-weight update from the server.

From http://docs.polserver.com/packets/index.php?Packet=0x11 one can see that there's a "BYTE[2] Max Weight" part to packet 0x11, but I'm not sure how to enable & send the data correctly.

UOX3 seems to have some support for all the stuff up until (and including) flag 4 in the list linked above, while stuff added in UOML (flag 5) and UOKR (flag 6) aren't.

I've monkey'ed around in the source but have so far only managed to break max-weight completely locking it at a static 325 no matter what your strength etc is.

Fixed on CVS. Added support for flag5 stats (maxweight and race, though race isn't showing up anywhere I can see?) in the status gump for clients v5+.

Fix available in UOX3 v0.99.1.