Dx11 Auto-Flask No pixels!

[Treasure_Box]

Try sending rst (reset) packet rather than fin packet. It will close from the server immediately.

I know this is supposed to destroy the TCP season instantly, but i think the problem is, does the server try to allow for some time, so that the client can re-enumerate the connection? Because some times you die when you should not, and i think that is a result of the server trying to give the client connection some time to resend a syn before it truly kicks your client from the instance.

[rlwjr]

I hate to sound like a complete idiot (possibly) but what is "Chicken Mode" exactly?

[dlr5668]

I hate to sound like a complete idiot (possibly) but what is "Chicken Mode" exactly?

auto logout on certain HP/CI %

[rlwjr]

Gotcha, thanks!

[Treasure_Box]

I hate to sound like a complete idiot (possibly) but what is "Chicken Mode" exactly?

or maybe its just an auto quit for when your really low on life. You decide.

[moniesforyou]

auto logout on certain HP/CI %

so, put 100 for hp, and like 20 for ES (CI build)

[Treasure_Box]

so, put 100 for hp, and like 20 for ES (CI build)

no normally you want to pick one or the other, depending on build. Also you don't want to set it too low as you will guarantee a death as it takes a few milliseconds to process the request. Normally between 15%-30% of your Life/ES depending on build.

[dlr5668]

For HC I use 40% ES. Life is barely playable in HC btw. Only cheesy builds like with 200% life, 80k EV, elemental status immmune and huge secodnary defences (MoM, curses, leech, fortify, good flasks).

[moniesforyou]

no normally you want to pick one or the other, depending on build. Also you don't want to set it too low as you will guarantee a death as it takes a few milliseconds to process the request. Normally between 15%-30% of your Life/ES depending on build.

Hmm I had it set for 30% and tested w/ dot didnt work.

Should the value be a percentage or actual hp threshold?

Currently I have it set with health box empty, and "30" in the shield box. Shield selected from dropdown

[GameHelper]

I know this is supposed to destroy the TCP season instantly, but i think the problem is, does the server try to allow for some time, so that the client can re-enumerate the connection? Because some times you die when you should not, and i think that is a result of the server trying to give the client connection some time to resend a syn before it truly kicks your client from the instance.

No, that's not possible. RST packets mean client is dead and wouldn't re-enumerate the connection. It's an OS level thing ( Windows/Linux ) POE server cannot control this.
You say sometimes char dies even after sending RST packet. Only reason this can happen is that
1: There is a lag between you and server.
2: Packet was dropped in between due to network congestion
3: Server is overloaded due to lots of users and took some time to process your request
All of these are not in our control, so best option is to send the RST packet. A better approach would be to send 2-5 reset packets. In that case server will ignore other reset packets if first packet has done it's job.


Other than that I have seen that cports.exe does send the RST packet after closing the socket. So I think cports.exe (version: 2.3) would be save bet in chicken mode. Screenshots as proof of RST packet in cports.exe (Packet in Red color).

Attachment 48115

[Treasure_Box]

No, that's not possible. RST packets mean client is dead and wouldn't re-enumerate the connection. It's an OS level thing ( Windows/Linux ) POE server cannot control this.
You say sometimes char dies even after sending RST packet. Only reason this can happen is that
1: There is a lag between you and server.
2: Packet was dropped in between due to network congestion
3: Server is overloaded due to lots of users and took some time to process your request
All of these are not in our control, so best option is to send the RST packet. A better approach would be to send 2-5 reset packets. In that case server will ignore other reset packets if first packet has done it's job.


Other than that I have seen that cports.exe does send the RST packet after closing the socket. So I think cports.exe (version: 2.3) would be save bet in chicken mode. Screenshots as proof of RST packet in cports.exe (Packet in Red color).

Attachment 48115

Yes i know, I've also captured with Wire Shark. I think its mostly number 3. I live right next to my gateway so my ping is around 10ms and max 20ms (there is about 5 hops to the server for me and most of that is just moving along my ISP to the route aggregator).

The other possibility is number 2, and that would cause the server to go into a time-wait until it got an RST

[moniesforyou]

Definitely think there's something amiss with energy shield. Tested with %s and actual values, doesnt dc me

[GameHelper]

Yes i know, I've also captured with Wire Shark. I think its mostly number 3. I live right next to my gateway so my ping is around 10ms and max 20ms (there is about 5 hops to the server for me and most of that is just moving along my ISP to the route aggregator).

The other possibility is number 2, and that would cause the server to go into a time-wait until it got an RST

for 2 and 3 just send more than 1 RST. I don't know if that is possible with cports.exe.

[Treasure_Box]

for 2 and 3 just send more than 1 RST. I don't know if that is possible with cports.exe.

LOL, just DOS yourself with RST Flood.

[datz]

still dont work at all for me.. deleted settings and redid my stuff and still nothing dx11