@JagexAsh Others and I have noticed for a long time that during the animation of the humidify spell in PVP you are much more vulnerable to damage taken. Could you please look into the code if defensive stats are affected while casting humidify?
Hi Ayiza! Reminder about the F2P CW Community to get a keyholder world to avoid sabotage and crashing of our events. see below our event today 40v40 F2P Castle War Match with CW Driven clans. Appreciate you're support
@JagexAyiza@JagexAsh
https://t.co/qW9Bjb5g9k
@openosrs_null @JagexAsh I can agree with you on that. Their detection needs work (if at all possible). All I'm saying is that YOUR current platform is benefiting and reaching potential cheaters to a great extent. I have personally seen it turn an entire community into cheaters.
Hey @JagexAsh, the 3rd party client "OpenOSRS" recently moved all of its (bannable) plugins to a private repository to comply with Jagex. However not only is the repo easily accessible but the client itself still has very OP features like a customizable menu entry swapper.
@openosrs_null @JagexAsh Not sure if you're making up stuff to try and win an argument. I have never and would not ever ask for anything related to lifting restrictions. I invite you to post a screenshot.
@openosrs_null @JagexAsh You can repeat yourself all you want but that still won't justify the fact that you're, again, supporting users to abuse the game by granting them access to alternative methods of your "removed code". Abuse can be LIMITED by requiring an IDE to add malicious content.
@openosrs_null @JagexAsh You have several places for users to suggest content for your team to decide whether the idea is acceptable or not. Despite this, you're giving the user access to undetectable banned content, having them entirely skip familiarity with an IDE. Users cheat and you're supporting it.
@openosrs_null @JagexAsh With your analogy players can use a bot client as long as they're not botting. There is no reason to have the feature(s) there. It would only make it more difficult for Jagex to detect abuse. If you want QoL swaps then do it like Runelite does and remove the custom swapper.
@openosrs_null @JagexAsh OpenOSRS does provide them the tools to abuse interactions in-game by enabling the "custom swaps" in the menu entry swapper. It allows them to change default options of construction and thieving (which are supposed to be bannable according to Jagex) and a ton of other options.
@openosrs_null @JagexAsh Whatever you discussed with Ash was clearly misleading. As of now I am seeing over 600 people in the discord server regarding the "private" repository "ONLINE". The ease of access is no stretch at all. If you "hope" Jagex punishes users for it then you wouldn't be supporting it.
@OPRS_Kyle @JagexAsh There is a difference between loading external repos for testing and having a repository dedicated to granting access to plugins that are not (anymore) in compliance with Jagex's rules. Having an external plugin manager on the client makes your intentions blatantly obvious.
Hey @JagexAsh, the CW themed world (334) has been dealing with a lot of sabotaging: https://t.co/BBCBFEk2GU We are in desperate need of your support. We'd like to suggest giving keyholders the ability to kick sabotagers out of the game. They know when it's grieving or a strategy.
@JagexAsh Yes, they are the ones I'm referring to. What action should be taken to get this arranged? We don't mind having only 2 or 3 of the current keyholders get the ability to kick extremely disruptive game changing behavior to test the waters in the themed world.