MQ2SuperStacker for the 5/16 compile

[Warrene]

This was a straight re-compile, no code changes. Successfully tested using Redquest's 10.1 compile.
.
.
.
...and if posting this is breaking any rules, will a moderator please delete the thread. I get soooo confused!!!

 

[fierymomof2]

Woohoo my forager is rejoicing! Redcent incoming!

 

[Jetanroth]

Is this plugin considered an "active hack" or is it safe still?

**I ask cuz it seems like whenever Im manipulated stacks that have been stacked outside their normal peramiters with SuperStacker I get "Disconnected" No CTD just Disconnected. It seems odd. **

 

[vladus2000]

I'd consider it an active hack, as for whether or not its "safe" to use, it shouldn't be sending any of its own packets, so that part of it should be alright, I guess it depends if they added tracking to this sort of thing.

 

[golem]

Ive had the same thing happen batweed not sure if there tracking it but to be safe ive discontinued use at the moment just in case

 

[Warrene]

Is this plugin considered an "active hack" or is it safe still?

**I ask cuz it seems like whenever Im manipulated stacks that have been stacked outside their normal peramiters with SuperStacker I get "Disconnected" No CTD just Disconnected. It seems odd. **

I've had a CTD at times, but it pre-dates any of their new stuff. Essentially, it's bad timing....pulling an abnormal size of a stack and immediately dropping it onto that same stack is a recipe for CTD. The stack sizes are being constantly checked, but bad timing can throw a size into the negative. Auto-tradingskilling is another example. Pulling from a superstack will blow up once you use up the normal size...even though your client thinks there are more, the TS engine doesn't know about them. I always "de-construct" my superstacks to normal sizes before starting alot of TS. If not, you'll CTD and poof your remaining stack.

...but caution is always better. If your gut tells you don't use this, don't.

 

[Jetanroth]

aye I stopped using it after the 4th Disconnect. Its just too odd that it just boots me out to server select and not a full CTD. Checking my e-mail for a warning from SoE.

 

[pms]

You can only pull off three sizes of stack from a SuperStack: the whole stack (up to 5million in this plugin) or the max legal size on the server (20 or 100). Alternatively you can CTRL-click and pull off one at a time. If you try to split a SuperStack by using anything but those three numbers, you will not have a legal stack. Sometimes it will make you LD and sometimes it will not, but if you try to trade your new "split" superstacks with anyone, you will notice your original stack still has the superstack amounts, but the new stack you split off will reduce to the max legal size (20 or 100).

Anywhere you see:

StackSize = 5000000

...in the source, you can reduce that to whatever you want, just make sure all the values are the same to avoid conflict. The trick is that if you make a superstack of 5million and then use a plugin that allows for only say, 1000, you can split off 1000 at a time from the 5 million stack by shift-clicking with the new plugin loaded. So you could compile this plugin, and then change the stacksize's to be 1000 and name that superstacker1000 and then one that is 500 and name that superstacker500 etc, then load the big one, make a very large stack with it, UNLOAD it first and then load the new one to be able to shift-click off 1000 at a time without going LD.

I'm sure this could be easily implemented into one plugin using the command line to change the values on the fly if anyone has the drive, I certainly don't.

 

[rodmapstone]

anyone else CTD after loading this gem following patch the other day?