devtrackers.gg
about 2 years
ago -
Hunt: Showdown
-
Direct link
Transcript (by Youtube)
| 0s | let's move on to our other big topic |
|---|---|
| 3s | because you guys are asking again which |
| 5s | is the servers obviously also a very |
| 8s | very very hot topic right now in the |
| 9s | community and there's a good reason why |
| 11s | as well and uh yeah i see uh people |
| 14s | still asking for a bunch of other bugs |
| 16s | uh with update 1.8.1 we will have a |
| 18s | bunch of bug fixes uh i just wanted to |
| 21s | mention a few as highlights but |
| 24s | obviously as soon as we have the patch |
| 25s | notes you will be able to read about all |
| 27s | the fixes there there's a lot of fixes |
| 29s | yeah the the bug section of this patch |
| 31s | notes is is quite a long one but fun to |
| 33s | read through it's always fun |
| 36s | all right uh for the server issues uh we |
| 39s | want to start by apologizing we know |
| 42s | when the servers get disrupted it can be |
| 45s | very |
| 46s | you know jarring while you're in game |
| 49s | and if you're in the middle of firefight |
| 51s | or you know you're gonna just get out |
| 53s | with that bounty it can be really |
| 54s | frustrating |
| 55s | we know the server issues did escalate a |
| 58s | bit during the live or during the event |
| 60s | and those for a few different factors we |
| 63s | also heard |
| 64s | just to quickly address at the start of |
| 66s | the stream that we're having some eu |
| 68s | server problems |
| 70s | from what we can see on our side we |
| 72s | think they've been resolved for people |
| 73s | who might have been playing hunt as the |
| 75s | stream was getting started but we're |
| 77s | still watching that and |
| 79s | with all our server issues we do try to |
| 81s | address them as quickly as possible |
| 84s | we're watching our discord we watch |
| 85s | |
| 87s | one of my jobs as a us community manager |
| 90s | is that i'm a different time zone as |
| 92s | most of our people located in germany or |
| 94s | eu and that is just so we can spread out |
| 97s | more people over a greater period of |
| 99s | time that we're watching for these |
| 100s | reports we're watching to see when these |
| 102s | server issues happen and we can address |
| 104s | them as quickly as possible right now |
| 106s | our servers are pretty much our top |
| 108s | priority and we are working to get them |
| 111s | more stable and |
| 114s | going forward we've |
| 116s | identified a few different cases that |
| 118s | have caused |
| 120s | these server drops these cases have |
| 122s | included |
| 123s | isp problems that's your internet |
| 125s | service provider |
| 126s | compatibility with them and hunt have |
| 129s | not been great but we're looking into |
| 131s | that we also had some malicious attacks |
| 134s | that happened during the |
| 136s | event this is something else that we're |
| 139s | looking into and we want to be more |
| 141s | protected at against in the future we've |
| 144s | also |
| 145s | had our own system and back-end issues |
| 147s | for the hunt servers themselves so it's |
| 149s | not always |
| 150s | uh you know other people's problems with |
| 153s | the isps and with malicious attacks part |
| 155s | of it is our own system that we're |
| 156s | looking at and we're working to improve |
| 158s | let's just look at the issues a bit |
| 160s | separately and uh what we are doing with |
| 162s | them so as we as ary mentioned we had |
| 165s | some isp issues as well as malicious |
| 168s | attacks basically to resolve the isp |
| 171s | issues in particular |
| 173s | we are looking at other ways considering |
| 175s | alternative approaches to ensure that |
| 177s | our packets are rooted through faster |
| 180s | networks in those cases where it's |
| 181s | needed so obviously it depends on the |
| 183s | isp and then they resurface but we want |
| 186s | to uh ensure this and this should help |
| 189s | if |
| 190s | alleviating the issues sorry for that |
| 192s | and uh yeah as for the malicious uh |
| 195s | attacks uh we already implemented better |
| 197s | protection against them so this should |
| 201s | solve those issues on that and so that's |
| 204s | very good to see let's take a look at |
| 207s | our own systems and our backend where we |
| 210s | also have found multiple issues first of |
| 212s | all since uh we've seen that you guys uh |
| 216s | and seen the server issues ever since uh |
| 218s | they started uh we made it like our |
| 221s | highest priority straight away because |
| 223s | of that we already managed to implement |
| 225s | some fixes |
| 227s | so it should be already much better than |
| 229s | it used to be than it is in our system |
| 231s | and back end we also have a lot more |
| 234s | fixes coming with a future update |
| 236s | it shouldn't be too far away |
| 239s | from 1.8 1.8.1 but it will be a future |
| 241s | update after that and that will tackle |
| 244s | uh like the |
| 245s | majority of the remaining issues uh on |
| 248s | our end |
| 249s | so uh that hopefully will uh |
| 252s | fix most of your problems and also |
| 255s | to make sure that our service is always |
| 258s | in a good quality we are also looking |
| 259s | into other alternatives for the future |
| 262s | uh to make sure it's always good we |
| 265s | really want to uh tell you guys what we |
| 267s | are doing so we will uh release a blog |
| 269s | of this as well uh that will still take |
| 272s | some time because it will be probably |
| 274s | online when the bigger fix arrive in the |
| 276s | future update but uh around that time we |
| 278s | will have a detailed explanation to |
| 280s | these for you as well |