MattScott

This is something in design, and I'm really excited about where we are headed. However it is complicated. There are a number of things that need to occur in tandem, some of which aren't possible with Unreal 3. So changes will go in after Unification is complete.

This is absolutely a pre-requisite to any action mentioned above. It's a great example of why we need to take this slow.

Hi everyone, Here are the current CS stats right now: -5,580 total tickets have been created for APB since the new portal went up on 5/25 -3,293 of them have been closed. -14,092 interactions back and forth on tickets. -1,249 of them are untouched. I'm not going to try and sugar coat these numbers. We slowed down due to staffing changes and training. We are continuing to hire to meet demand. We are committed to doing better. Also if you didn't get unbanned, you do not need to open a new ticket. Please just reply to your existing ticket to have it re-opened so you can request a review. Thanks, Matt

Hi there, This is something I'm contemplating, but the implementation would be very very different from what has been discussed. We have already started more regular email communication with our players, and something like this would need to be communicated months and months in advance to give everyone enough time to react if they want. Nothing is going to happen immediately with this. Thanks, Matt

Hi guys, I can understand your trepidation. I'm not even saying it isn't warranted. We are attempting to bring back as many former RTW employees as possible, and for this we have rehired a former APB designer. He has a deep and intimate knowledge of the game, and while you may not agree with his direction, these changes wont be made by rookies. He has read through the forums and also reviewed how each weapon is performing to make sure it's meeting the original goals of that weapon. This wasn't about nerfing. This wasn't about evaluating how many players are using a specific weapon or its popularity. This was about looking at the overall matrix and evaluating how each weapon fits into our game to make sure everything is where it needs to be. We have lots of new content planned, including a new gun in the near term. But before we can add stuff, we need to tighten up the design a tad. I said in the Q&A that we needed to be careful and I meant it. I'm hopeful that this wont be as big of a change as you're anticipating. Thanks, Matt

Yes. We are planning to make a complete pass through the console district maps to help fix things. We are hoping to correct some of the areas that were handled badly We do have to be careful with this effort. Our main focus right now is just getting the districts to play better. I don't want to spend months revising district maps and holding up more content. I can definitely say that we are removing the N-HVR nerf from the Anubis. I can't speak directly to different crosshairs yet. Good idea, and I hear everyone on their concerns over ARMAS. Please bear with us. We need to clean up the store. This wont be a one-and-done effort. After this change, we'll see how the system works and continue making adjustments. There are competing goals at work here - show everything for advance players but make the store friendly enough to new and casual players. I'm not at all opposed to working out a way down the road where everything can be seen and bought. Right now, we can't do anything with the PC store because it's a mess. This first step is just to get our hands around it, and then we'll keep iterating till we all feel comfortable with it.

For clarity mostly we're removing duplicate references for items in the store. You'll still be able to buy the variation under the item itself. Having said that, some of the items are being removed and then added to a sale rotation to help clean up the sheer volume of stuff in the store. Map changes aren't in the weapon balance pass, but we will be working through map issues in the Roadmap. Basically, we have made a pass through the existing weapons and looked at how well they fit into the niche they were designed for. We also looked at under performing weapons to try and figure out how to make them more attractive. To give one specific change, the Anubis is getting a new crosshair, because the old one was wonky. I felt this pass was necessary to properly define the empty space in our weapon line-up before we started implementing new items. I'd like to see a proper database of every item as well, but the store isn't the place for that. We need to balance usability and align the stores across all platforms in prep for the codebase unification. Right now we spend lots of time administrating the each storefront differently. There is also a redesign coming. Yes. That is the goal.

Hi all, I'm not avoiding a Roadmap in any way. I had thought I spelled things out fairly well in the Q&A session to live up to my promise of a Roadmap in 30 days. However several players have expressed a desire to see more detail, so I'm translating our dev sprints into a post now. That should be up tomorrow. Thanks, Matt

Hi there, I wish I could provide more details, but unfortunately there are members of the community that will use that information against us. Thanks, Matt

Hi there, We have mitigation, and I have dedicated staff that turn it on immediately as soon as an attack hits. The problem is more related to how our network is architected and what happens to packets once mitigation is on. It has nothing to do with cost. We are working to correct the issue, but it's a significant change to how the game works. Thanks, Matt

Hi guys, We are continuing to work on BE, but this has devolved into naming and shaming and doesn't look productive any more. Locking. Thanks, Matt

Dear OP, I am sorry you had a bad experience with support. It would be improper for me to post details here, but I am happy to walk through our decision not to remove your ban over private message on the forums. For everyone else in this thread, I want to acknowledge a couple things: - Unbanning players is meant as a correction not a 2nd chance - We originally unbanned all players banned through FairFight under the category of "cheater" - This was because we know some of those players were banned improperly - After the first wave, we found multiple other categories of bans, some of which were also FairFight bans, contained subjective justification, or had no documentation at all - This 2nd wave of unbans was meant to try and catch anyone else that we felt were banned improperly - If you still feel you deserve to be unbanned, you are welcome to contact support, and we'll investigate your situation But I want to caution anyone who approaches us with "well, he got unbanned, so I deserve an unban too". We didn't set out to give people 2nd chances. We set out to correct unfair bans. To be clear - I realize in solving one problem, we have created another. We now have a lot of old players who knowingly and blatantly violated the TOS. We did our best to be selective, but there are millions of APB accounts, and it was impossible to review them all individually. Each of the unbanned accounts now has a choice: They can decide if they are going to enjoy the game and follow the TOS, or if they are going to get banned again. My team is committed to making APB fun and safe to play. I'm going to lock this thread. Thanks, Matt

Hi all, This thread honestly made me smile today. The best shitposting I've seen in weeks. Sorry for the silence. Everyone is catching up from E3. We should have an update today on the unbans. Waiting for dev to confirm our ETA is accurate. Thanks, Matt

Hi all, I spoke too soon. A couple issues were just brought to my attention. Unfortunately we are going to pause turning back on stack splitting, but I’m looking into other alternatives to help alleviate the issues. Thanks, Matt

Hi everyone, We had a busy week at E3, but I don't think that had a negative effect on Customer Support. Here are the current CS stats right now: - 4,612 total tickets have been created for APB since the new portal went up on 5/25 - 2,338 of them have been closed. - 11,353 interactions back and forth on tickets. - 837 of them are untouched. I'm proud of the team. We received ~1500 new tickets this week, yet we're overall lower than last week's untouched ticket count. Hopefully players are starting to feel like their tickets are being read and responded to. I do want to give everyone a heads up that our progress may slow down this next week. Selali and Lixil are going to be re-training some staff members based on observations and feedback we have received. There were some issues with individual reps copy/pasting responses without properly reading the tickets. I want to apologize to anyone affected by those issues. We are working to make sure that doesn't happen in the future. Thanks, Matt

Hi guys, We are turning back on stack splitting. It was a stop-gap measure to buy some time while we dug into the code to see if we could get the issue corrected. Upon further reflecting the lack of stack splitting is doing more damage than good, so it's being added back in. Sorry about that, Matt

Hi there, Great question. We have taken over everything - including the store. That means anything you want to spend comes directly to us. Thanks, Matt

Hi all, This week was E3, so I didn't get a lot of time on Fallen Earth. We have been able to extract the compiled game issues from the main data file. We have been able to get about 40% through re-organizing all the C++ code. The main problem was that several core libraries were copied and included several times. It's impossible to know which version is the most up-to-date, but it's clear they aren't all the same. So we've started moving everything into a new repository with each library referenced and only included once. We still have to do this for all the server code and some of the front end code, but we were able to get some of the tools recompiling this way. (This has been added to the original post for easy tracking) Thanks, Matt

Hi everyone, Lixil and several other team members were out all week with me at E3, so we have had limited ability to get on the forums. I'm sure you've noticed her responding at night mostly for the past couple of days. The DDOS attacks seem to be ping ponging between Jericho and Citadel right now, which is irritating because we are forced to leave up mitigation nearly all the time. My original post was two weeks ago, and we're getting close to a solution now. I should be able to give an update soon. Thanks, Matt

Hi all, We did just experienced another DDOS attack (literally minutes ago). But I don't want to confuse the issues. We are looking into the possibility that we have introduced an issue in this last patch. I have posted an update here. Thanks, Matt

Hi all, Here is a quick update of where we are with the last update released on Friday: 1) Installation issues There are some ongoing installation issues with the latest patch. These issues seem to be centered around the following three scenarios: (a) Steam installer not correctly writing registry entries. We are working with Valve on this. It was a problem a long time ago. Hopefully we can get a fix from them soon. We are also starting a work around just in case that doesn't happen quickly. (b) Players who copied files or didn't use an installer to add the game to their system. This can sometimes happen when players back up one system to another. Again, it appears certain registry entries aren't getting made (despite installing BE over and over). The fix for this is to delete your APB install, and install it from scratch off the download link on our website. 2) Lag / freezing issues There have been some players reporting an increase in lag after the patch. We are looking into possible negative performance impacts related to the BattlEye implementation. 3) Bans and detection We are not broadcasting bans, and to be crystal clear - no bans have been implemented. We took a very conservative approach this weekend. We didn't want a scenario where BE started mass autobanning players for incorrect reasons. We never want to have to mass unban again for some anti-cheat problem. Instead we chose to record and analyze the data, and then we will be processing players accordingly. Moving forward we are also adding extra detections one at a time till we feel the system is running smoothly. Anti-cheat will never be perfect. It takes iteration and constant tuning. Little Orbit is firm in our commitment to leverage solid client-side and server-side systems to help us identify and eliminate as many players using unfair advantages as possible, so the rest of us can enjoy the game. We have put our money where our mouth is, and this process will be ongoing. Having said that, there are some amazing players in the game who have spent years to master very difficult skills. They know the guns and their various parameters. They know the maps and where people tend to go. They know how to use APB's 3rd person camera to attack behind them which can look like a snap. My point is that to the average FPS player, these players can look like cheating. But APB is not an FPS. We need to make sure we don't punish good players. We appreciate your support. Thanks, Matt

Hi guys, I can confirm that server lag (see my post on this) and matchmaking are high priorities in the roadmap. BE is working as intended. I wont share exact details, but it is collecting data and reporting cheaters properly. Thanks, Matt

Hi guys, We will continue to test this, and see if we can come up with a fix. Thanks, Matt

Hi there, I appreciate your heart-felt letter. We've made our commitment clear. Now it rests on us to perform. Thanks, Matt

Hi there, We are going to work on this for many reasons.. size, colorblindness, etc. It's just a question of time and other higher priorities right now. Thanks, Matt