[New Users] Please note that all new users need to be approved before posting. This process can take up to 24 hours. Thank you for your patience.
Check out the v.249 - Minar Picnic Patch Notes
here!
So... why don't we time limit kanna creation?
As we all know unless kishin is removed kanna bots will continue to exist and be the best class to use with hacks as they can increase mob spawn rates and reach high levels faster than other bot classes. We can not stand to lose kishin unless Frenzy Totem bites the dust as well (or at least given a different effect). The reason why Frenzy Totems must change with Kishin is because if Kishin no longer has the spawn increase effect, raising spawn rates in maps will be severely monopolized by Frenzy Totem holders selling service. But in the short term until the final decision is made up by Nexon, we could try to bandaid the solution and perhaps the solution might work well enough that Kishin might not have to go.
Nexon can suppress kanna bots by attacking them where they're being created by temporarily removing the ability to create Kanna classes like they did once before (although for a separate reason). Kanna creation will not be disabled for a long term period but have a monthly creation period that lasts for a week for players who still don't have a kanna mule/character in general to make a kanna and limit max kannas per world to 1 (unless deleted). That way players don't have to wait long to make a kanna as they'll get a chance to do it once a month for an entire week. That should give nexon a bit of time to thin out the herd of kanna bots and if they can do it in time we'll have less server disruptions and Kanna botters won't really have anything to do until the period reopens. We really have to depend on our GMs for this to happen. Nexon will need to train their staff that monitors the game directly by obtaining the source of hacks themselves and use it as an example so the GMs know what to look for when swatting down kanna bots (like map teleporting further than normal, for example). If it's successful we can begin testing with other classes like Ark and Dual Blade, which have recently rose up on suspicion lists for botting. We can try having 1 class available for 1 week, and then open up a different class the next, in a pattern-like way and notify players of their monthly re-release in the patch notes.
Since nothing is being done right now to stop kanna bot creation, but rather action being taken later on, it's worth a shot.
Comments
Bots do not bot to reach high levels, they even suicide to stay in level range of the map they want to bot in for the highest profit. That's why you see boatloads of kannas and arks and whatnot that are the exact same level in the same low level areas.
The problem is detection, account creation and general server stability.
Limiting classes and limiting the game for legitimate players should never be the solution to botters but that seems to be Nexon's go-to reasoning.
A good example of this...is ARK bots! Remove Kanna as an option, we just see a bunch of ark bots pop up, or even some of the old botting classes like BW and Kinesis. Ultimately, the big problem is taking care of the bots...auto bans have proven themselves...bad.
While it's true they'll bot on other classes, it's not true they'll cause the same amount of lag. Because each bot will be killing far fewer enemies per minute.
However, OP's suggestion will not work, by itself. The botters will simply create a huge stockpile of accounts with a Kanna on them during the one week a month when creation is allowed, and then release them as needed throughout the month.
A better suggestion would be to limit Kanna creation to one week per month, and also require having a higher level character (150? 200?) before being allowed to create one. This would require the botters to prepare that stockpile of accounts by first botting some other class, which might give Nexon time to detect and ban the account before the Kanna is even created.
However, this would make life harder for new players in Reboot. Up until now the recommendation was to make the meso-farming Kanna first, then some essential link skill, and only later worry about what class to main.
Since everyone benefits from it I would prefer to have Reboot suffer for a bit if it means that a better solution/mitigation to the Kanna and the bot issue as a whole is found.
I forgot that Zero creation was only allowed with a character in the account having a certain level, and as AKradian suggested, have a minimum level requirement of another character on the same account on the same world be reached before the class could be created when it's available for creation. However, like he mentioned, this would be unfortunate for Reboot players who haven't made their kanna yet for whatever reason. That is a different problem requiring a different solution, as Reboot wasn't originally intended with Kanna having a big impact in mind as KMS doesn't have Kanna to begin with. But you really have to ask yourself this, would you rather have Kishin get nuked, or wait it out for a few weeks to make a kanna and play a different class, perhaps the class you intend on maining and get it to the minimum level required to make a Kanna, while you wait for Kanna or one of the other classes to be re-released?
If a level requirement is in order, I feel that having a level 200 might be too harsh to ask for from Reboot players who are just starting out and don't have a kanna yet. Perhaps if there's a way for the game to check if there's more than 1 character in the account in that world that is at level 150, then having 2 level 150 characters instead of 1 level 200 may be the better and less harsh option.