GearSwap - Re-enabled

The day that SE bans solely for Windower is the day they might as well shut the servers down. The latter will happen first.

Not to rock the boat or anything here but I always see windower guys saying you're safe there's no way SE could know you're using windower... I use windower, but I guarantee you SE allows it right now and has many methods they could use to figure out if you use it or not. An easy way off the top of my head is just realize that the pattern of packets sent out, while valid, will have different patterns than the ones sent out by the native client and equip sets. Consider it a fingerprint for lack of a better word. You might say that that's too advanced! Or whatever. But no it's really not, besides just monitoring for impossible actions like large sets of gear changed within 1 second, you can look at the number of gear changes made in a small time, and there's many other indicators. Like the large number of people that crash after an update, for example, and oh they also send out a ton of gear changes that our equipsets don't allow and... there's lots of ways. And knowing these you could very well turn packet data received from the client into a visual medium, just like they do with the CIA and looking through cell phone binary code, you don't have to know what it is, just by how it is represented in a physical medium, you can learn pattern recognition because all processor binaries look this way and networking code binaries look this way... and packets sent from a client using this software looks this way and packets sent from the native look this way. There's patterns there and there's nothing the windower team can do to change that, other than simulating packet for packet and having all the same limitations that the in game equipsets do, and even then they are different entities. I really appreciate your work on it and I think it's great you do it and I like to use it. But I simply know it's a false statement to say that there's no way for SE to know you're using it. Because there are tons. So lets just be honest about it shall we? We can use it cause SE has allowed it. And probably because if they didn't they'd lose half their subs.

... because if they didn't they'd lose the rest of their subs.

Okay, I didn't have all the libraries I needed included, but all the results so far have been expanding our list of action types rather than our knowledge of the strange new bytes. Here is an updated version:

https://www.dropbox.com/s/a7lweujwsxgogzp/action_monitor.lua?dl=0

I pushed a version live that works again to go along with Arcon's LuaCore changes. No one has documented anything but 00s in the last 12 bytes of the action packet.

What are they up to?

Trying to look into it. Are you guys R0ing and DCing, getting an error and disconnected, or getting a crash to desktop?

I don't use autojoin, but have distance on. keybinds work, and everything else appears to be working properly. Although Im in a BC right now where LS mate keeps dc'ing, perhaps related, ill ask when they log back in.

Okay, I just auto crashed all the way out when trying to call a trust. Despite not being leader.

LS Mate said they were trying to call a pet (BST) both times that forced the crash.

*Edit: For what it's worth, my offensive mode triggers (Mote .lua) doesn't crash me on Dnc.

Trying to look into it. Are you guys R0ing and DCing, getting an error and disconnected, or getting a crash to desktop?