OP
OP
yasueh
OG
Re: Yasueh's Macros and Addons for F2P
I guess I could have the addon whisper people on the friends list to ask for the channel they're using, in case the default channel ever becomes locked. Would work well enough for people who are online regularly, although completely new players would still be unable to find the channel name.
I wish Blizzard would support a way to make addons more secure. They probably can't work with compiled or obfuscated code, because we'd have to submit separate source and object code, and someone would have to be paid to check all the source over to make sure nothing malicious was submitted (I'm not entirely sure how thorough Curse's checks are, or if their people are paid, although they do make enough money from hosting addons to give a little back to the authors).
What they could do instead is have the game client run a hash on an addon's folder, and then whenever an addon communicates with the same addon being used by another player, that checksum is provided as an additional field in the addon-to-addon message, so that addons can decide to accept or reject incoming data, based on whether or not a player has made changes to their own copy of an addon.
It wouldn't stop the most determined of hackers, but they would have to modify the game client to send false hashes, instead of just being able to modify the addon code to send false data.
---
If I was to make an arena rating addon, then it would merely collect data to be sent to a web server by a separate executable, kind of like how the Wowhead addon needs a separate uploader. Ratings for each match would only be considered valid if all participants submitted matching data, as well as screenshots of the final scoreboards (and you could even crowdsource checking the scoreboards, by using them as a captcha for the website).
I guess I could have the addon whisper people on the friends list to ask for the channel they're using, in case the default channel ever becomes locked. Would work well enough for people who are online regularly, although completely new players would still be unable to find the channel name.
The code had to be obfuscated (made unreadable in a way that still allows it to function) for the addon to have a chance at being "secure". This is now prohibited by Blizzard's addon policy though, so there'd be no way to stop people changing their ratings if/when I update it
I wish Blizzard would support a way to make addons more secure. They probably can't work with compiled or obfuscated code, because we'd have to submit separate source and object code, and someone would have to be paid to check all the source over to make sure nothing malicious was submitted (I'm not entirely sure how thorough Curse's checks are, or if their people are paid, although they do make enough money from hosting addons to give a little back to the authors).
What they could do instead is have the game client run a hash on an addon's folder, and then whenever an addon communicates with the same addon being used by another player, that checksum is provided as an additional field in the addon-to-addon message, so that addons can decide to accept or reject incoming data, based on whether or not a player has made changes to their own copy of an addon.
It wouldn't stop the most determined of hackers, but they would have to modify the game client to send false hashes, instead of just being able to modify the addon code to send false data.
---
If I was to make an arena rating addon, then it would merely collect data to be sent to a web server by a separate executable, kind of like how the Wowhead addon needs a separate uploader. Ratings for each match would only be considered valid if all participants submitted matching data, as well as screenshots of the final scoreboards (and you could even crowdsource checking the scoreboards, by using them as a captcha for the website).
9: in function `F2PData_SendMyData_ToAll'
