Easy to use plugin helper for auto accepting exchange stuffs.
Useful to exchange stuffs to your party without looking both phBot windows.
Nothing much to explain, just check the plugin interface:
Download :
[Save as Link]
Do you like my plugins? Buy me a coffee!
Keep the track of my updates with xPluginUpdater
@JellyBitz hello my friend
have problem in remove button
Python Error: returned a result with an error set
and have problem in all checkboxes
(Accept all exchange invations)
Python Error: save_configs() takes 0 positional arguments but 1 was given
(Auto accecpt reply)
Python Error: save_configs() takes 0 positional arguments but 1 was given
(Auto approve reply)
Python Error: save_configs() takes 0 positional arguments but 1 was given
i looked save_config functions but i didnt see any problem…
ı click this but auto refuse all exchanges how can ı auto accept ? help me please
ı write name to list but not accept request and cannot delete name
21:25:58] Takas: Doğrulama hatası [2]
@JellyBitz auto exchange fail and show “The trade cannot be made normally”, how i can fix it?
Which Silkroad version are you using?
Try to make the exchange slowly, do not active the plugin in both characters.
vsro version,if not active both char so i need check and recheck everytime i exchange right ? 
Useful to exchange stuffs to your party without looking both phBot windows.
You just ask exchange to your party players and send the items (manually) without worry about confirm/approve from that character because it will be automatically made by plugin.
I’ll try to add a more useful feature soon like auto exchange items from inventory. 
Example: all 8 char check auto confirm
Char 1 exchange char 2 → uncheck char 1 → exchange
Then
Char 3 exchange char 2 → uncheck char 3-> exchange
Then
Char 1 exchange char 3->check char 1 → exchange
Then
Char 3 exchange char 4->uncheck 3 → exchange
that i mean, need check and uncheck to make auto exchange work
I don’t get it, not sure what’s the purpose you are using it but the errors can be about exchanging nothing or too fast. I’ll check that.
my purpose is plugin work with both char check, i just need manual put item to exchange then confirm
and i can do it on any char in my party
Just update your plugin. I changed a few stuffs, it may fix your issues.
Now it takes at count the exchange state to avoid cause conflict while using it manually.
i just test whit 2 of my char, thei are not in party.
if i exchange from main char to ssecund char and i confirm from main char, is work good.
if i confirm from secund char, is not work anymore X_O
me same
Hi @JellyBitz, are you planning the fix the issue mentioned in previous replies?
I can explain better maybe:
Assume there are 2 chars: Char1, Char2.
Case 1:
Char1 has Char2 in the exchange list.
Char1 can send manual exchange req to Char2
Char2 will automatically accept it
Char1 can manually put items and manually click approve
Char2 will automatically accept it
So far so good.
Case 2: Now let’s try sending from Char2 to Char1.
Char1 has Char2 in the exchange list.
Char2 can manually send exchange req to Char2
Char1 will manually accept it
Char2 can manually put items and click approve
It will return error (Exchange: Confirm error [2)
Case 3: Same issue but this time both has each chars in the list
Char1 has Char2 in the exchange list. Char2 has Char1 in the exchange list.
Char2 can manually send exchange req to Char2
Char1 will automatically accept it
Char2 can manually put items and click approve
It will return error (Exchange: Confirm error [2)
hi @JellyBitz
in my case still have problems when i want to exchange whit 2 chars who have all 3 options check. sometine is work fine, sometine no:S
maibe is you add a delay on confirm?
After having launched this Plugin a lot, the same error that happens with everyone previously, still continues today.
No updates to fix.
This plugin is wonderful, because it speeds up the whole “Alt+Tab” process.
Works perfect on csro-r files… But i want you to do something. Could you make the same thing but not required any party.
That’s not possible, you need the player ID which is only possible to get through the get_party API.
