BlackBrony wrote: » In before Noanni "addons can't be avoided, there will be a combat tracker whether IS likes or not"
Kahvipaussi wrote: » I was just logging off World of Warcraft's Season of Discovery, and i got reminded of the devastating effects of addons. I still remember how the slippery slope started in Vanilla, with the usual excuses of just having better UI and accessibility. Fast forward to the current day, and you see a game that has been turned into a conveyor belt single-player experience. Quest addons that bypasses the reasons why the quests exist in the first place. Addons that tell you information about the game you shouldn't have access to. Like enemy player hp,buffs and their durations. Addons force the game devs to start designing raids and bosses around existing addons, making them garbage. It is not an exaggeration that addons will destroy this game if they are allowed to be used.
Taerrik wrote: » Noanni, before you get mad at me. I am actually in support of having dps meters, but seeing as the rules are clear here, I will simply stick with just parsing the provided combat log for the information I need.
Noaani wrote: » This is all ACT does. It doesnt intercept network traffic at all. All plugins for ACT do is act as a translation layer between the format of the games combat log and ACT. You "could" write an application to read network traffic and then transfer that to a log file in a format ACT can read (via a plugin), but then it is this second applocation that is reading the network traffic, not ACT.
Taerrik wrote: » Its a cheater app now, when before it was only a DPS meter.
Noaani wrote: » Taerrik wrote: » Its a cheater app now, when before it was only a DPS meter. You know you wouldn't be able to say this without me calling it out. Here, I'll link you a version history of every ACT release since 2011. Show me which one adds functionality to read network traffic. I'd happily accept even just an update to that functionality. Now, since you can't do that (can't show me something that doesn't exist), I'll instead tell you what has probably happened. What has probably happened is that you have come across either an installer for ACT for what ever game you are playing, and that installer also installs plugins for ACT that have the functionality you talk about, OR you have simply followed instructions to install ACT and a number of plugins which has bought you to the same outcome. So, essentially, it isn't a case of ACT being a "cheater app", but rather the way it is being used is functioning as such. Now, the issue I have is that this applies to literally any application. You can use a web browser to do basically the same thing, you could write a plugin for Excel to literally read network traffic and parse out the information just as ACT does (a combat parser is basically just a spreadsheet). The thing is, in both cases you don't then label the application as being a "cheater app", because it is blatantly obvious that it is the specific use case of the application that is "cheating". What you seem to be missing is that this also applies to ACT - it isn't that ACT is a "cheater app" - it just could be considered cheating based on the way you are using it. With that being the case, don't blame the application, blame the user. When I use ACT it does not and can not read network traffic. If it is doing that when you use it, that is on you, not on ACT.
Depraved wrote: » Noaani wrote: » Taerrik wrote: » Its a cheater app now, when before it was only a DPS meter. You know you wouldn't be able to say this without me calling it out. Here, I'll link you a version history of every ACT release since 2011. Show me which one adds functionality to read network traffic. I'd happily accept even just an update to that functionality. Now, since you can't do that (can't show me something that doesn't exist), I'll instead tell you what has probably happened. What has probably happened is that you have come across either an installer for ACT for what ever game you are playing, and that installer also installs plugins for ACT that have the functionality you talk about, OR you have simply followed instructions to install ACT and a number of plugins which has bought you to the same outcome. So, essentially, it isn't a case of ACT being a "cheater app", but rather the way it is being used is functioning as such. Now, the issue I have is that this applies to literally any application. You can use a web browser to do basically the same thing, you could write a plugin for Excel to literally read network traffic and parse out the information just as ACT does (a combat parser is basically just a spreadsheet). The thing is, in both cases you don't then label the application as being a "cheater app", because it is blatantly obvious that it is the specific use case of the application that is "cheating". What you seem to be missing is that this also applies to ACT - it isn't that ACT is a "cheater app" - it just could be considered cheating based on the way you are using it. With that being the case, don't blame the application, blame the user. When I use ACT it does not and can not read network traffic. If it is doing that when you use it, that is on you, not on ACT. but if the app can be used to cheat through plugins, shouldnt we prevent the app from being used? or at least make it illegal? how can we know if a user is using the app to cheat or not? you cant know what plugins they installed.
BlackBrony wrote: » Depraved wrote: » Noaani wrote: » Taerrik wrote: » Its a cheater app now, when before it was only a DPS meter. You know you wouldn't be able to say this without me calling it out. Here, I'll link you a version history of every ACT release since 2011. Show me which one adds functionality to read network traffic. I'd happily accept even just an update to that functionality. Now, since you can't do that (can't show me something that doesn't exist), I'll instead tell you what has probably happened. What has probably happened is that you have come across either an installer for ACT for what ever game you are playing, and that installer also installs plugins for ACT that have the functionality you talk about, OR you have simply followed instructions to install ACT and a number of plugins which has bought you to the same outcome. So, essentially, it isn't a case of ACT being a "cheater app", but rather the way it is being used is functioning as such. Now, the issue I have is that this applies to literally any application. You can use a web browser to do basically the same thing, you could write a plugin for Excel to literally read network traffic and parse out the information just as ACT does (a combat parser is basically just a spreadsheet). The thing is, in both cases you don't then label the application as being a "cheater app", because it is blatantly obvious that it is the specific use case of the application that is "cheating". What you seem to be missing is that this also applies to ACT - it isn't that ACT is a "cheater app" - it just could be considered cheating based on the way you are using it. With that being the case, don't blame the application, blame the user. When I use ACT it does not and can not read network traffic. If it is doing that when you use it, that is on you, not on ACT. but if the app can be used to cheat through plugins, shouldnt we prevent the app from being used? or at least make it illegal? how can we know if a user is using the app to cheat or not? you cant know what plugins they installed. But HOW WILL I PLAY THE GAME WITHOUT THE NUMBERS, IT'S IMPOSSIBLE!
Depraved wrote: » Noaani wrote: » Taerrik wrote: » Its a cheater app now, when before it was only a DPS meter. You know you wouldn't be able to say this without me calling it out. Here, I'll link you a version history of every ACT release since 2011. Show me which one adds functionality to read network traffic. I'd happily accept even just an update to that functionality. Now, since you can't do that (can't show me something that doesn't exist), I'll instead tell you what has probably happened. What has probably happened is that you have come across either an installer for ACT for what ever game you are playing, and that installer also installs plugins for ACT that have the functionality you talk about, OR you have simply followed instructions to install ACT and a number of plugins which has bought you to the same outcome. So, essentially, it isn't a case of ACT being a "cheater app", but rather the way it is being used is functioning as such. Now, the issue I have is that this applies to literally any application. You can use a web browser to do basically the same thing, you could write a plugin for Excel to literally read network traffic and parse out the information just as ACT does (a combat parser is basically just a spreadsheet). The thing is, in both cases you don't then label the application as being a "cheater app", because it is blatantly obvious that it is the specific use case of the application that is "cheating". What you seem to be missing is that this also applies to ACT - it isn't that ACT is a "cheater app" - it just could be considered cheating based on the way you are using it. With that being the case, don't blame the application, blame the user. When I use ACT it does not and can not read network traffic. If it is doing that when you use it, that is on you, not on ACT. but if the app can be used to cheat through plugins, shouldnt we prevent the app from being used?
Noaani wrote: » Depraved wrote: » Noaani wrote: » Taerrik wrote: » Its a cheater app now, when before it was only a DPS meter. You know you wouldn't be able to say this without me calling it out. Here, I'll link you a version history of every ACT release since 2011. Show me which one adds functionality to read network traffic. I'd happily accept even just an update to that functionality. Now, since you can't do that (can't show me something that doesn't exist), I'll instead tell you what has probably happened. What has probably happened is that you have come across either an installer for ACT for what ever game you are playing, and that installer also installs plugins for ACT that have the functionality you talk about, OR you have simply followed instructions to install ACT and a number of plugins which has bought you to the same outcome. So, essentially, it isn't a case of ACT being a "cheater app", but rather the way it is being used is functioning as such. Now, the issue I have is that this applies to literally any application. You can use a web browser to do basically the same thing, you could write a plugin for Excel to literally read network traffic and parse out the information just as ACT does (a combat parser is basically just a spreadsheet). The thing is, in both cases you don't then label the application as being a "cheater app", because it is blatantly obvious that it is the specific use case of the application that is "cheating". What you seem to be missing is that this also applies to ACT - it isn't that ACT is a "cheater app" - it just could be considered cheating based on the way you are using it. With that being the case, don't blame the application, blame the user. When I use ACT it does not and can not read network traffic. If it is doing that when you use it, that is on you, not on ACT. but if the app can be used to cheat through plugins, shouldnt we prevent the app from being used? Only if this applies across the board. I can create a plugin for Excel to do exactly the same thing. Does this mean Intrepid shouldnt let anyone run the game with Excel running as well? Discord has been used to facilitate unintended gameplay for years, should that also be banned? What about the windows command prompt? Should Intrepid also ban that from being open at the same time as the game client? Or are we only going to ask them to "ban" applications from smaller developers that dont have the resources to fight back? Then we could get in to the logistics of how - do you want Intrepid to know every application you have running on your computer, and exactly what that application is doing?