deleted issue about enet-socks5 HOT 33 CLOSED

this is what im talking about, this is something I can do that you can't so easily, without mixing stuff up within ENet itself and making it not generic-purpose for those who dont even want to use this for GT (unless you start doing it like me with the SocksTunnel)

from enet-socks5.

from enet-socks5.

Maybe just coincidence bro, but our 10k bots literally can connects perfectly

from enet-socks5.

would like to see proof

from enet-socks5.

I can definitely show a picture of proxyrack 10k clients being connected, but you can test for yourself

from enet-socks5.

ok sec

from enet-socks5.

• gt doesnt check for ip shit they only check for meta which lasts 1 minute

maybe they will soon, GTPS3 def does as of rn

from enet-socks5.

also literally i can #define HAS_POLL lol.. and enet will use epoll shit you talked

from enet-socks5.

ofc you can lol... but u didnt, so do that - you will still be inferior in 4 other aspects

from enet-socks5.

does this look like "ENET-OPTIMIZATION" or "ENET-SOCKS5"

from enet-socks5.

also about the framework shit, this is not a repo for "growtopia enet framework bot" shit, this is clearly just enet with socks5 protocol support

from enet-socks5.

HAS_POLL will allow you to have more than 1k per program so you should prob do that, but yeah enet-socks5 it is I guess but it'd be better if it at least worked on GTPS3, you need the http tunnelling for that and maybe even soon for GT or already, I personally encountered shadowbans when not doing so

from enet-socks5.

also about the framework shit, this is not a repo for "growtopia enet framework bot" shit, this is clearly just enet with socks5 protocol support

Understood.

from enet-socks5.

yours are clearly has a purpose for growtopia bot thingy, maybe consider renaming the repo to "growtopia bot socks5" and not just "enet-socks5" and complaining to other repo why they dont have a framework

from enet-socks5.

Have you checked mine out?

from enet-socks5.

i did, its literally intended for growtopia-bot purpose whereas mine is just enet with socks5 protocol support

from enet-socks5.

yours are clearly has a purpose for growtopia bot thingy, maybe consider renaming the repo to "growtopia bot socks5" and not just "enet-socks5" and complaining to other repo why they dont have a framework

but then I mean you also have ubisoft enet protocol so this is kinda self-contradictionary

from enet-socks5.

i agree, but atleast it's just pure enet without any things

from enet-socks5.

and renaming it to "enet socks5 with ubisoft protocol support" will make the repo name longer :D

from enet-socks5.

would like to see proof

This is a sample bot running over nordvpn-proxy

from enet-socks5.

There are 2 messages suddenly

from enet-socks5.

we sent the same image, so he deleted

from enet-socks5.

Is the meta grabbed locally or via socks5

from enet-socks5.

If its grabbed locally it is proof then that gt doesnt need it

from enet-socks5.

otherwise GTPS3 wont work with that ig but I guess it doesnt matter

from enet-socks5.

Closing issue. The library referenced in this repository works in real GT.

from enet-socks5.

• just saying joining once for few secs doesnt mean you wont get shadowbanned later on

from enet-socks5.

• just saying joining once for few secs doesnt mean you wont get shadowbanned later on

that's on you

from enet-socks5.

Kk also out of context but why does it say I got help from proxyrack and I got discredited etc.? If you look at my work, you will notice it's actually just made using the docs and maybe some sips of help from github and 1x stackoverflow isnt it a bit unnecessary? I mean I get that maybe the intention was to provocate, but I mean I kinda don't need to see my name elsewhere already

from enet-socks5.

What even is a customer potential policy, I mean I wouldn't start doing the same saying on my repo that this disclaimer is bullshit because that would be like shooting myself in the head

from enet-socks5.

@AboodTBR check ur discord if u want me to shut up ultimately

from enet-socks5.

actual fucking manchild

from enet-socks5.

My implementation outperforms this repo and Olli's implementation (recently published on github) massively in especially 5 aspects:

1. The fact that my implementation has an actual framework
2. My implementation has a very high-performance, extremely multithreaded, multi-clustered architecture
3. My implementation has custom ENet tweaks (such as lower ping frequency to save bandwidth & CPU), other optimizations
4. My implementation allows for more than 1024 sockets to be opened (go try yourself and you will see what I mean), that's because I make use of poll() instead of the default select() in ENet, select() only allows for 3 bits of data per file descriptor, meaning you should get segmentation faults when trying to spawn more than 1024 bots. With my implementation, you can go full 64K (32K for udp, and 32k for the socks5 tcp implementation)
5. Lastly, my implementation actually works up-to-date because you will get shadowbans on THIS as opposed to mine because you dont visit the webserver before to 1. grab meta and 2. making a request to growtopia1.com/growtopia2.com is necessary to avoid shadowbans, and you can't easily do it in your implementation because your socks5 stuff isn't separated, it is embedded right into ENet itself which doesn't really give much headroom to do anything else from within the socks5 connection, to get its proxy IP on the webserver and not your own local ip as if you were to visit the page normally.

🤓

from enet-socks5.