How to ban this cheat client? #214
Comments
|
And no one is against having a "bugfixedhl" mod which have their own servers and clients. Then again, everyone is on the same, level playing field. But being able to join "non-bugfixed" , vanilla servers without the server admins permission isn't right. As these "bugfixedhl" players clearly have an advantage over "non-bugfixed" ones. I initially thought that VAC or |
|
Just detect and block BHL clients, such feature exist. |
Thanks, I'll look into that. There is already a serverside component in this, and client's ability to query server settings. Why there aren't simply: edit: or maybe just check whether And the client can see whether these cheats are enabled or not. If not , by default, then don't enable them. It's pretty appalling that people run around with these cheats among the vanilla players who then think these people are good bunnyhoppers executing frameperfect jumps, while in fact they are cheating but also deluding themselves that they are not. Again, I'm not against auto-bhop servers nor "BHL" players playing against other "BHL" players. Just that people should be aware of this, as currently other players think they are playing on vanilla servers with other vanilla people without being aware that they're being taken for a ride by players using this "BHL" client. I'd also bet that there are many server admins who don't know about the existence of this client and that some of their playerbase are cheating using this. |
|
I couldn't find any information about the feature @Safety1st was talking about, which could detect and block BHL clients. However, meanwhile I put together this quick AMXX plugin which can block BHL clients. #include <amxmodx>
#define AUTHOR "Anon"
#define PLUGIN "Block BHL"
#define VERSION "1.0"
public plugin_init() {
register_plugin(PLUGIN, VERSION, AUTHOR)
}
public KickUser(id) {
new address[32]
get_user_ip(id, address, charsmax(address), 1)
server_cmd("kick #%d;wait;addip 0 ^"%s^";wait;writeip", get_user_userid(id), address)
}
public BHLCheck(id, const cvar[], const szrValue[])
{
if (!equal(szrValue,"Bad CVAR request")) {
KickUser(id)
}
}
public client_connect(id)
{
if (!is_user_bot(id)) {
query_client_cvar(id, "aghl_supports", "BHLCheck")
query_client_cvar(id, "aghl_version", "BHLCheck")
query_client_cvar(id, "hud_colortext", "BHLCheck")
query_client_cvar(id, "hud_strafeguide", "BHLCheck")
query_client_cvar(id, "cl_messages_log", "BHLCheck")
query_client_cvar(id, "cl_autojump", "BHLCheck")
query_client_cvar(id, "cl_bunnyhop", "BHLCheck")
query_client_cvar(id, "cl_jumptype", "BHLCheck")
}
}This still doesn't solve the issue though, which is that allowing BHL clients should be an opt-in thing, not opt-out. It's really not unlike forcing autoaim on at clientside even if server has sv_aim 0 / sv_allow_autoaim 0. So let's call it what it is, cheating. And not try to sell this as some "bugfixed" version, which it clearly ain't. In fact the way I found about this was that I heard somewhere about this "bugfixed" version. I was delighted, who wouldn't want bugs to be fixed, right? Que my surprise, when I found that it's a cheat client instead, being called nonchalantly a "bugfixed" version which hides its' true intentions. Get a grip, devs, please! |
|
@anzz1, you are right: in ideal world server owners should have the ability to enable only 'bugfixed' features without 'improved' ones. But the reality is different: there is no ability for GoldSrc servers to force particular rules on clients. BTW there is better way to detect BHL clients, look into native API: |
I am not sure what you mean. Sure, GoldSrc servers by themselves can't block aimbots and wallhacks either. If that's where you were going. What I was going at, is that this "bugfixedhl" already has server and client components which can communicate with each other. This is not some "perfect world" scenario. This was and is perfectly doable, always has been. It's about not pushing cheats as a supposedly legitimate client, calling it a "bugfixedHL", instead of something like "hackHL" or whatever. I'm pretty sure that this has already misled people to think they're not cheating by installing this client, while in fact they are. Automating frame-perfect jumps isn't different from automating aim, both require skill and are a slap in the face for the players which have legitimately acquired those skills. So why not go all the way then and include aimbot and wallhack too? Why this half-way measure? What is exactly the problem here? |
|
The problem is in GoldSrc design. They're is no way to detect ether enabled functionality on clients or restrict from enabling certain features by server. Especially if it is open-source project. |
|
Obviously GoldSrc doesn't have server-side functionality on detecting client-side cheats. Just because you are not blocked from cheating via invasive measures like forcing you to install system-wide kernel drivers before allowing you to play, like many modern games do, that doesn't make cheating okay. Just because you can cheat doesn't mean you should cheat. Even worse is calling the cheat some innocuous name like "Bugfixed HL", implying you are not peddling cheats here, while in fact that is exactly what you're doing. I love open source but this type of thing is exactly what gives open source a bad rep. Why make any part of your game or engine open source, when cheat vendors are circling around like jackals and immediately exploit the situation when something is open-sourced. Why do you have to fuck up things for everyone? Every time these things happen, game developers are further discouraged from open-sourcing anything, or allowing modding for that matter. |
And this is obviously a lie. There is the CVar flag There is absolutely nothing preventing from designing the client in such a way that either It was just never done so and cheats were enabled right from the beginning without asking anyone for any permission, and now you're giving the reason as "it can't be done" which is a complete and utter lie. Not even owning up that a bad thing for modding and open-source has been done here, and then claiming nothing could have been done or even can be done about it, is just bewildering to me. You can claim ignorance or whatever if you really need to save face, just don't lie. |
|
It's sad to hear I'm a liar. But you know better and are allowed to post anything you want. HAND |
|
And by the way, it's also entirely possible to make bhl a separate mod, not to be used with vanilla servers. An example on how this can be done is here in the halflife-updated repo: twhl-community/halflife-op4-updated@ab5735c And "half-life updated" doesn't even have any cheat features, yet they still have the integrity to block it from being used in vanilla servers. "Can't be done" my ass. |
I agree that auto-bhopping and auto-ducktapping are somewhat controversial. However, advanced movement mechanics (like bhopping, wallstrafing, airstrafing, gauss-jumping) have always been a core part of the gameplay. It used to be normal to use console scripts to automate some of them. BHL provides a convinient command for that.
Default servers have a speed-cap for bhopping. BHL servers or some other servers can disable it.
You can use the Server API or query the cvar "aghl.ru". Which you've already done.
Because the original BHL didn't have them. Almost all of my improvements are on the client-side.
In an ideal world, yes. Unfortunately, there is a large number of clients and servers that use old versions of BHL (even before any of my changes) or some other custom clients. If clients update, players will find out that servers that used to allow bhopping no longer do because the server runs an old version. Then players will download a previous release, disable auto-updates and will keep playing.
There is. Using custom netork messages or maybe using
That only makes it easier to bypass a server-side protection. But that takes a differnt kind of skill.
It is though. One requires precise movement and good reaction times. Other requires the player to press a button during the window of 4 milliseconds (at 250 FPS), which is impossible for a human to do non-randomly. |
When it used to be normal, back in the WON times? When was the last time automatic bunnyhopping was possible without using a cheat or an exploit (you probably mean the bugged _special, which was completely unintentional engine bug which has been fixed for like ~15 years now, and was always banned to be used in any competitive scenario like CS leagues)
Of course it is. Admittedly this is the smallest of the offenses, but still there is a timing component present in not pressing Ctrl+Space, but pressing first Ctrl, then Space. This is just another entry in your long list of trivializing gameplay, allowing players to focus on other things like aiming while your bot does the rest of the work. Also, have you not heard of the console command
I'm not too familiar with KZ modes in HL, but at least in CS all sorts of scripts and helper programs have always been banned as long as KZ servers have existed. Some KZ servers introduce such elements to everyone from server-side, which also puts everyone in a fair and equal position. Those features can be easily implemented server-side by using server-side mods, it is only a cheat when done client-side. There is no need for such thing, this is again you forcing your stuff to be used on servers which don't have such features enabled.
I didn't know replacing original game sprites were allowed, so I'll concede this point. My background was mostly in competitive CS back in the day, where modifying the client in any way, including any models, textures or sprites was expressly disallowed. I guess the HL community took a more laissez-faire approach in creating advantages over others by use of modifications.
I did not mean removing the bunnyhop cap, I meant the automatic bunnyhopping allowed by the cheat client. Which should obviously be allowed by querying the serverside cvar first, either
So in your defense, because someone already shit the bed, it's okay to keep on piling more shit onto that bed? If you were to correct course and make the cheats opt-in by servers like is right and fair, and that would make some cheaters use old versions to keep up their cheating, let them. At least it's no longer your fault at that point, and you're not actively endorsing cheating.
Exactly. Cheaters are and always will be problem in any multiplayer game. It's impossible to make it such it can't be bypassed, but cheating shouldn't be the default option. Having cheats be enabled only when server allows it not only can be done, but should be done, obviously.
There are some speedrunners who would beg to differ on your point of bunnyhopping without cheats being impossible. No one is also forcing you to play at 250FPS, the engine (including physics) was never meant to be ran at over 100FPS anyway. I can't fathom how you don't see that is the exact point, frame-perfect bunnyhopping is hard, and that's exactly as it should be. Patch to have either Quake-style or completely automatic bhopping would be the easiest thing ever to patch, yet it has never been done. I can't understand how it doesn't ring any bells in your head that what it means, is that current behaviour of not allowing automatic bunnyhopping is intended behaviour. And I also don't get how you don't see anything wrong in what you're doing. Not only are trivializing the skill of people who might have practiced perfecting the bunnyhopping for years, but it's worse than that. No, you take a step further in much more bad and sinister direction. In fact, since automatic bunnyhopping is not actually a part of the game, you are fooling other unaware players that you have practiced and perfected the art of bunnyhopping, while in reality you're just another cheater. And when people become aware, you're putting the shadow of doubts in people's minds about those who really have the skill, "Is this one just another cheater too?" might one think after encountering a great bhopper. Yeah, sure, the game is old now. But kudos to you for trying to bring down whatever's left today. You really think you're helping the community by creating more cheaters zooming around the servers using your auto-bhops? I like to re-emphasize the point that no one is saying you couldn't create a mod in which you can run around auto-bhopping and play against other auto-bhoppers. In fact there exist such a mod already, called Adrenaline Gamer. What you're doing wrong is forcing yourself and other cheaters like you into vanilla servers running vanilla Half-Life, which want to have vanilla gameplay, which does include (but is not limited to), having to press jump precisely to be able to bunny hop without slowing down, having to press jump+duck in order to long jump, having to aim manually if server is configured as such, etc. You are forcing yourself into a place where you and others like you are not wanted into. I sincerely do not understand how you can't see anything wrong in that. The greatest problem of all isn't even the fact that you're openly distributing a cheat client. It is the fact that you're being insincere about it, calling it an innocent name like "Bugfixed" HL. This could lead an innocent player trying it out without even realizing that they're installing cheats. Then left wondering why the hell did they get banned. With a more appropriate name like "HaxxHL", "CheatHL", "AutomatedHL" or anything to that effect, you wouldn't be lying to your potential users by misrepresenting your software and there would be no such confusion. |
|
If you'd like an example of project which does this correctly, look no further than s1lentq/ReGameDLL_CS, which is a decompilation/recreation of Counter-Strike's So pretty much what you're doing here, but just doing it correctly. That is, having the modifications be controlled by the server, putting everyone in the server on an equal footing. If your modification also did this:
We wouldn't be having this conversation, and absolutely no-one would accuse you of cheating and endorsement of cheating. Note the difference, it's sv_ and not cl_. Two small characters which make all the difference. |
|
Bro demands 1.5 contributors to implement an anticheat for open-source project 💀 |
|
What is considered a cheat for you, for other communities may quite commonplace with fully explained arguments, and it is still subjective to consider what gives an advantage in fact and not For example, if you think that having GL crosshairs ( Understand that you are not the only one of the earth around which the whole world revolves For example, when you have autobhop, it still doesn't provide a good advantage if you're fairly unskilled itself Because you also need a strafe mechanic and some bhop techniques (such as surfing, stand-up bhop), which takes months and years to improve the result, and believe me, I know this perfectly since I’ve been in the HL/AG bhop / speedrun community for a long time and I have enough significant records on bhop maps andin friend with most of HL/AG runners and bhoppers Autobhop in fact simply forces you to focus more on your strafe skill, without being distracted by the factor of whether you have bad mouse scrolling or not, which in fact forces you to progress more faster in bhopping There are also games that focused on bhop functionality, where autobhop is enabled by default and there are things like HUD strafeguide / speedometer (Momentum Mod, DeFRaG, Diabotical) I’m not saying that everyone should use autobhop, I understand categories where they are exclusively done without scripts, for example in Half-Life speedruns there is a division between playing with and without scripts, and runs will be in different categories, that is, you know, the authors the leaderboard is respected by both sides, not just one: https://www.speedrun.com/hl1 You should also understand that all these checks will be meaningless simply because this is an open source project It's not BHL's fault that you think some functionality you don't like is available, it's only your concern to ensure your server is protected from it, you're always open to making a pull request to the project In addition, such things as autobhop and ducktap were discussed about allowing not only by AG bhoppers, but also among AG deathmatch players, there were those who did not agree, there were those who agreed, but in the end they sided with the majority and that’s was right Also about your approach in #214 (comment), are you just trying to IP ban all players who have these commands on the client? LOL Need to explain two reasons why it is wrong to do like this? Firstly, those who know about this, rather: A) rename all cvars and recompile client Secondly and most importantly, you do not give them a chance to correct themselves according to your principles. Instead of kicking a player and telling him to use a client that in your opinion is considered normal for this server, you immediately blacklist him, this is just ridiculous, then you are losing online due to your own stupidity Enabling flag in
Speaking about all these workarounds, I do not support cheating, it’s just that in general it lies on the surface It’s just that your understanding of cheating is quite absurd, that is, those who run around with custom crosshairs / speedometers and autobhop are the number one enemy in comparison with real cheaters who may have aimbots, wallhacks and autostrafing And even if we consider the same wallhack, for example, in multiplayer it is definitely bad to use and I am categorically in favor of blocking such players, but for example in the singleplayer it is helpful for speedrunners to research the game in more details (but they are not used during the run itself since it disallowed, but only before it for a practice), so not everything is so simple |
Wikipedia describes video game cheating as "Cheating in video games involves a video game player using various methods to create an advantage beyond normal gameplay, usually in order to make the game easier." There are no "double standards" in sight, except in your arguments. Anything involving a 3rd-party program is cheating, including installing 3rd-party software to add crosshairs. But I already conceded the point that the crosshair is the least contentious issue, the other cheats are the major issue. This is what I hate here, that you have somehow deluded yourselves into thinking you are not cheaters, and now are trying to delude others too. Trying to absolve yourselves by making excuses why you should be allowed to use these cheats and why it's okay, because you aren't skilled enough to bunnyhop without additional cheats yet you still somehow believe that you're entitled to be elevated to the same skill level as those who have mastered it, by means of cheating. Now you're pushing this bullshit to everyone else, just so you can keep on cheating instead of practicing. This is very dishonest of you.
What the actual fuck? So what you're saying is because the cheat becomes more effective the more skilled you are, it somehow makes it okay? Your arguments make absolutely no sense. Let's try replacing some words, quoting you:
Yeah, the same exact thing applies for other cheats too than just auto-bhop, like wallhacks, ESP, whatever.
So we are in agreement. Like said, I'm not against having different categories, which in this context mean different mods and servers which allow auto bhop. Just don't force yourself into the vanilla mod/category, armed with auto bhop and taking advantage over others. That is cheating. If you use scripts (or cheats like auto-bhop) in the vanilla non-scripted category in speedruns, you would get banned instantly. For the umpteenth time, this is only about cheating in vanilla Half-Life by the use of modified client files. To be honest, I don't think you are that stupid that you don't understand the point.
I couldn't agree more. You are completely free to keep your auto-bhops in your Adrenaline Gamer community, where everyone does have auto-bhop and is on equal footing. Just keep your AG clients out of vanilla Half-Life servers. Auto-bhopping where everyone has the same auto-bhop client, or is on the same auto-bhop server, is obviously not cheating, it's modding. Cheating is when you take the liberty of creating an advantage over other, non-modified players.
No, I am not saying that. This is about vanilla Half-Life.
Again you're trying to make the point about something else that it ain't.
I never said you can't bypass checks, that cheats don't work. There has always been ways to cheat, and there always will be, no matter the game. Some games block these better, some worse. Usually making better anticheats mean more pervasive measures which hinder the players privacy. Ultimately it's the cheaters' fault all these measures need to exist in the first place, the cheaters are the bad actors. This includes you who endorses cheating by trying to distort what cheating even is. In the context of multiplayer video games, it is advantage over others by use of modifications, can't get more simpler than that. And this definitely falls into the cheat category, and that fact doesn't change no matter how hard you try to justify it, bullshit everyone, or distort the facts. In fact, I can't think of a single multiplayer FPS game where installing a modified client dll to add features like auto-bhopping, auto-aiming, wallhacks, ESP, radars, no-recoil, etc. wouldn't be considered cheating, as it obviously, absolutely, is. It's beyond me how you still try to argue against that. |
No, you distort my idea that I wanted to convey. And it lies in the fact that a skilled bhopper without an autobhop can easily destroy a noob with an autobhop in most of cases. Scripts help you progress faster in the mechanics of bhopping and strafeing, so when you learn bhopping technique itself, you can turn that autobhop off and you only left to master with using scrolling on the mouse At the same time, when you're trying to learn how to bhop and scroll at the same time, you're trying to sit on two chairs, and you'll usually be bad or average at the best in both aspects, so you'll need a lot more time to learn and master than if you were to approach each aspect separately So usually most skilled bhoppers used autobhop in one way or another to understand first of all how the game works, if such a simple idea doesn’t reach you, then I’m sorry In addition, when bhop servers allow the use of autobhop, this gives everyone a good condition in that if, for example, you have bad scrolling on the mouse (here we do not mean the skill of the player with scrolling, but the scrolling on the mouse itself in terms of its quality from the mouse manufacturer), then, as I already said, you will not be distracted by this factor and can focus solely on mastering your strafes and that means that in general your bhop mechanics
Not banned, but your runs will simply be rejected with a comment to redirect it to a scripted category (since you could, for example, forget to click of change category or due to lack of experience, send it to wrong category) or the moderators themselves will redirect it to that right category Even here, you are always looking for a way to ban, as I explained above with the example of your amxmodx script, instead of simply kicking of player and pointing him with message of what he does wrong to according your server rules, instead you immediately try to block them, well, aren’t you an stupid? Because this is simply the best anti-advertising of your server if you really want to use this approach, why don’t you think about the fact that even those players that using the modified client, then some of them can probably agree with your requirements and actually use the original client?
I will repeat once again, if you do not like this or that functionality in your subjective opinion, it is only your task to protect the server from this, why should we have anything to do with it? If you want to add system so that in HL1 some cvars would be turned on when the server responds, you can go ahead and make a pull request for this repository and maybe it will be approved, I don't think tmp64 can be against this I also liked how you falsely accused tmp64 that the cvar to enable bhop is not such It is, because if you didn’t know, in September 2001, Valve released 1.1.0.8 WON patch, which introduced the bhopcap system, so if your speed exceeded more than 544 units, then you were instantly stopped and lost a most of the speed (this value is in 544 was calculated from your BugfixedHL-Rebased/src/pm_shared/pm_shared.cpp Lines 2561 to 2593 in 1a1f601 So this is what I want to say, that if you are really afraid of all bunnyhop players, then what is the issue on the server side, you can simply patch all of these, so you will both bug abusers and players with scripts kill in the once I'll tell you more, you can use autojump even without this modified client and still able connect to servers, all you need to do is download a older version of the GoldSrc steampipe engine ( And although it does not cause I also don’t like this approach in general about replaced client files So you want to say that any client change is already a departure from what Valve intended and therefore all this should be prohibited? That is, if Valve, for example, added some bugs and did not fix them, either because of a rare connection with the community, or perhaps because they did not have time at work, then all this was intended by the game and does not need to be fixed? Just accept the fact that Half-Life is a different community from what you are used to seeing in some modern AAA projects, these are different people in general, scripts here have long been considered from the half of the community, and even here not all scripts are approved by the same half community, I have seen a lot of forum battles among the same HL/AG deatmatch players, for whom only more than standard scripts can be allowed and do not directly give such a significant advantage, but at the same time they are very unhappy if someone, for example, uses a script, which will allow you to move silently, which in fact gives such a very hugely advantage on maps with large corridors in 1vs1 matches But then the same people who played without scripts also speedrun in the category with scripts and thereby broke this curse So if a person achieves great results without scripts, then he likely previously trained heavily with the scripts themselves in order to simply understand how the game works with high percent, I hope this idea will reach you So for example, allow everyone to use some kind script, then everyone will use it for the same conditions, so no one would in advantage toward other Changing all sorts of game settings, using all custom sprites to, for example, hide explosions (which can give an advantage in general), this is just the norm that everyone is used to it and tracking some of these things is not very easy, and sometimes not even possible with current API state and how the GoldSrc works itself |
|
I don't know how many times I can possibly say the same thing over and over, now I'm just repeating myself. No one has said you couldn't practice bunnyhopping using the auto-bhop cheat in single player or against bots. Of course, practice as much as you want with auto-bhop while you are playing amongst yourselves. Then put your cheats off when joining a vanilla HL multiplayer server. It really is that simple. This is really the same thing as practicing wallbangs against bots using a wallhack would be. Which is perfectly okay. The point is about consent. If you'd agreed among a group people that you'd all install wallhacks and play against each other in a "hack-vs-hack" server, that would also be perfectly fine. But when you are forcing yourself amongst uninformed, non-consenting players in a public server which has not expressly allowed cheating, and have cheats like auto-bhops, auto-ducktaps, auto-aims, wallhacks, etc. installed without permission, you are acting in bad faith.
Yes, no one was ever against auto-bhop servers. The whole point was and has always been you playing with auto-bhop in vanilla servers without consent of others, which is cheating. Because this client doesn't make a distinction between single-player and multiplayer, and also doesn't check if the server has
Again you are trying to bring your point of view as such, "it is possible to cheat, henceworth it is okay to cheat". 🤦
I didn't falsely claim anything. You are just misunderstanding, or pretending to misunderstand like you have been doing all the time here. Yes there is a cvar which controls the bhop, The cheat thing here is that it only effects the bhop speed cap, right here: While any In my country we have this saying of "trying to bend from an iron wire", when you are trying to explain the simplest concept in a simplest way possible but the receiving end is still too stupid (or pretending to be stupid) to understand. I think I've pretty much exhausted my explanations here, if you still don't understand maybe try reading again until you do. In a nutshell
I would also check up on the definition of whataboutism, since your posts are full of it. You are throwing around red herrings like it's the closing day at the fish market. |
|
If it's the case, then just create PR / create own client/mod without any "cheats". And also, if it's 100% a cheat client, then why we don't go far by creating other cheats? Automatic bunnyhop/ducktap or other things which you describe as a cheat is not such a benefit. About the issue, you can't ban this (or any) client completely because of the engine. Yes, you can check some cvars / compare MD5 hash / use BugfixedHL server API but it's not so stable and it has some nuances which you can't get over without writing own client with specific server communication. Of course, this type of server won't be popular but clean. There are many ways to achieve autobunnyhopping and etc. and we can't do a lot there because of established principles in community with using scripts/modified clients/older engine builds and so on. Not only BugfixedHL-Rebased has these features. |
|
Yes, unfortunately the consistency checks in GoldSrc engine are inadequate, and cheaters can exploit this flaw. Valve fixed this with This was more of a call to moral conscience than anything else to stop distributing cheats. Unless Valve itself does something, there isn't much to be done as a server owner. Cheaters be cheatin', and the battle against cheaters has always been an uphill battle, this is true for basically every online multiplayer game, let alone one that is 25 years old. |
Hey, I was wondering whether it was possible to block this cheat client from joining to servers?
It seems that VAC doesn't detect it, is there any other way?
If some people are wondering what I'm talking about this being a cheat client, the README file is misleading.
All the cheat features, like
cl_autojump/+ducktap/+ljump/hud_strafeguide/hud_jumpspeed/ ,cl_cross_enable, etc. are enabled by default, even on default servers which haven't explicitly allowed any of thisYou can test this by downloading a non-modified, fresh install of HLDS and then joining your server with the BugFixedHL client. All of the above commands work, even without enabling anything, so this claim
https://github.com/tmp64/BugfixedHL-Rebased#features
seems to be clearly a lie. Also all the other automations work which were never enabled server-side. No mentions of them on the frontpage either, you have to dig into the https://github.com/tmp64/BugfixedHL-Rebased/wiki/Client-command-reference to find the more cheaty options. Only thing currently missing is an aimbot or an "hearing automation" aka wallhack.
@ValveSoftware please see what is going on over here, and if need to be update VAC to detect this. In the meanwhile if there is any other means to block this via server plugins or whatnot, I'd be pleased to hear how.
I am not saying this couldn't be a mod/option, something like OpenAG already is, and no one can complain about bugfixes which don't affect gameplay.
But all of this, should be an opt-in feature from servers admins. Having clear gameplay advantages over non-modified clients using a modified client, is clearly and absolutely cheating.
To be perfectly clear, no one is complaining about your colored HUD or improved scoreboard. Your automatic +ducktaps, bunny hops, long jumps, strafing huds and so on, should only be allowed in the case server allows it. So everyone is on the same, level playing field.
This should be a no-brainer. How this stuff ever passed the smell test without being called out as a cheat, is beyond me.
The text was updated successfully, but these errors were encountered: