Dutchman101

We know that you are "Engin Canpolat", also known as "R 1 O T" for your DDoS channel on YouTube: * Your channel used to contain much more attack video's People like you, that are targetting MTA users and servers with malicious activity, aren't welcome on MTA services. But you already know that, because you had been banned for a long time, until you evaded the global ban (on serial C01DB526C186CD95E90291FC09A3FD53) by using another PC with serial 7F175DF43F406C28997DA61D61B00124. So because it's you, it also got banned. That's why you are here trying to lie your way through an appeal. Ban appeal denied, and as you know, this will never change. @Kerem Koca

Don't lie. As we all know, MTA forks, also known as the "russian projects" (such as RP BOX, Next RP, MTA Province) have a very limited anti-cheat, so cheating there is much more rampant than on the 'real' MTA. But still, occasionally we help forks reduce usage of specific cheats, reaching out with an alternative type of detection that will cause a ban wave. This is what happened yesterday, and is still ongoing - cheaters on forks are getting mass banned. We don't need your excuses, no one likes cheaters so as I said, when we can help forks, we won't leave that chance. Temporary bans cannot be appealed, and forks cheating bans can't be appealed at all. Ban appeal denied. If you don't like what happened, then don't cheat again after your ban expires @Sergey Busterenko

As we all know, MTA forks, also known as the "russian projects" (such as RP BOX, Next RP, MTA Province) have a very limited anti-cheat, so cheating there is much more rampant than on the 'real' MTA. But still, occasionally we help forks reduce usage of specific cheats, reaching out with an alternative type of detection that will cause a ban wave. This is what happened yesterday, and is still ongoing - cheaters on forks are getting mass banned. We don't need your excuses, no one likes cheaters so as I said, when we can help forks, we won't leave that chance. Temporary bans cannot be appealed, and forks cheating bans can't be appealed at all. Ban appeal denied. If you don't like what happened, then don't cheat again after your ban expires @sumtsov228

Don't lie As we all know, MTA forks, also known as the "russian projects" (such as RP BOX, Next RP, MTA Province) have a very limited anti-cheat, so cheating there is much more rampant than on the 'real' MTA. But still, occasionally we help forks reduce usage of specific cheats, reaching out with an alternative type of detection that will cause a ban wave. This is what happened yesterday, and is still ongoing - cheaters on forks are getting mass banned. We don't need your excuses, no one likes cheaters so as I said, when we can help forks, we won't leave that chance. Temporary bans cannot be appealed, and forks cheating bans can't be appealed at all. Ban appeal denied. If you don't like what happened, then don't cheat again after your ban expires.

Don't lie. As we all know, MTA forks, also known as the "russian projects" (such as RP BOX, Next RP, MTA Province) have a very limited anti-cheat, so cheating there is much more rampant than on the 'real' MTA. But still, occasionally we help forks reduce usage of specific cheats, reaching out with an alternative type of detection that will cause a ban wave. This is what happened yesterday, and is still ongoing - cheaters on forks are getting mass banned. We don't need your excuses, no one likes cheaters so as I said, when we can help forks, we won't leave that chance. Temporary bans cannot be appealed, and forks cheating bans can't be appealed at all. Ban appeal denied. If you don't like what happened, then don't cheat again after your ban expires.

You were developing software that is intended to harm MTA servers, so we don't really want you around. Ban appeal denied, @redOx0628

As we all know, MTA forks, also known as the "russian projects" (such as RP BOX, Next RP, MTA Province) have a very limited anti-cheat, so cheating there is much more rampant than on the 'real' MTA. But still, occasionally we help forks reduce usage of specific cheats, reaching out with an alternative type of detection that will cause a ban wave. This is what happened yesterday, and is still ongoing - cheaters on forks are getting mass banned. We don't need your excuses, no one likes cheaters so as I said, when we can help forks, we won't leave that chance. Temporary bans cannot be appealed, and forks cheating bans can't be appealed at all. Ban appeal denied. If you don't like what happened, then don't cheat again after your ban expires. @PaladinScrpt

Don't lie. As we all know, MTA forks, also known as the "russian projects" (such as RP BOX, Next RP, MTA Province) have a very limited anti-cheat, so cheating there is much more rampant than on the 'real' MTA. But still, occasionally we help forks reduce usage of specific cheats, reaching out with an alternative type of detection that will cause a ban wave. This is what happened yesterday, and is still ongoing - cheaters on forks are getting mass banned. We don't need your excuses, no one likes cheaters so as I said, when we can help forks, we won't leave that chance. Temporary bans cannot be appealed, and forks cheating bans can't be appealed at all. Ban appeal denied. If you don't like what happened, then don't cheat again after your ban expires. @malaholny

We have determined that you're 1 of those people in the Turkish DD scene looking to toxify it, through inventing (looking for) exploits and methods to gain unfair advantage and then, like usually happens, spreading it amongst the scene. This kind of behavior tends to include constantly trying to bypass EXEMOD patcher, working on lagswitches, other tools to gain an unfair/cheating advantage and such.. This group, known as the "core abusers" in Turkish DD scene, has began getting banned, and it brings a benefit to fair play for MTA. Ban appeal denied, unban isn't possible. It's just that we dont want you on MTA. In cases like this, past bans are considered together with information we have on your current activities (which we won't share, to prevent people from learning of their mistakes).

We have determined that you're 1 of those people in the Turkish DD scene looking to toxify it, through inventing (looking for) exploits and methods to gain unfair advantage and then, like usually happens, spreading it amongst the scene. This kind of behavior tends to include constantly trying to bypass EXEMOD patcher, working on lagswitches, other tools to gain an unfair/cheating advantage and such.. This group, known as the "core abusers" in Turkish DD scene, has began getting banned, and it brings a benefit to fair play for MTA. Ban appeal denied, unban isn't possible. It's just that we dont want you on MTA. In cases like this, past bans are considered together with information we have on your current activities (which we won't share, to prevent people from learning of their mistakes). In your case, it also counted that your friend is Rampakron and he also shared stuff with you, he's just like you, only a little worse. It's not called a group of "core abusers" for no reason.

We know who you are, a cheat developer who messed with MTA for many months this year. So lying about the ban reason won't help. Your ban will never be removed, @russiky

It should work now, the ban took longer due to a technical issue, but also because of you constantly evading the ban. Next time you want to cheat and get banned for it, don't be so invested in ban evading or else things like this will happen, @Banido mta

Well actually, i didn't read exactly what you said - my post is applicable to "This is a Non-Standard DFF" error message in general. In your case, if you are sure that you're using the same modelling program + DFF importer/exporter plugin at all times (which is still doubtful - otherwise the information I wrote about that part definately applies), you may have corrupted the DFF. That size is actually an indicator that something went wrong, as it would be hard especially for a skin model (considering you mentioned 'clothes') and then it will probably be of the type recursive corruption, that is when an exporter or conversion tool keeps writing DFF structures in a loop until you, or something, interrupts it. There are many DFF's that you can reproduce this phenomenon with (e.g a DFF that "rwconv" command-line tool for some reason doesn't support, and when you run it on that, it will output in a loop infinitely. It's like a hang on a certain part that it cannot intepret) and also this can be avoided by first exporting it with another plugin before (as in my example) using rwconv. Although that's not relevant to you, unless you have a back-up of the version right before you exported this "oversized, apparently broken" one, can restore it, and then idenify what exactly you did that made it incompatible with your plugin, causing it to write corruption. You can ask, how do I know this can be what happaned in your case? Because you gotta mess up big time in order to make a skin model so unoptimized, with a size of 4.50MB - it's unlikely that you gradually did so. Which means, it probably happened all of a sudden through the introduction of corruption. But if you really made it that unoptimized, who knows that your plugin doesn't support that, as it is plain unrealistic for a plugin to ever work with such a high poly skin model (different from vehicles: unoptimized vehicles can be like 30 MB, but unoptimized HQ skin models usually stay under, or just over, 1 MB.. yes, entirely a different standard) so the plugin author didn't count on users ever doing it, and then it might be a technical limitation. If that technical limitation exists, it might have surfaced while exporting (e.g now your DFF is corrupted, the plugin doesn't support writing such an unoptimized skin model) or only when reading it afterwards, so you cannot import it anymore. Intuitively, you'd say: let's try another plugin now.. but I really don't want you to mess up GTA with super unoptimized, for most users laggy, skin models either. This means it would be smart to wait until you provided us with the DFF, so we can check out what might have happened exactly. You know, the sheer size of my 2 posts is exactly the reason why offering for us to check it is more convenient, because as you can see, there's tons of things that may cause this and that you can do wrong to end up in this situation. But it's informative for future visitors about this matter in general so better understand what can be behind it.

That error message occurs in 3DS Max, when you're trying to import a DFF into Kams plugin that wasn't created by an exporter that Kams supports well. It may also happen when the DFF is corrupted. You're probably using the original (very old) version of Kams, because there is a newer one that got maintained at https://gtaforums.com/topic/907323-rel-kams-gta-scripts-2018-upd-31052020/, which added support for some types of "Non standard DFF", i believe at least from when the DFF was exported using common Blender DFF plugins, which was one of the most common reasons. Even though i would recommend this modern plugin instead of using Kams (even the updated one): https://gtaforums.com/topic/838479-dff-importer-and-exporter-for-3ds-max/. It's the best for many purposes, except for some niche uses that Kams excels at. Let me guess - it's an "invalid chunk" type of error. This again is a result of not all tools supporting eachother, due to some of them not applying the proper RW (DFF) format because their authors not understanding it thoroughly. As a side note, plugins with a proper DFF format is also beneficial for the game, again I really advise you use the link above for The_Hero's 3DS Max plugin. You can still import the "invalid chunk" (as z2g converter tells you) using another plugin, and re-export it so it should work. But if you do that with, for example, The_Hero's plugin, you will have automatically solved the "Non-standard DFF" error anyways, so then you're already done. You will have solved it for the old version of Kams, let alone for the new version from goldfish (in case the reason was some sort of corruption, rather than an unknown exporter like from Blender).

You were banned in 2018 because it appeared that you were speedhacking - whatever you did, don't do it again. We don't expect you to remember what you did, and the ban is so old that whatever we wanted to know is no longer relevant. So, the ban will be removed. Btw, the reason it took longer than neccesary (keeping you from playing) is that if you get a ban message like this (e.g "EMAIL: [email protected]" like in your case), you'll need to follow the instructions and send an e-mail there in order to possibly get unbanned. But you didn't. @Adrian_Vengeance

This ban is for trying to evade the global ban on your other PC (with serial 072093040ECF97B3C054FF25EF86BB03) - so yes, you may not have expected it, but I know who you are. I'm pretty sure we've already told you, but the thing is, you originally got banned for repeated cheating related activity, like at first you were in the private circle of friends with cheat developer "Skyflux / silenceesk" and used his cheats, you got unbanned for cooperating with us. But then, last month (October 2020) you decided to start cheating again, using a paid hack. Considering your past, we intended to now keep you banned permanently. Yeah, so don't lie, you're fully aware that you got banned last month and you simply tried to evade it, which didn't work out.

Ok, that sounds great. I suggest you join the MTA discord and get in touch with the devs at #development @fastman92 Edit (09 May 2021): just want to mention how this went down, so others that weren't present in #development chats in November 2020 are aware.. fastman92 had a new dialogue with MTA contributors & MTA team, and it again didn't work out to implement FLA to MTA due to his weird demands that border on the shady, or at the very least definately dont fit with MTA's opensource principles. He was hell-bent on keeping his FLA library closed source after adding it to MTA, fully secrective (even not allowing MTA team access to it) and being the only maintainer of this library within MTA. There was no way to talk sense into him about the plenty of reasons we would need it to be open-source and fully transparent on what we were adding, so the negotiations have been cancelled in an early stage again, with no further interest shown by MTA due to this weird behavior. Multiple devs have felt as if he was hiding something from us. There's much more to it, but i rather keep it simple. Also, we didn't want to resort to spending manpower fully reversing his library (due to him as its developer not cooperating) just to know what we were adding to MTA, in order to keep our users safe from any threats or vulnerabilities. Having to do that is clearly ridicilous, there should simply be transparency. TL;DR for the public: chance that FLA will ever be implemented is 0.01%, we will continue to lift limits by ourselves like we have steadily been doing for the past 2 years. When we announced a potential arrival of FLA on MTA (what this topic is about), we didn't yet realize what kind of a person/developer "fastman92" was, and how hard he would make it for us. Btw, some arrogance from fastman92 was involved (regarding his achievements with FLA), and we can say however that we don't need FLA or fastman92 - we can do it by ourselves, and people can expect future MTA releases to lift a bunch of such limits.

I thought the offer expired, you sort of gave up and set terms / expressed wishes that were considered unreasonable by the MTA team. After which others (including @Saml1er) started working to lift GTA limits, of which the currently merged and pending changes may conflict with yours. The people that worked on limits related stuff also said there are better ways of implementing the required changes than yours, and were fearing for instability (they were also rather afraid of using your code, as you can see for example in the closing comment of https://github.com/multitheftauto/mtasa-blue/pull/917) I'm not saying your achievement will go down the drain, but what I mean to say is that you're definately going to have to talk to the MTA devs again surrounding the desirability before anything else, @fastman92. If you are sure that you used the latest MTA source (in which some of the stuff was already implemented, or solved, such as with dynamic model IDs for skins and such) and also prevented duplicates between what your limited adjuster can do versus those changes that are already in MTA, then it's more likely to work out.

That's correct, they are out of memory. Considering your other recent posts.. maybe you shouldn't worry about crashes (as in: wonder about their reason), and thus stop asking, until you moved away from the server(s) you're currently playing on, to other servers that have better optimization.

Alright @sushiroll101, i just updated it. Yes, it's even growing - you can compare the new stats in main post with the old stats here Btw, during the past few days, at several moments in the evening there were 37,000 players online at the same time. Usually that's ~ 30,000 (without corona lockdowns ?) Examples: Date: 2020 Oct 29th 6:00 pm - Players: 37879 Date: 2020 Oct 28th 5:30 pm - Players: 37654 Date: 2020 Oct 27th 6:00 pm - Players: 37417 Note that the above examples are CEST timezone, so the evenings in Europe (the most busy moment on a daily basis)

You're not telling the full story.. as the real reason for trying to use that serial (which you're appealing for - 4F824E942CC8FB76160F87AD9EAD8A84) which happens to be banned due to past cheating related activity, is the fact that you were banned 2 days ago for attempted cheating (yet again) and wanted to be able to play, so you decided to try and evade using it. Facts: - That serial which was already banned since 2019, it was banned for trying out MFT cheats (at the time, we had reason to believe you were working for them, as a tester to NtKernelMc) - The serial that you got banned last week (C6439D8F86E9561FCCD366ACAFDE4D53), you also used it for trying out MFT cheats. Not a coincidence right? You seem to be involved with them, not just someone who desperately wants to cheat. Anyways, i realize that this is all on a russian MTA project (fork), not the 'real' MTA, unlike the first ban from 2019. Even then, MTA does want to help such fork keep persistent cheaters and cheat developer-involved people out of their project, like you - because they have weak anti-cheat and they are posing a greater danger. So, we will keep you banned. Now that we see the connections, we'll also permaban your other serial(s). Unfortunately, over the years, don't know how to be a normal player.. @Ellesse

There are currently multiple things wrong with this resource: - YouTube API key is no longer usable - Various issues (and things they changed on YouTube's end) obstructing playback, including https://github.com/multitheftauto/mtasa-blue/issues/1747 We recently already helped them maintain this resource, e.g by removing the "YouTube TV workaround" update that made the interface look worse - after MTA released a solution of their own (see here). Soon, when the current issue with that "do you want to play that video" has also been solved by MTA, we will probably do that again, by releasing an update to fix various issues that would be left to stand in the way of proper functioning. Because the authors seem rather inactive and this resource isn't their priority anymore.. while it was very popular when it still worked. So just wait, it probably won't be long until y'all can use it again.

Hypnoaltux, You're constantly invested in abuse and cheating-related activities - for example, massively trying to bypass our EXEMOD patch (not saying you succeeded yet, but it's the intention) and testing & building lagswitches, as many are detected by MTA individually you needed to put some effort to end up lagswitching like you did. Considering these activities, and the fact that you've got banned 7 times in the past for EXEMOD cheating (when it was still possible) and that you created your own EXEMODs during that time just like at this time while you're also looking for a bypass, tells us both that you didn't learn, and will never learn to be a normal player. So, we think that the MTA DD scene is better off without people like you, so we can issue longer or permanent bans based on individual cases. Don't lie (oh and I see you also didn't learn about not lying, considering your 2 ban appeal topics in the past after you were cheating in DD) Ban appeal denied, ban will stay forever

Nice story (and code written purely for the purpose of "proving your innocense") - don't lie. Ban appeal denied, unban will never happen.

Read https://wiki.multitheftauto.com/wiki/Resource:Admin Basically, add an user.AccountName entry to the Admin group inside server\mods\deathmatch > ACL.xml Like this: But please don't ask more questions than this, because you're probably using a leaked gamemode like stated earlier