devtrackers.gg
over 2 years
ago -
Hunt: Showdown
-
Direct link
Transcript (by Youtube)
| 0s | so let's look at the service side of uh |
|---|---|
| 4s | everything that happened after update |
| 5s | 1.8 i believe |
| 8s | including the event as well so we wanted |
| 10s | to go over some of the |
| 12s | reasons for the recent issues this is |
| 14s | primarily going to go with the servers |
| 17s | that were having problems during the |
| 19s | event and maybe a little bit beforehand |
| 22s | but uh like it's very important to |
| 25s | mention for the update side of things |
| 27s | that |
| 28s | the recent reasons for uh the issues |
| 31s | were caused by manufacturers for 1.8 uh |
| 34s | one was our traitor's moon campaign |
| 37s | which is obviously we had planned |
| 39s | traitors moon uh |
| 41s | like earlier in time at a certain date |
| 43s | and we set up multiple campaigns uh with |
| 46s | that with like that includes team |
| 47s | highlighting uh steam sales and multiple |
| 51s | uh other campaigns |
| 52s | with third parties social media all that |
| 55s | was set up for traders moon update 1.8 |
| 58s | came out on test servers and |
| 61s | we had a very limited time frame for the |
| 64s | update itself and unfortunately due to |
| 67s | our mistake we misjudged the quality of |
| 69s | the update after testing and released |
| 71s | 1.8 |
| 73s | uh in a state that we didn't want to |
| 75s | release it in so |
| 77s | yeah as you guys know there were |
| 78s | multiple bugs and issues in the update |
| 81s | that |
| 82s | could have been uh |
| 84s | obviously uh could have been fixed |
| 86s | earlier |
| 87s | uh but this led to multiple hot fixes |
| 91s | from our side and downtime that we |
| 94s | really did not want to have to do during |
| 96s | the event but was needed to get those |
| 98s | hot fixes out we learn from our mistakes |
| 101s | this allows us to learn in the future |
| 103s | and allows us to not |
| 106s | make the same mistakes again we are |
| 107s | focusing on the stability and quality of |
| 109s | each update |
| 110s | so again we want the test servers to be |
| 113s | a very important part of this on pc |
| 116s | and actually have the time to fix the |
| 118s | issues and not release them and make |
| 119s | sure they are |
| 121s | as good as they can be and yeah also |
| 125s | this way we want to allow more times for |
| 127s | us to work on the updates and also the |
| 129s | fixes to these updates thank you for all |
| 131s | of you understanding the issues we are |
| 133s | sorry for all done we appreciate your |
| 135s | patience we know it can be frustrating |
| 138s | when there's an event going on and |
| 141s | you're just seeing a bunch of issues all |
| 142s | over the board |
| 144s | and we know that can make the event feel |
| 146s | worse in the long term and we don't want |
| 149s | that to be the sentiment when an event |
| 151s | comes so we're listening to the feedback |
| 153s | and we do want to do better exactly and |
| 155s | the since i in the chat i already seen a |
| 158s | bunch of questions about different bugs |
| 160s | so obviously with uh the four hotfixes |
| 162s | we had uh in this period we fixed uh |
| 165s | most bigger bugs but there's a few that |
| 168s | you guys have been asking about like the |
| 170s | romero edius bug |
| 172s | uh the that bug will be fixed in this |
| 174s | update uh also for console players the |
| 177s | quick swap uh issue where |
| 180s | it like resets itself and doesn't work |
| 181s | properly that will be fixed as well and |
| 184s | the |
| 185s | the leather bug is a another issue that |
| 187s | obviously you guys all know about and we |
| 189s | also posted about |
| 191s | so that is being worked on but uh it |
| 194s | will most likely not make into this |
| 195s | update yet because it is a much uh more |
| 198s | a bigger issue and we actually have a |
| 200s | smaller note about this so going over |
| 202s | the uh the latter exploit is a little |
| 205s | bit more explanation because we are |
| 207s | still working on this on our side but we |
| 209s | know it can be frustrating because it's |
| 211s | in the game and it can be exploited |
| 214s | as far as the |
| 216s | exploiting side we are still |
| 218s | going over all the reports that are |
| 220s | coming in and people who are exploiting |
| 222s | that system we are addressing on our |
| 224s | customer service side |
| 226s | please read over our hon showdown code |
| 228s | of conduct |
| 230s | that we have on our website we do |
| 232s | mention that exploiting the game can |
| 233s | result in actions being taken against |
| 236s | you and we hope you remember that |
| 238s | because there are people who are still |
| 239s | trying to abuse this |
| 241s | the reason this is taking longer than |
| 243s | than what we would want is the climbing |
| 245s | is |
| 247s | the climbing system in hunt is one of |
| 248s | the oldest systems that we've put into |
| 250s | the game there have been other newer |
| 252s | movement systems that have clashed with |
| 254s | that ladder climbing system and because |
| 257s | of that it's causing kind of a larger |
| 259s | issue that we're having to address but |
| 262s | we are still working on it we're still |
| 265s | addressing all the reports and we hope |
| 267s | to get this fixed as soon as we can so |
| 269s | thank you for understanding and again |
| 270s | please if you see someone using the |
| 273s | exploit which is uh very easy by |
| 275s | spectating them after they killed you |
| 276s | please report them in game as well as if |
| 278s | you can capture a video of it and send |
| 280s | it to our customer support on our |
| 282s | website |
| 283s | because we are indeed banning players |
| 284s | using this exploits right now so it's |
| 286s | very important that you guys actually |
| 288s | report them to us |