Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About wakai

  1. Known Issue: Server Login/Select Issue

    Sadly, no one has said that the issue can be solved by Wednesday restart. Selective IP address filtering sounds like cybersecurity system related and if they have an outside vendor servicing that, this could drag on for a while...
  2. Banned Accounts?

    You are correct in the sense that it is a piece of software, it was created by a third party and it affects the game. But l2 rules of conduct say this: So they refer to third-party programs as a separate category from game modifications. The reason why this matters is when they list 3rd party software as ban reason, they most likely mean #21 only.
  3. Banned Accounts?

    Let's draw a distinction between memory on disk (= C:/path/to/l2/folder) and memory in RAM (= running l2.bin application). Unless contents of a given file on disk are loaded into l2.bin they can't have an effect on the game. So what happens when l2.bin tries to load, let's say, some settings.ini file that contains the max camera zoom? At a high level, l2.bin determines the path of the required file (= C:/path/to/l2/folder/settings.ini) l2.bin sends a 'read file' request to Windows to retrieve the contents of the file at that path If Windows finds the file and l2.bin has a 'read' permission for that file, Windows provides the file contents to l2.bin. Otherwise, the request fails and l2.bin has to try again Upon success, a copy of the contents of settings.ini (or some portion of it) is now a part of l2.bin's memory. Let's say those contents are 'key=value' pairs separated by new lines, like l2.bin knows (from its code and current state of execution) which keys it needs, which in our case is min/maxCameraZoom. So it looks through the contents and if it finds them, it saves the values. Let's say l2.bin has in memory that current cameraZoom=950 (this is the value that determines what you see). Now you use the scroll wheel on your mouse and l2.bin receives a request to increase cameraZoom by delta = 100 l2.bin sets the value of cameraZoom = minimum(cameraZoom + delta, maxCameraZoom), which in this case, = minimum(950 + 100, 1000) = 1000 when l2.bin generates a new graphics frame (frame as in FPS), the contents will be based on cameraZoom. These steps are, of course, extremely simplified. Changing contents of settings.ini would have an effect through step 4, but that's not the only way of affecting cameraZoom. Here are others: You could change the memory of l2.bin so that it thinks the correct path to look for is C:/path/to/my/hacked/settings.ini. (step 1) You could patch Windows itself so that when C:/path/to/l2/folder/settings.ini is requested, Windows provides C:/path/to/my/hacked/settings.ini instead. (step 2) You could use 3rd party software to modify the code in l2.bin's memory and get rid of the section where the check is done (step 9) and instead put cameraZoom = cameraZoom + delta. (step 9) None of these require changing C:/path/to/l2/folder/settings.ini and all of them would have the same outcome. Some of the differences are difficulty and reliance on version of l2.
  4. Banned Accounts?

    I think making modifications to the game client is a separate issue from using third party software (even if you used some software to make such modifications). I can't think of many scenarios where players would be incorrectly banned for modifying the client since most software doesn't touch memory of other software. Even antivirus software that does scan memory contents of other apps merely terminates suspicious apps without modifications.
  5. Banned Accounts?

    What elements are you talking about that can be inferred from the name of the application that caused the ban? And you know this because you have conducted an anonymous survey of banned individuals where the 'vase majority' honestly disclose the fact that they were intentionally using prohibited 3rd party software? I deal with trolls too and I am not talking about them. I am talking about an average human being recognizing an average bot, not every human and not every bot. That alone would provide a far better solution than there is currently. The edge cases of AI usage are not that big of a problem (yet). Which is why I suggested ML as a screening measure to make GMs' jobs easier/faster. You should also consider the differences in magnitude (thousands of players here vs millions there). I never said no banned player deserved it. The focus of this discussion is on players that didn't.
  6. Banned Accounts?

    Bot builders could just as easily make any # of accounts and keep modifying their code until the usage of their app no longer results in a ban. In contrast to us, they can have no doubt that it is their app that causes the ban. So IMHO, providing the name of the application that caused the ban is of no additional benefit to bot builders. One can argue that we could also make dummy accounts and launch the exact same apps we had open at the time of the ban by turn to find the troublemaker. The problem is that unless you can replicate the exact same state flow of the application, you are highly likely to end up with false negatives. I would argue that the safest way (w.r.t. the sanity/existence of player base) to detect bots is to do so on the server side through avatar behavioral analysis by machine learning. Humans can pretty accurately recognize when someone is botting just by observing for a few seconds, so the idea is to get the computer to learn to do the same thing. If they had the server do it automatically as a screening measure and then route to GMs for action, NCSoft would have a nice, low-cost and more reliable alternative. It's stupid that innocent people keep getting banned while bots are busy in the ant nest racking up $$$.
  7. Feels like NCSOFT ppl that read player complaints are detached from NCSOFT ppl that make gameplay decisions. Are we really at the mercy of Koreans?