they ban only sellers and cheatersI will say that this is *usually* true, and I used to say it was 100% true, but after introduction of the WOW token, I know a couple of people, my brother being one of them, who got banned for being a "repeat" buyer. They try to target very specific hacks and bots and user groups with their bans.īullshit, blizz dont ban buyers. There are endless examples of players Blizzard would not desire to ban that would get banned in blanket-catches. People using friends tools for harmless features (such as a deaf friend who uses my text-to-speech plugin) could unknowingly be using more abusive features For example if my friend got a new version from me and did not turn off some default stuff, he could easily have the auto-rebuff cast his buff on injection with lua and then realize it and turn it off but it would be to late. People who write tools or experiment with them solely for fun and learning and never use them to gain any meaningful advantages on Live who could catch undeserved bans in such blanket-catches as well.Ģ. Some examples of people I would imagine they would prefer not to hit in mass-blanket bans:ġ. I would make a guess and say the reason they would like to avoid such blanket tactics is it will inevitably catch a lot of harmless 'cheaters'. They are making a choice not to do blanket detection's like that. They're not incapable of hiring anti-cheat help that could implement that, I assure you.
They would really prefer not to blanket ban every single person that uses some part of their games memory such as a function pointer or memory reads/writes. I would say packet based is the way to go atm.Believe it or not blizzard takes great care to be very specific with who their ban waves target. I dont see why they dont hook a handfull of common apis like Spell_C_CastSpell, they could nail people calling it directly and people using the lua wrapped version.
After everyone moves away from that Blizz will just start hooking game functions and doing the same thing. Most bots use lua so thats what they are hooking. Same result (minus variable access, which seems kinda useless to me.)Īgain dont think your safe calling apis directly. is, ask yourself if it's really that hard to fake a lua state to call Script_* functions with. Packet.ClientServices_s_currentConnectionĬlientDB.WowClientDB_Base_GetRecordDataUnsafeĬlientDB.WowClientCompressedDBCache_CreatureDisplayInfoExtraRec_GetRecordĬlientDB.WowClientCompressedDBCache_GameObjectDisplayInfoRec_GetRecordĬlientDB.WowClientCompressedDBCache_ItemDisplayInfoRec_GetRecordĬlientDB.WowClientCompressedDBCache_SpellEffectRec_GetRecordĬlientDB.WowClientCompressedDBCache_SpellRec_GetRecordĬlientDB.WowClientCompressedDBCache_FileDataRec_GetRecordĬlientDB.WowClientCompressedDBCache_FileDataCompleteRec_GetRecord (Sorry for the sorting, it's something I've been meaning to get around to)Įdit: Before people start telling me how useful Lua execution etc. Packet.NetClient_ClientConnectionConnectToHandler Interface.CCharacterSelection_s_selectionIndex Interface.CCharacterSelection_s_characterList Interface.ClientServices_m_selectRealmInfo Interface.CGMailInfo_GetMailItemAttachment Interface.CGPlayer_C_AcceptOrUnacceptTrade Interface.CGLookingForGroup_ProposalResponse Interface.CGGossipInfo_SelectGossipOption PartyManager.CGParty_OnGroupMemberRemoved
ObjectData.g_baseDynamicObjectDescriptors
ObjectManager.CGUnit_C_OnSetRawFacingLocal ObjectManager.CGGameUI_m_currentObjectTrack ObjectManager.ClntObjMgrEnumVisibleObjectsPtr ObjectManager.ClntObjMgrGetActivePlayerObj CMovement_C_SendMoveMessage_PlayerMoveFallLandĬGSpecializationInfo_m_activePlayerTalents
0 kommentar(er)
