Frosi

What I heard is that EAC was waaaaay faster to patch things and that cheat providers would basically have to maintain their cheat with weekly updates else it'd run into being detected. In the cases they were too slow it was detected and players got caught. Putting pressure on cheat providers is huge cause keeping things updated are work hours and in a game with a population like APB they may run into the whole thing simply not being profitable anymore. As for the server side, if anything it'll help with detecting private cheats / closets since server sides can give away who's cheating so the client side can look into said flagged players.

Color based Triggerbots may still very well work, however, cheats that inject into the game will have to be updated to 64Bit which is a big task and therefore means its unlikely anyone has done so in such little time.

The 64Bit update is an entirely foundational change, its not meant to change the games looks but rather modernize the engine to a 64Bit standard which then allows them to backport things from 2.x and more reliably work on the games issues and therefore steer it into a better future. In other words, 1.30 is so they can continue to support the game and actually develop things. 64Bit also fixes the RTX crash and increases the memory ceiling which allows for future game optimization, one such example being a new approach to garbage collection and texture streaming so stutters aren't as frequent or don't happen in active gameplay scenarios.

1.30 looks identical to live, nothing has changed in that regard, its a foundational change without any visual impact, however, I can still provide you with the data of 3 of the benchmarks I ran, you will quickly notice that the first two are basically identical with the third one being a run with uncapped fps that I however can't mirror with a benchmark from Live since Live obviously has capped FPS. Specs are as follows: Intel i9 12900k (Stock) 2080 Super 32GB of 4000Mhz Ram Live 1080p Max settings (145 FPS Cap) 1.30 1080p Max settings (145 FPS Cap) 1.30 1080p Max settings (Uncapped FPS)

If you want to participate in the 1.30 Beta please refer to this thread and follow the link to download the client. Happy Testing

That's a mix of using High Quality Health Hud, Bloom and the night time shaders and can be fixed by changing two ingame options, no configs required.

You can try the code "AMA2022" and see if its still active, it awarded you 100G1c

You can check out the VoD on Twitch, Matt will also upload a recording of the AMA to Youtube at some point.

What Matt posted above is a quote from the Open Letter that I have written, those aren't his words, they're mine.

It is not, the document was done as a passion project of mine but kept the fact that if weapon balance becomes a talking point and LO wants to do something about it in mind, That way I can submit the document in which case the wording makes sense. I won't go into the feedback much but I want to point out that both of you seemed to have missed that the RFP changes are a revert to how the RFP used to be when it was the go to pistol in the game and could reliably kill players on 40-47 meters. Also all these changes are subject to change, I don't have access to their tools, I have to do a lot of math for these and often have to guess how certain values interact with each other, many of these values are starting points to iterate from, not something to just ship to the live game and expect to go flawlessly. I agree that the Tommy gun needs some love, its a bit of an oversight that its not in the document but the first thing I'd want to do to it would be to move back to its old, static recoil which no one has the old values for so its hard to make a suggestion without actually providing stats. From there it would likely need a recoil reduction but still keeping the old values in mind, simply toning them down a little followed by buffs to its bloom as example. Not a typo, very much intentional, its an aggressive approach and that's why, if this would ever be an approach LO would want to take it would be tested in which case it'll be very obvious if its too strong or not.

The document hasn't been given to Matt, it wasn't linked in the letter at all however he has now seen it because I asked for permissions to make it public since players have been asking to see it to which he said yes so here is the document. https://docs.google.com/document/d/167-1L_hXaxFe9a2QMTbHfLsGONCVaEEem2pTP3le97c/edit?usp=sharing

I authored the letter and intentionally made the decision to make it anonymous, this way players aren't afraid to give their unfiltered feedback to some of the serious topics at hand. The overall amount of toxicity in the game coming from some players will also make players not want to put their name on something they don't know the outcome of. Here you go this was also entirely authored by me, almost all of these changes are my ideas and opinions, nothing is set in stone and this is nothing more than a passion project of mine. The changes in the document are balancing around the current state of the game and primarily focus on buffs to underused guns or some that were recently over-nerfed. Both, its usually easier to buff guns without taking mods in mind considering many of them don't exactly have a set of meta mods to use on them especially when it comes to red mods which tend to change a gun the most. For Meta guns, nerfs shouldn't entirely kill a certain mod on a weapon (I am aware that was the case with CJ N-tec as well as HB2 N-tec back in the day) but in many cases there's also not a huge amount of room for nerfs in areas in which a gun is over-performing, again using the N-tec as an example, lowering the RoF would've been an option rather than nerfing its bloom / jump accuracy although this change was tested in a public test environment previously and was received with even more negative response than a simple max-bloom nerf. Balance is so incredibly subjective and guns like the Oblivion or even DMR-AV existed in that very state for the longest time before people have figured out just how strong they are after another part of the game has been touched. With the exception of the DMR-AV nerf I want to say that none of the changes in the document cater specifically to one type of play, this is also largely helped by the fact that its almost all buffs to weapons that never see any use in high level play anyways. I honestly think that higher mechanical skill already wins you fights, aiming, knowing how to play around cover and so on, I know the suggestion of overall lowering the bloom / increasing base accuracy exists but that'd require a rework for more than half the weapons in the game so I personally don't see that as an option, if balancing a hand full of guns is an issue then I don't see how this is a possible path.

Now that's a really spooky idea

Its a known bug with Tokenize, you can fix it by disabling and re-enabling Tokenize on your G1 account page

For all I know Unreal 4 is very different from Unreal 3, so much that you're better off rebuilding from Scratch rather than trying to port from 3 to 4 as most if not all of your code will no longer be functioning, APB also runs a crap ton of custom code to the point where APB's version of Unreal 3 may as well be its own engine and use some Unreal 3 things on top of it. In short, Unreal 3 differs too much compared to 4 while 4 and 5 are similar enough to allow for Unreal 4 projects to be migrated to Unreal 5, although even that will take a lot of work. As to building from Scratch, there's a lot to APB, an extreme amount of background systems doing things that most players would never notice, rebuilding it would be such a huge effort that you may as well make a new rather than try to rebuild a failed game again.

Updating APB to anything past 3.5 would mean having to rebuild it from scratch and rebuilding APB on newer versions of Unreal with a medium sized team would likely take many years before they have anything that they can show / play. In other words, not feasible unless you're a massive publisher and don't care about income while the rebuilding happens.

I am extremely sure that new engine was fixed on the new engine, even at 300+ fps.

I'm not a super knowledged guy when it comes to game engines but here are some basic answers to your questions 32Bit is VERY outdated and has many restrictions that clash with modern day technologies, the most basic result of moving to 64Bit will be not being bound to ~4GB of RAM anymore, allowing the game to use more ram if possible which can be used to optimize the game whether its load times or garbage collection. Nvidia cards released as or after the 20 series cards have new memory which in APB's case causes "out of memory" crashes, this will be fixed on 64Bit. There will be a performance increase across the board. Assuming they manage to backport the tools unreal 3.5 provided it'll also help with faster development. There's no date yet but I doubt LO would want to rush this IF the update itself succeeds internally, there will likely be a lot of inhouse testing done by their Quality assurance team as well as SPCT before they head into possible Open Beta tests and the eventual release. For all I know this is an "under the hood" type of upgrade, us players will likely not see any significant changes to the games looks. If they manage to backport modern tools it should hopefully increase the efficiency and speed at which they can update the game whether its new content, balance or bug fixes. Better performance, better options for them to fix issues about the game, possibly introduce means for them to utilize graphics cards more rather than mostly relying on fast single core processing power, better tools for them as well as more options for external tools such as anti-cheats.

Plant bug on Phone booths is usually not placed on the phone booth but rather on the wall behind it (this is why your character often walks a bit to the side when trying to do it from the front), this means that if the wall is thin enough you can do it through the wall from the other side, this is rather helpful cause most Phone booths are in wide, open areas that are easy to defend.

I'm assuming they're going to try and backport some of the things they did on 2.2/3.5 ahead of releasing 1.3, I think the plan is to also backport the tools that 3.5 would've provided which means making new content should hopefully be easier and not like jumping through hoops at every step. While I personally think the meta is in a good spot except for very few outliers I do think there need to be improvements and I'm not just talking about buffs to the dozens of weapons that just cant compete. Weapon stats need to be communicated to players much better than the bars we currently have and hopefully that should also be an easier task to do on 1.3. I'll attach a concept I did in like 5 mins in ms paint (xd) below but ideally the bars are replaced with actual numbers for important stats that could also change dynamically depending on the mods you have on the gun such as IR increasing the effective range from 50 to 57, Three point sling decreasing the equip time etc. As with 3.5 and 2.2 I think that LO is well aware that this is likely their last shot at a big increase in player numbers, if it fails, they'll have to work their way up slowly by making the game better one update at the time much like No Man's Sky did so ideally they actually release 1.3 in a state that has a bunch of QoL improvements, updates or content that actually makes a large chunk of returning players stick around as that'll accelerate the games potential revival. I think every player that actually still cares about the game should encourage LO to do so, taking an extra month or two getting these QoL updates in in an attempt to make returning players stick around should be well worth it. I might look into making a thread in the future when 1.3 is getting closer to release asking the community for feedback and potential QoL changes that LO could implement, I already have a document with suggestions for this that I've been updating for a while myself that could then be updated with the communities ideas and forwarded to someone at LO. If you have ideas now and don't want to wait feel free to poke me on the LO discord.

The engine can go beyond what the current cap is but its hardly advised because it'll break other things such as making sliding even worse or new bugs entirely. Sliding was never an issue on 3.5 however so assuming they somehow backport whatever fixed sliding I could see them unlock the fps on the 64Bit client.

If they had a date for when the post from Matt is coming they would've mentioned it, they simply wanted to let people know that something is coming and that APB is still on Matt's list of things to work on which breaks the complete silence we had in the previous months.

If its an .ini file you are allowed to edit it, mousefix, hold crouch, toggle sprint and most graphical changes you can do are all done in .ini files which are the files the game changes when you make changes ingame to your sensitivity etc. They can set minimal values for these like how they did back when ppl set their Particles to 0 to turn them off entirely, this does not work anymore so instead, ppl are using .upk edits to remove things like grenade explosion particles, muzzleflash etc, this is absolutely not allowed. If the muzzleflash removal if done through .ini files it should be fine because it follows LO's rules, however, I believe all ways to do it through .ini edits has been fixed by G1 and ppl are editing the actual unreal package files to remove it. The nofog shader is weird in how it operates, its technically considered a shader but doesn't behave like what is traditionally considered as a shader edit in apb since it does not require bloom to be enabled to work. Long ago, within the first year of LO's takeover I personally asked Matt if the nofog shader is something they ban for and was given the answer that they do not ban for it but plan on fixing the ability to remove the fog at some point and I believe they even did so with the events which kick you if you are using certain versions of the nofog shader although it doesn't work for all. So I would very much consider it as a grey area and they could change their mind on how they handle it at any time.

I think that's a fair take to have but in the end there's just no doing right with the APB community, ppl will always find something to be negative about and I genuienly think he simply wanted us to know that he's still there and APB is still on his map of things to work on and that we'll hear more soon.

I'd imagine that if they had a time frame for Matt's post they would've announced it in the post last week, never once did they indicate that the post is coming within the next x amount of days, they simply let the community know that the concerns have been heard and Matt is making a post in the future.