codeYeTi

Congrats. You don't like the game anymore. Now the rest of us can move on and talk about what we'd all like, rather than... just complain about something we don't even play? The rest of us are going to talk about what we would like to do about things, so we can all have some fun.

Just because you're not playing doesn't mean others aren't still enjoying it.

Agreed. I don't really think that medics doing DP's instead of their job(s) was really even a factor in this, though I could be wrong. Personally, I've never been on medic and seen someone overtly neglecting revives to do DP's instead unless there's another medic already responding to everything. If they're missing revives, it's almost always something else causing the distraction (in my experience). I was actually the one that fixed them... immediately after playing some medic and seeing they were fucked . I don't know if it matters at all, but you do have the timing reversed there. The reason they were broken for so long at that point, was because nobody noticed they were busted because they were so useless that nobody was doing them. Personally, I think the civ DP's are a little more interesting due to higher variety in location(s), but I see no reason for them to have any difference in values, if that's what people would want. I'd agree that they got absolutely destroyed in the nerfs... a year? ago. Now here's where we start to disagree. Taking risk and putting your skill to the test against those who would counter your objectives is kind-of... a pretty darn core mechanic for the game. Start a fed? Fight the cops there to counter. Doing a run? Deal with potential threats from APD and other civs by either riding under the radar, or rollin' around with your cock out ready to fight. Want a gang base? People are definitely going to come and counter you. The game isn't designed to be 0-loss-risk, and the frustration that comes with losing is part of what makes it feel good to successfully do/rob a run. As far as the statistics go, DP's were actually being utilized pretty heavily by new players who are trying to build up their initial bank account to "catch up" to the already-set-up player base (from what I've been told). It sounds like you probably think that the changes that were made to attempt to rebalance the few prominent experienced players using them extensively went too far; that's surely a more productive way to put it compared to "devs and whomever just nerf shit". Building adversarial relationships doesn't exactly do much to foster progress, at least in my opinion. Take this with a grain of salt, as I wasn't super-involved in this particular decision, but here's how I see it. I agree filling your time between other events/calls/etc. with DP missions is a fine activity; I do it plenty on medic. The problem comes from how "content" interacts for multiplayer experiences. Doing a run generates content for those who are robbing. Robbing generates "content" for those doing runs. Starting federal events generates content for cops. Playing cop generates content for those doing feds/runs. Unfortunately, activities with less player-to-player interaction generate less content for others playing the game, and therefore make the experience feel more "dead" and like it's hard to find something going on. Therefore, the way I see it, doing something to incentivize playstyles that encourage interaction can help the server as a whole, making it feel less empty, and less like a grindfest. I won't speak to the actual numbers of this specific change since I wasn't that involved, but I agree with the sentiment that they should be still at least somewhat rewarding, to fulfill those that enjoy them, but I definitely think that activities that improve the game for others should be encouraged over more "solo" activities in the long run. I look forward to the montage of you actually attempting to make this rate of $ doing this. I'd love to see the attempted landing points

I like how I've spent my entire day on your gang base and you're over here acting like a 4-year-old who feels entitled to the valuable time of people who fucking volunteer to make a game for him. Back-end infrastructure changes are the only way we're going to move past the performance issues we're seeing these days. If you knew the amount of time that was being invested to deliver you the game you play, and how little reward there is for it, I don't think you'd be behaving like this. "futurecept", the new I/O backend, was the culmination of 500+ hours of work, and has grown to ~1/5 the size of the mission as a whole in terms of lines of code, at least. With it, we are seeing tangible benefits, including 7500% performance increases in some functionality. Changes of this size are going to have some growing pains, even with the literal 50+ hours spent on just fucking testing. If you want to do the work, be my fucking guest. Until then, why don't you try to work with us instead of just wandering around like a whiny twat? I refuse to believe you're being 100% serious here; I don't think anyone can have that few brain cells. I'm sorry for coming off unprofessionally here, but but pouring a bunch of my life into thankless shit and then getting told off by the person I'm trying to help is a bit of a motivation killer my dude. Comparatively to things like "futurecept", the taxi system took one of our guys little more than an afternoon. Are there some inefficiencies in our processes that cause things to still take longer to get released even though they were developed quickly? Sure. But, I think you're misunderstanding how much development time goes in to various things. The taxi system took very little effort, from a very small amount of the team. The gang base changes that are in progress required reworking something in order to get the result that you desired; rather than just half-assing it, we're putting the work in to do it correctly so that it's a system we can work with going forward. Even if some of these smaller features were taking up as much of our effort as you seem to think, they're important to someone, which is why they decided to pick up that task. If you want to take it upon yourself to sit in TeamSpeak with me all day and work through the issues on gang base to accelerate the process, you're more than welcome to do so, but until you're willing to put the effort in to be a team member instead of just a third party advisor/complainer, then I don't really see you having any room to continue opening your mouth. Hopefully this literature is more your speed. https://americanliterature.com/childrens-stories/the-little-red-hen

Yes.

copied from my status update by request When Server 2 opens today (8pm EDT), it will be running a very new experimental I/O backend we've written from scratch over the past couple of months. We've done this as an attempt to improve the less-than-desirable server performance we've been seeing at high population levels over the past while. While we're not expecting any issues, due to this being quite the experiment, with changes to database interaction/logging, and other core components, YMMV with respect to receiving comp if things are just completely crashing. Obviously, admin staff may pity you if it's something huge, but please understand that comp is not guaranteed, and avoid submitting requests, especially for small stuff like losing a loadout to a server crash (if it happens, that is *fingers crossed*). If you want to help, play a bit of S2 tonight to help give 'er a decent day 1 stress test! I've spent an insane amount of time on this system over the past 4 months or so to try and get our server performance up to a livable level, so thank you for pardoning my dust as we work on rolling this out to production workloads!

EDIT: We are working on it.

Yea you can hear which rebel a hatchback coming in to bottleneck went towards while sitting on window, so it's pretty good.

Look what happens when ya put in bug reports! RE: rangefinders - Uhhh no I didn't know rangefinders were fucked as well. put another bug report in and I'll remember to do it.

I wrote a lot of the disputes system on the in-game side, and making sure that the right player(s) were in the list without it's size being completely unmanageable took a few tricks. After talking to you in game yesterday, I identified at least one way that one's name would not show up, and a resolution is being worked on. As with any new system, there are a few kinks to work out after the first pass. If someone was in game, and you try to submit a dispute against them immediately thereafter, their name should be present; if it's not, then we'll get that fixed. The likely cause of nigh all of the incidences of a player's name being missing from the creation menu has been identified, and a fix is in the works. It's important to remember, though, that disputes were designed to be submitted relatively close to the time of the incident, akin to a "wtf rdm" text from yesteryear, but with the ability to include recently disconnected players in possible recipients. I agree this selection style still isn't perfect, and hearing things like this can help improve it While not ideal, even in it's current state, the player's last seen time is shown on the following screen when you're filling in a Subject and Description; this would at least allow you to tell whether or not you selected the correct one at that stage. I agree that some way of displaying that info on the initial selection menu would be nice, I just didn't find a decent way to do it in a compact enough manner on this first pass. I'll play with a few things and see if we could come up with a decent way to display that earlier without cluttering the list making it even harder to read / sort through. Before they were separated by faction, it was even harder to find people when the list was super full. I definitely agree adding more hints like that could help.

Retracted since apparently I don't know how to tag people on the forums

That would explain it. The OVH issues on S1 before we switched back would explain that.

I could just be nuts, but I feel like the frequency with which I see the latter is much greater now than two years ago. Would be interesting to see the actual root cause if anyone from BI ever gets to the bottom of it.