SWG Inventory Sorter : Star Wars Galaxies Premium Cheats

You removed the [_ItemDeleteActions] section, most likely. If not, I'll need the full info on what it says with the error.

If the former is the case, please read the OP entirely again.

Seems to be working now. How do I stop the script while in-game?

The pause key.

Looks like I won't be working on this one for a while, so if anyone wants the source to look at it and maybe contribute any fixes send me a PM.

As a disclaimer, it's fine for anyone to post their modified versions, but keep it in this thread unless you do a complete overhaul.
For the latter, please provide credit where credit is due.

Seems that i cant get this to work anymore, getting a message "you dont have permission to access this container" everytime the scripts tries to delete something. Any idea what this could be?

You're running it indoors while it was made to be ran outdoors, so it's trying to drop things instead of hitting the destroy key.

In the config up all the _ItemDeleteActions up by one except the one that's currently 0.

damn i didnt know that caves was counted as indoors, bah i have been about to go nuts over this the last 2 days and it was that damn simple:P thanks

As long as there's "drop" in the radial menu it's counted as indoors

Any idea if work will continue on this? Was looking forward to getting the no RAA being moved fixed.

rugburn wrote:Any idea if work will continue on this? Was looking forward to getting the no RAA being moved fixed.

What is RAA?

Random Attributes Affected

This is in reference to my post on the first page. Basically the script is moving all isomerace with no random attributes affected stat.

rugburn wrote:Random Attributes Affected

This is in reference to my post on the first page. Basically the script is moving all isomerace with no random attributes affected stat.

So if it is a guarantied affect like health it gets moved also?

Sorry about the redundant questions. I haven't used this or read the comments in the thread. I might get a look at it tonight.

OK, in my first round of testing you can add:

GUARANTEED.* IE 2=(LYASE ENZYME|GUARANTEED.*|BEAST MASTER MISCELLANEOUS|FURNITURE|GENERIC ITEM|FISHING BAIT|COLLECTION|CHRONICLE RELIC.*)$

to line 2 and most of the lyase with the word guaranteed get deleted and not moved.

It still seems to have a problem with lyase that do not have any RAA

So in testing with this change

/will delete
Random Attributes Affected:8
Guaranteed Attribute Affect=Health

/will delete
Guaranteed Attributes Affected=1
Guaranteed Attributes Affected=Health

/will MOVE and I'm not sure why at this point
Guaranteed Attributes Affected=Health


Is there such a lyase as

Random attirbutes affect=11
Guaranteed attribute affect=health


If there is I believe those might also get deleted.

I'm sure this is just an issue with finding the right text to enter in the save delete areas.

Big HI5 to r04r on this one. This is a pretty nice script. The ONLY thing keeping this from being "legendary" in my book, is making it work when the SWG windown doesn't have focus but I know that's a limitation of autoit. Multi client support too, but with out the first part that is useless.

Great work r04r!

One question (without reading the regex stuff)

Will GUARANTEED.* include GUARANTEED ATTRIBUTE AFFECTED: I assume so.

The part that I'm having issues with is things that can fall into two delete options but have the same name.

IE: BODYSUIT

There are normal body suits that would go under 4 for delete, but there are Ithorian body suits that say humans/zabs/trandos can't wear so they fall under 3. Since the game has them all as body suits the Ithorian body suits get sent a 4 and never get deleted so it breaks the program.

Might need to look at adding something that checks for item description and if the same item is there more then 4 times in a row it goes to the next highest delete order and sends that one time.

And now, strangely enough, I'm getting the default "don't know how to delete this" message but it's not giving the item name to add either.

Even worse, this is on a machine that was working fine in my testing.