PCRPG 3.36

[Corona]

Yeah, this is a known problem. I once purchased 700 parchments, disconnected and reconnected (the server did not crash) ...and then I had 500 on me. :S

[Particle]

Interesting.  Usually when people complain about losing items, it's the problem I described (though they don't realize it).  I'll add it to my "investigate" list for 3.36.

[Particle]

It appears to be by design.  When you save your character file, it checks if you have more than $maxItem of any one item when it builds the list of your stuff.  If so, it drops you down to $maxItem.  It's a global variable in globals.cs and defaults to 500.

So, it will save a max of $maxItem (default 500) of any particular thing but will let higher quantities float in memory until you log on again.  At that point, it uses the capped item count that it saved.

[Xenos]

So it's an easy fix then?  Some people carry up in to the 10,000 range.  I dont think anyone legit has more than 100,000 of any items.  You could just make it some abusurd high number or remove it right?

[Particle]

It wouldn't be a fix so much as an adjustment.  It's a preference, just like how many SP you want people to get upon leveling up.

Yeah, it's easy to change.

[Jeenyus]

I'd like to sell more than 100 items/click and take more than 100/click from my storage. A lot of people would like that. Don't know if you can do that.

[Particle]

Yeah.  Admins can do 1000x at a time if they want.  Players are limited to 100x.

[Jeenyus]

Why are we limited?  

[Particle]

You can crash the server with that feature if you go high enough.  It's done with a loop instead of just quantities.  Admins can be trusted typically not to be malicious with that power.  Players cannot.

[Xenos]

You can crash the server with that feature if you go high enough.  It's done with a loop instead of just quantities.  Admins can be trusted typically not to be malicious with that power.  Players cannot.

So does this mean it's on your list of things to fix or that we are stuck at 100?

[HUBBA]

You can crash the server with that feature if you go high enough.  It's done with a loop instead of just quantities.  Admins can be trusted typically not to be malicious with that power.  Players cannot.

So does this mean it's on your list of things to fix or that we are stuck at 100?

I think you are stuck with a hundred. Just don't put a lot of crap into storage and sell stuff more often.

[villman420]

doesnt matter if gods maxing out sell often or wait to sell in mass quanity, we still have to buy and sell in 100's. just make everything so much easier if 1000 was the maxx.

and do you have any ideas about what i said earlier on the nwe class name for gods above remort 100? blank sucks

[Xenos]

How about this. A revised bash recovery time.  Currently it sucks because if you want to bash before level 101 it takes too long to recover. Base rpg dely is this

Code: [Select]

%delay = Cap(101 - fetchData(%shooterClient, "LVL"), 5, 50);

At level 51 your bash recovery time is 50 seconds. Every level it decreases by one second until you get to 5 seconds where its capped. Can we add remort into that somehow. So higher remorts have a 5 second recover at level 50 or less?

[Bovidi]

It appears to be by design.  When you save your character file, it checks if you have more than $maxItem of any one item when it builds the list of your stuff.  If so, it drops you down to $maxItem.  It's a global variable in globals.cs and defaults to 500.

So, it will save a max of $maxItem (default 500) of any particular thing but will let higher quantities float in memory until you log on again.  At that point, it uses the capped item count that it saved.

From my understanding the reason why they cap it at 500 is because if you have something like 1000 of an item then you join the Tribes engine in the inventory messes up big time.  Although the server has the correct item count the player could have their inventory saying something like 215.  The Tribes inventory seems to only mess up if more than 500 items are given or taken in a few milliseconds of each other.  Although say you give 500 items, then another 500 items a second after Tribes should correct say you have 1000 items

To recreate just create a pack:
1) Create a pack with 1000 basic arrows
or if #hamalarkeyem still works
#hamalarkeyem basicarrows 1000 or however the command works again

[Xenos]

It appears to be by design.  When you save your character file, it checks if you have more than $maxItem of any one item when it builds the list of your stuff.  If so, it drops you down to $maxItem.  It's a global variable in globals.cs and defaults to 500.

So, it will save a max of $maxItem (default 500) of any particular thing but will let higher quantities float in memory until you log on again.  At that point, it uses the capped item count that it saved.

From my understanding the reason why they cap it at 500 is because if you have something like 1000 of an item then you join the Tribes engine in the inventory messes up big time.  Although the server has the correct item count the player could have their inventory saying something like 215.  The Tribes inventory seems to only mess up if more than 500 items are given or taken in a few milliseconds of each other.  Although say you give 500 items, then another 500 items a second after Tribes should correct say you have 1000 items

To recreate just create a pack:
1) Create a pack with 1000 basic arrows
or if #hamalarkeyem still works
#hamalarkeyem basicarrows 1000 or however the command works again

I've heard of problem with the inventory screen when you have numbers over 500.  Another option would be to check if they have over 500 and then automatically put anything over 500 in storage when they #savecharacter or disconnect.  If duping is elimiated then this shouldn't be exploitable.