Jump to content

MattScott

CEO
  • Content Count

    1281
  • Joined

  • Last visited

Everything posted by MattScott

  1. Hi all, For clarity, the SPCT uses a company Discord server. I have previously stated that we don’t want to interfere with the various community channels. Players need non-LO spaces to vent about us. We haven’t opened an official Discord to the general public because we need to demonstrate that we can properly moderate the existing channels and districts before we start adding new places for players to interact. Thanks, Matt
  2. Good catch. Just had my team put it up. https://steamcommunity.com/app/113420/discussions/0/3216031607502214335/
  3. @Kewlin - It’s Saturday for me, and I didn’t keep up with this thread as well as I should have. In the future I’ll avoid lengthy responses when I’m in the middle of other things. Let’s back up a little ways. I don’t have the experience or history with the community or this game that many of you do. Yet I found myself needing to recruit some players to help us test some upcoming features. Sometimes you simply have to pick a starting point and run with it. I chose many of these members based on my perceptions of them on our forums - but not necessarily their public posts. Many I have spoken to privately through PM. As Shini conveyed, some of these members reached out to me with feedback. Or in some cases I reached out to them. Others are active in the APB community outside of posting on our forums every day. And others were recommendations that were vetted by my staff. At the end of the day, they are still all my choices, and I have chosen to share that information with the community. Right or wrong, the buck stops with me. Thanks, Matt
  4. Hi all, Couple more points of clarification: Announcing the members of the SPCT was my idea. 1) Why did we announce who is in the SPCT? I don’t like secrets for the sake of secrets. People always find out anyway, so unless there is a good business reason, why bother creating that landmine? Imagine if you found out months from now that we had reformed the SPCT and we didn’t tell the player base. How would that feel? Better or worse than how we handled it? My guess is that any reaction you’re having right now would be 10x down the road. On top of that there are concrete reasons to reveal the team members. For instance, we are video capturing some of the playtest sessions so we can start creating marketing assets in time for the launch of upcoming features. In my opinion, it’s going to be pretty obvious who those players are in the videos. 2) Why do we need NDAs? This should be a no brainer. Testers get context about internal business issues that we don’t necessarily share publicly. Most importantly, we are sharing some information with them that is under NDA from external partners. Testers will see incomplete, broken features. We don’t want that shared with our players till it’s working correctly. Having said all that, I do want the testers to be able to share the good, the bad, and the ugly sometimes about what we are working on. I have already commited to finding opportunities for that. 3) Why did we choose these specifc people? There is no science to this. I read the forums. I chose people with opinions that participate a lot. These people had to pass our own internal standards, and I also chose people that could work together. For this initial group, I wanted a smal set of testers that we could manage properly. I don’t expect that all of our choices will be perfect. They just need to be ‘good enough’ to keep us moving forward. I want the team to be bigger, and there are plenty of other people on my list that I will likely approach in the future. 4) What are some tasks of the SPCT? Let’s use Slay Bells as an example. The members of the team have access to an internal Discord channel and to a private forum channel. We coordinated several tests on a closed server for them to get on and work through the event. They were given times and testing items. Each build was at various stages of completion ranging from late Alpha to Beta. After the playtesting they would write up feedback on the forums or discuss points over Discord. In several cases, we had Beastie get on to answer questions or respond to feedback. During the process of testing, the SPCT discovered various bugs within the gamemode. For example, vehicles could kill players in early tests, and we made adjustments after seeing some of the crazy stuff testers did to abuse things. To sum things up: I’m less interested in spending a lot of time second guessing and anticipating problems with our current team. I’m far more interested in holding this team accountable and revisiting this topic as time goes on to make sure we are meeting the goals of the game and the community. Thanks, Matt edited to include examples
  5. Hi there, I wasn’t sure if this was a joke post or not, but the OP seems sincere, so I’ll take it at face value. I can 100% confirm this is not true. Thanks, Matt
  6. Hi there, 3 months for support is objectively awful. Unfortunately, players submit tickets for absolutely everything from harassment to scammed items to billing issues. The old G1 also had a lot of copy/paste responses, and I made it a policy not to respond to players like that. If you ask for help on a ticket, we try to take the time and properly research the issue to get it resolved. We created the trading system in response to the sheer number of scam tickets. And we’ve recently rebuilt the /report system so players don’t need to open tickets for harassment or cheating issues. We are slowly seeing the queue times drop. We are working hard to catch up. Thanks, Matt
  7. Hi all, Despite some of the negativity, there has been a lot of good discussion here around the new team and its members. Given this game’s history I expected there would be some criticism. I’ll try to address some of the concerns. 1) The new SPCT is primarily focused on testing unreleased content. We test things internally as best as we can, but as we saw with some of the recent events, we could have used some help finding issues. These aren’t necessarily bugs. They can just be abusable mechanics for a minigame. We want to do more public tests, but engagement on OTW can be pretty hit or miss these days. In order to be involved in the SPCT, these members have agreed to participate in closed tests and write up feedback. 2) They are not representatives of Little Orbit, nor are they meant to be community ambassadors or player-facing helpers. We started the team to address a specific problem, and that’s it. We need to walk before we run, but if this works well, then we may start other community teams for other reasons. Hopefully we will be expanding the SPCT over the coming months. I’d like to have a much larger pool of reliable players that we can use for testing more complex features as they come up. Thanks, Matt
  8. Hi all, I have sent this to the team, and it looks like a bug unrelated to 2FA or tradelocking. We’re working on the issue. Thanks, Matt
  9. Sorry about that. I have edited the post for clarity. You can finish in 5 days total.
  10. Hi all, I've updated the post with all the rewards. Slay Bells starts on December 19th through January 2nd. Thanks, Matt
  11. Hi everyone, I have updated the details in this post to announce "First Night", which will start December 19th. We are very excited about this event. It hasn't been run for quite a while, and it has taken a lot of internal work to get all the pieces put back together. Thanks, Matt
  12. Hi @Aroa Croft, This is the same event with minor changes. However on December 19th we will be running an event that hasn't been seen in a long time. Without significant code changes, we can't innovate or make new content. We are still working on that. Thanks, Matt
  13. Yeah. Obviously I’m not going to be able to edit my way out of that one. It turns out, everyone on SPCT proofed that post...
  14. Hi all, I'm going to amend my earlier statement about 3 day bans. Under certain circumstances, we do allow BE to do automated temp bans for cheaters. This immediately alerts my staff, and then they check the documentation on the ban to make sure it was valid, and then they make it a permanent ban. I referenced this months ago as a precaution we put in place to prevent what happened with PunkBuster and FairFight automatically permabanning players. So it is 100% possible that you could have heard about a 3 day ban for cheating, but more than likely that is escalated to permanent before the ban ends. Thanks, Matt
  15. Hi all, I think we’ve gotten a fairly solid discussion around this topic. It’s clear we aren’t going to make everyone happy. But the poll shows more than 50% voting in favor of the skin for everyone who logged in. I know the title is a poor reward to those that actually won, but with our current work load, it’s the best I can do. We will try to avoid the issues in Autumn Assault in the future. i’m going to lock this thread and get my team started on awarding the skin. Thanks, Matt
  16. Hi all, Over the last few months, Little Orbit has created 2 new events and we are about start Slay Bells next week. We added 2FA, a new reporting system, and we’re going to be testing the new engine upgrade and RIOT mode soon. That’s a lot, and we’ve seen what it looks like when we rush things or don’t communicate enough with you, our players. So it’s more important than ever that we re-create the San Paro City Testers (SPCT) to have a group of dedicated players that we can test with to collect feedback. Although this job sounds glamorous, I can assure you these players work hard to make themselves available. They play through buggy content, and they spend time writing up notes to help us fix it. I am very pleased with the team we have selected. I wanted a combination of the best players who have the most availability, and even some who have been our harshest critics. In the spirit of transparency, here are the current members of the SPCT: Shini, Kempington, Skay, Frosi, Rooq, Skitty, CookyPuss, Shakespade, Kevkof, Elanih, Speedz We will be adding more over time. These players are under NDA, however whenever possible, I’ll try to give them approval to post their raw feedback on upcoming events and features, so everyone can track our progress. Thanks, Matt edited: ... for reasons
  17. This is a great question. Copyright Infringement as a category is there purely so large corporations can flag content they want removed that violates their rights in a way protected by law. It would mean that a representative of Nickelodeon would have to get on the system and flag a character selling Sponge Bob pants for real money. Bear in mind by our definition, Copyright Infringement goes well beyond dressing up a character as Sponge Bob. It would generally mean using their character in a way that negatively reflects on them or making money off the content. IMO that scenario is pretty unlikely, but legally, we felt the need to at least support it. Thanks, Matt
  18. Hi Wastelanders, The holidays are officially here! The Grunch Event - December 12 "I hate all those Whoms! How they sing and they shout! I'd love to destroy them, and rip their guts out!" The Grunch had an idea! An awful idea! The Grunch had a wonderful, awful idea! Grunches and Whoms have invaded the Wasteland! Seek out Cindy Loom Whom, found in Spider Hill, New Flagstaff, Trader’s Flat and Los Alamos. If you can stop the Grunch and bring back some of the xmas gifts he stole Cindy will give you a special holiday reward. Players Level 46-55 can take a second mission to earn an exclusive (and antlered) bonus reward. Quest giver: Cindy Loom NPC Locations: Plateau - Spider Hill, waypoint 4680480 4135025, quest available for player level 1-15 Northfields - New Flagstaff, waypoint 4482171 5508380, quest available for player level 16-25 Kaibab Forest - Trader's Flat, waypoint 6524573 5214506, quest available for player level 26-40 Deadfall - Los Alamos, waypoint 5527405 5105450, main quest available for player level 41-55, non-repeatable quest available for player level 55 only Grunch locations: Plateau - waypoint 4682417, 4297973 (for player level 1-15 quest) Northfields - waypoint 4249533, 5451852 (for player level 16-25 quest) Kaibab Forest - waypoint 6766428, 5292237 (for player level 26-40 quest) Deadfall - waypoint 5665130, 5103273 (for player level 41-55 quest) Alpha Zone (Alpha County) - waypoint 6544607, 3920430 (for player level 41-55 quest) Epsilon Zone (Outpost) - waypoint 6309186, 3380807 (for player level 41-55 quest) First Night - December 19 - January 2 Since the Fall, computer glitches and leap years have created controversy over the actual date of the New Year. For decades now, people in all areas of the Grand Canyon Province have used different dates, leading to much confusion. Now, the Archivist Coalition, with the help of LifeNet, has finally determined the actual date of the New Year. In the process of their research, the Coalition has also uncovered a great deal of information about various holidays that had been celebrated in the past. In honor of the establishment of the true date, the Coalition is sponsoring “First Night” a festival that combines many of the holidays past. There might not be any snow in the Wasteland, but citizens from all over the Grand Canyon Province can join together, build some Dirtmen, and wait for the arrival of S.A.N.T.A (the Seasonal Arctic Network of Toy-based Altruism). They’ve been keeping track of who's naughty and nice. The nice get gifts and the naughty get hunted down. Hope you were nice! There will be plenty more celebrating where that came from, as well as holiday missions and goodies. Enjoy party crackers, fruitcake, and festive top hats from gift boxes, or trade the unopened boxes in for a chance to win the ultra-rare white top hat. First Night waypoints for location of questors: Odenville -3989214, 3072292 (player level 2-15) Embry Crossroads - 4237238, 3218729 (player level 2-15) Watchtower - 4511717, 3941784 (player level 8-20) Sunshine Corners - 4565090, 4988004 (player level 10-30) New Flagstaff - 4523486, 5486292 (player level 20-35) Dieseltown - 6094646, 5709645 (player level 25-55) Trader's Flat - 6521150, 5229402 (player level 30-55) Thanks, Matt
  19. Hi all, It's not really feasible for us to award the Top X winners from each session. We don't have that kind of tracking, which is why I didn't offer it in the first place. @Darkzero3802 I understand your frustration. I don't believe I'm setting a precedent here by awarding the skin from an event that didn't go as planned. It's also not feasible for us to create a 2nd skin, but I am looking into awarding a title to everyone who actually got 1st place to give them something unique. Thanks, Matt
  20. Hi there, This is a real problem. I reached out to a couple players yesterday to collect some player information for the devs to look at tomorrow. Apologies, Matt
  21. Hi there, I'm not sure where you heard we were doing 3 day bans on hackers. We have different ways of handling different problems. For toxicity, harassment, and some other issues, we have escalating bans (24 hours, 72 hours, until permanent). Our goal is to help players learn what is acceptable and what is not. For hacking and cheating, there is no escalation. We simply permanently ban. It's unfortunate, as I hate losing players that way, but it takes too long to catch them. Thanks, Matt
  22. Hi there, My apologies. We are looking into this issue. It seems to be a bad interaction between BattlEye and APB on some computers. Unfortunately. BattlEye support hasn’t been very helpful. At this point we are focused on the engine upgrade which will significantly update the underying libraries of APB to 64-bit. It is our hope that the upgrade will help address issues like this. Thanks, Matt
  23. Hi all, Just for clarity, I'm not talking about the Butcher skin at all. I don't know the history, and we shifted away from that skin well before the event started. I do recognize that the current Autumn Assault skin is bugged on some weapons, and it shows red where it shouldn't. That is being fixed. But this thread is just about awarding the Autumn Assault skin to people who logged in during the dates of the event. Thanks, Matt
  24. Less difficult, but still an hour of a dev’s time vs a couple minutes. More than I want to devote.
  25. This is a good idea, but it would take a lot of effort to try and go back through the logs to determine the participants and then sort them by the number of times they played to find a cutoff. I’d rather focus our development efforts elsewhere. It’s fairly easy for us to determine the players that logged in during the weeks the event was active and award those players the skin.
×
×
  • Create New...