-----------------ACB V5----------------- ACB V5 is the newest version of ACB, it has brand new advanced features such as an (actual) Collision Box instead of just using the player's sprite. SACB has this feature but ACB V5 improved upon this concept to bring you a better development experience. With ACB V5's brand new hitbox system you don't have to switch the costume to the hitbox whenever you want to check ground unlike in SACB, and it makes it easier to make advanced predictions without having to worry about hitbox issues such as whiskers unlike in ACME. ACB V5 just like its predecessors has decent compatibility with earlier ACB versions, but if you are trying to port more than a version ahead(ACB v3 to ACB v5 for example) you will have to make major modifications to your anticheat. -----------------Performance & Statistics----------------- (Math / Data provided at the bottom of this section) ACB V5 has no noticeable impact on performance when compared to ACB V4, SACB, and ACME. Compared to ACB V4, ACB V5 is 24% Smaller (in blocks) and 82% Smaller (in file size) Compared to SACB, ACB V5 is 49% Smaller (in blocks) and 96% Smaller (in file size) Compared to ACME, ACB V5 is 17% Smaller (in blocks) and 80% Smaller (in file size) -----------------Math / Data----------------- ________Blocks|File Size________ ACB V5 - 130 | 9 KB ACB V4 - 172 | 51.2 KB SACB - 257 | 230 KB ACME - 157 | 47.3 KB Versions Used: ACB V5.00, ACB V4.11, SACB 1.4.4, ACME v1.0.2 (results were rounded down to the nearest whole number)(this is beneficial to the other anticheats) Extra Notes: The " no noticeable impact" claim is subjective but pretty much every anticheat base has no issue with performance. ACB V5 might have a VERY(and I mean miniscule) performance impact compared to ACB V4 (but my logic for this also applies to ACME since it does the same thing), if you want to test the performance, I think I have a performance tester on my alt(notfgh) although, it may be for blocks only... well, just use the time stuff from it and just put a frame wait in the block area(it should say 0.029439478 or something instead of perfectly 0.03, that's the "lag", but its less than a frame of lag, its like 0.0000001% of a frame, so its literal grains of sand) -----------------Porting To ACB V5----------------- (if you have trouble with porting to ACB V5 or anything else related to ACB or even anticheats, you can always send me a message on dc ) ACB V4 to ACB V5 Should be pretty simple. The major thing you may run into is ACB V5's different collision logic. Y Position predictions that function when your touching ground may produce falses. ACB V3 to ACB V5 Expect at minimum the same issues as ACB V4. ACB V3 has many deprecated features that are no longer in more modern versions of ACB V3. Much of the logic in ACB V3 is different but it shouldn't be nearly as hard to port to ACB V5 as something like ACME as ACB versions share distinct similarities. ACB V2 to ACB V5 Expect at minimum to have the same issues as ACB V3. ACB V2 is extremely outdated compared to ACB V5 or even ACB V4, it is highly recommended to recode the entire anticheat on ACB V5 instead of trying to port, nearly every important part of ACB V2 is different when compared to ACB V5(Excluding some of the movement code which pretty much hasn't changed since ACB V1). If you do wish to port, expect major challenges regarding the collision system and deprecated features. ACB V1 to ACB V5 This is HIGHLY unrecommended and I implore you to recode your anticheat instead of trying to port it to ACB V5. ACB V1 does not even feature horizontal collisions, it's only vertical collision only affects MotionY, not Y position, it has no "Teleport Up" system, nearly every check in your anticheat that relies on collisions will false. SACB to ACB V5 SACB has considerable changes to its "source material"(which is ACB V4). It generally is possible and would be easier than trying to port ACB V2 to ACB V5, but in no way is it recommended. SACB despite being a ACB V4 distro is quite different and you will face challenges will porting, although most of the challenges will be just changing the names of stuff or how things are used, like the input system or the names of variables, sprites, etc. ACME to ACB V5 Not tested, but it should, in theory, be possible. Pros: ACME uses the same values as ACB V5(according to ea) Cons: Different names for MotionY(Yv), MotionX(Xv), Ground(plateform)(why ea, why plateform???), and Flag(FlagHandler). Lacking many things that ACB V5 anticheats would rely on(Rcol, Lcol) Completely different collision system(its as big of a difference as most things created by two different people who dislike how the other does things(think samsung and apple, or windows and linux)). It's recommended to avoid trying to port a ACME anticheat to ACB V5 and to either just stick with ACME(I'm sure ea would like the market share since right now he has 0%) or recode on ACB V5
--------------------------Changelog------------------------- 5.00->5.01 Removed redundant costume switches Modified the movement handler to use boolean's in the math to reduce the use of if blocks to lower block count Added a new broadcast, "When player flags - any", to allow code outside of the flag block to receive when flags occur (made by sparky @tombman999 ) Added a new custom block, "Check response handler", to allow more detailed reporting of flags outside of the flag block (although, multiple hat blocks of this can not exist, so it is recommended to not use this if you make an addon, but anticheats are fine to use it.) (made by sparky @tombman999 ) 5.01->5.02 Added security fixes to fix problems in R Col and L Col -----------------Credits & Thanks----------------- A lot of the utils are taken from ACB V4, which, despite being created by me, still took ideas and things people suggested so go take a look at ACB V4's changelog if you want to see who made / suggested what To Sweeper(owner/dev of SACB), thank you for the support on ACB V4 and your distro SACB. While I didn't take any direct ideas from it or anything like that, it did provide a good insight into what my base was missing. I may disagree with you on many things and you, me, but you did good work and I wish you well on your future endeavors, whether on Scratch or somewhere else.(I doubt she'll read this, but I want there to at least be some shred of proof that I respect her)
