What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[Plugin] Chicken based on TCP Disconnect

Heilmann

Member
Joined
Feb 7, 2010
Messages
61
Hello Community,

Since the ESC and Logout killed me many times, I've decided to implement a TCP Disconnect. This method of disconnecting is the fastest way to disconnect PoE, as far as I know. Even faster than using Currports.

Most of the code is from PoEHUD/AutoQuit, they took the code from lutbot. All credits go to Lutcikaur (http://lutbot.com/#/).

Introductions: Make sure that you run Exilebuddy as Administrator!

If you have problems, check the log file for the following entry:
Good - [Chicken] SetTcpEntry. Return-Value: "0".
Bad - [Chicken] SetTcpEntry. Return-Value: "317". --> Run Exilebuddy as Administrator!

I'm not a developer, I'm doing this for fun, code could be messed up.

Kind Regards
Heilmann
 

Attachments

Last edited:
dont work for me, i start EB in admin mode but wont chicken out when under the hp%. any clue what it can be?
 
I don't die often, but when I do it's usually 5% from leveling. I'll give this a shot and see how it works! Running as administrator now. Thanks a lot for the contribution!!
 
Not working. It says it's going to chicken then proceeds to where it was normally going. Some examples (I'm running as Admin.)

2018-01-01 13:39:54,639 [25] WARN Logger - [Chicken] Now chickening because our HP (2%) is below threshold (25%)
2018-01-01 13:39:54,662 [25] INFO Logger - [Logic] Now moving towards {1452, 2312} because [dist (36) > MaxRangeRange (35)]
------
2018-01-01 13:40:42,791 [25] WARN Logger - [Chicken] Now chickening because our HP (12%) is below threshold (25%)
2018-01-01 13:40:42,846 [25] INFO Logger - [Logic] Now moving towards the monster Well Creeper because [canSee: False][pathDistance: 8.496977][blockedByDoor: False]
------
2018-01-01 14:08:40,227 [25] WARN Logger - [Chicken] Now chickening because our HP (15%) is below threshold (25%)
2018-01-01 14:08:40,259 [25] INFO Logger - [Logic] Now moving towards the monster Prayer Guard because [canSee: False][pathDistance: 30.13256][blockedByDoor: False]
------
2018-01-01 14:12:16,720 [25] WARN Logger - [Chicken] Now chickening because our HP (15%) is below threshold (25%)
2018-01-01 14:12:16,786 [25] WARN Logger - [Chicken] Now chickening because our HP (18%) is below threshold (25%)
2018-01-01 14:12:16,843 [25] INFO Logger - [UpdateObstacles] Update => Success
2018-01-01 14:12:16,847 [25] WARN Logger - [Chicken] Now chickening because our HP (20%) is below threshold (25%)
2018-01-01 14:12:16,900 [25] WARN Logger - [Chicken] Now chickening because our HP (23%) is below threshold (25%)
2018-01-01 14:12:17,017 [25] INFO Logger - [UpdateObstacles] Update => Success
2018-01-01 14:12:18,032 [25] INFO Logger - [UpdateObstacles] Update => Success
2018-01-01 14:12:18,723 [25] DEBUG Logger - [FinishCurrentAction][True] Waited 0 ms for the action to finish Cyclone.
 
Not working. It says it's going to chicken then proceeds to where it was normally going. Some examples (I'm running as Admin.)

2018-01-01 13:39:54,639 [25] WARN Logger - [Chicken] Now chickening because our HP (2%) is below threshold (25%)
2018-01-01 13:39:54,662 [25] INFO Logger - [Logic] Now moving towards {1452, 2312} because [dist (36) > MaxRangeRange (35)]
------
2018-01-01 13:40:42,791 [25] WARN Logger - [Chicken] Now chickening because our HP (12%) is below threshold (25%)
2018-01-01 13:40:42,846 [25] INFO Logger - [Logic] Now moving towards the monster Well Creeper because [canSee: False][pathDistance: 8.496977][blockedByDoor: False]
------
2018-01-01 14:08:40,227 [25] WARN Logger - [Chicken] Now chickening because our HP (15%) is below threshold (25%)
2018-01-01 14:08:40,259 [25] INFO Logger - [Logic] Now moving towards the monster Prayer Guard because [canSee: False][pathDistance: 30.13256][blockedByDoor: False]
------
2018-01-01 14:12:16,720 [25] WARN Logger - [Chicken] Now chickening because our HP (15%) is below threshold (25%)
2018-01-01 14:12:16,786 [25] WARN Logger - [Chicken] Now chickening because our HP (18%) is below threshold (25%)
2018-01-01 14:12:16,843 [25] INFO Logger - [UpdateObstacles] Update => Success
2018-01-01 14:12:16,847 [25] WARN Logger - [Chicken] Now chickening because our HP (20%) is below threshold (25%)
2018-01-01 14:12:16,900 [25] WARN Logger - [Chicken] Now chickening because our HP (23%) is below threshold (25%)
2018-01-01 14:12:17,017 [25] INFO Logger - [UpdateObstacles] Update => Success
2018-01-01 14:12:18,032 [25] INFO Logger - [UpdateObstacles] Update => Success
2018-01-01 14:12:18,723 [25] DEBUG Logger - [FinishCurrentAction][True] Waited 0 ms for the action to finish Cyclone.
Hello dirin,

The user Biffin has the same problem. I've send him a new version with more log messages, currently I don't know why this is happening.

https://mega.nz/#!vF8zVSZZ!hly0OAWNEumWV9FYV96TCIFz9MU7jbnGyOFoB9fZGEQ
Download this version and post the log. Maybe it is related to UAC, but I don't know.

Kind Regards
Heilmann
 
Hello Community,

Since the ESC and Logout killed me many times, I've decided to implement a TCP Disconnect. This method of disconnecting is the fastest way to disconnect PoE, as far as I know. Even faster than using Currports.

Most of the code is from PoEHUD/AutoQuit, they took the code from lutbot. All credits go to Lutcikaur (http://lutbot.com/#/).

Introductions: Make sure that you run Exilebuddy as Administrator!

If you have problems, check the log file for the following entry:
Good - [Chicken] SetTcpEntry. Return-Value: "0".
Bad - [Chicken] SetTcpEntry. Return-Value: "317". --> Run Exilebuddy as Administrator!

I'm not a developer, I'm doing this for fun, code could be messed up.

Kind Regards
Heilmann

Can we disconnect under 70% ES? the higher i can actually is 50% ES
 
the reason why this is not working for certain people as it was not working for me is because we are using the steam client, edit this line.
Process[] processes = Process.GetProcessesByName("PathOfExile"); <-- stand-alone client
Process[] processes = Process.GetProcessesByName("PathOfExileSteam"); <-- steam client
 
Back
Top