devtrackers.gg
over 2 years
ago -
Hunt: Showdown
-
Direct link
Transcript (by Youtube)
| 0s | yeah i think we have a bunch of gameplay |
|---|---|
| 2s | changes |
| 3s | uh we have to talk about so let's just |
| 6s | dive into it i think and uh starting |
| 8s | with the changes to the team details uh |
| 10s | screen after the games |
| 12s | i must say like i'm really amazed uh |
| 14s | just like i mean this being mostly a |
| 16s | service update has been like discussed |
| 18s | in the past right like um getting |
| 20s | stability back and getting performed |
| 21s | seven we still had a chance to put quite |
| 23s | a lot of gameplay stuff and i'm really |
| 24s | happy about all the level changes that |
| 25s | tom was presenting for level designers |
| 27s | and hopefully we can add a couple more |
| 29s | now in this part |
| 30s | yeah and there's some very exciting |
| 32s | stuff in there i can |
| 33s | absolutely absolutely i mean this is |
| 35s | mostly again also like thematically what |
| 37s | you can expect today is thematically |
| 38s | close to like the |
| 40s | the service nature of things so expect |
| 42s | lots of balancing lots of like |
| 43s | improvements uh rather than completing |
| 45s | new features |
| 46s | but that's what we announced before so |
| 48s | let's first talk about the team details |
| 51s | changes so just to recap the team |
| 52s | details that's the screen that you can |
| 54s | access at the end of a match to kind of |
| 56s | see what team consolations have been in |
| 59s | that last match of years like what's the |
| 61s | mmr ratings or was it a fair match or |
| 63s | not of the information that you can kind |
| 65s | of like take from that screen |
| 67s | but so far |
| 68s | we've only ever seen the information |
| 70s | next to each of the players that was |
| 72s | listed there in relation to yourself so |
| 74s | you couldn't really understand like how |
| 76s | this guy might have interacted for |
| 77s | example with one of your partners and |
| 79s | that's what we're adding to the screen |
| 81s | now to give you a better full picture or |
| 83s | closer to a full picture of what was |
| 85s | happening during the rounds in order to |
| 86s | make draw conclusions and kind of |
| 88s | replayed around a little bit in your |
| 89s | head and see like okay what is this guy |
| 91s | i had problems with or was this that guy |
| 94s | that killed me |
| 95s | so you can kind of like see the yeah the |
| 97s | missing pieces |
| 99s | and the yeah so uh |
| 101s | this also introduced some new uh color |
| 104s | for this so people can understand |
| 106s | exactly what you said so how it relates |
| 108s | to your partner how it relates to you |
| 110s | and everything is color coded now and |
| 112s | actually then is prepared a really |
| 113s | really cool scenario which we will go |
| 116s | through in a second |
| 117s | really cool i mean yeah it's like a very |
| 119s | specific gameplay scenario and then |
| 121s | after uh game detail screen and we will |
| 123s | be able to explain everything on that so |
| 125s | thank you for preparing that dennis as |
| 127s | well |
| 128s | we thought that maybe it's just better |
| 130s | to quickly run through an actual example |
| 131s | um um so |
| 133s | uh we'll have a look at it in a second |
| 135s | then part of that will also be that we |
| 137s | now have timestamps uh on the different |
| 139s | actions so you can kind of like better |
| 140s | remember okay what's this at minute 13 |
| 142s | was it many minutes um |
| 144s | 45 like you will know from that um by |
| 148s | looking at the timestamps which will |
| 149s | appear if you just hover over each of |
| 151s | these items it will be really cool like |
| 153s | you can kind of recap the whole game in |
| 154s | your head that way and see what happened |
| 156s | when exactly but let's look at our uh |
| 160s | sorry uh i forgot the very important |
| 162s | icon |
| 163s | yeah the last one is we also added one |
| 165s | uh so we had one already for bounty |
| 167s | possession in there like so you could |
| 169s | see which player had a bounty uh in the |
| 172s | position but he didn't know whether to |
| 173s | actually made it out or not uh that's a |
| 175s | difference we've now added as well so |
| 176s | you can see who actually took the bounty |
| 178s | out in case you were still in the match |
| 179s | when that happened obviously because |
| 180s | everything in that list is only to the |
| 182s | point you leave the session yourself but |
| 184s | it can help you differentiate a little |
| 186s | bit who was a team that extracted who |
| 187s | was the team that maybe had the bounty |
| 189s | but then lost it along the way |
| 191s | sounds awesome so yeah let's look at our |
| 193s | scenario |
| 195s | our example that you |
| 197s | so created with me on this one for a bit |
| 199s | uh obviously so we have an example here |
| 202s | this is like a contract with two bosses |
| 204s | uh in that contract you've had uh one |
| 206s | duel players a and b a solo player c and |
| 209s | another solo player d |
| 211s | now what happened |
| 212s | so |
| 213s | a and b the duo they killed the bosses |
| 216s | and took the bounty so they run around |
| 217s | with four bounty tokens |
| 219s | now b of that team is being snapped by d |
| 222s | but gets revived without further |
| 223s | interaction so like |
| 225s | long range shot maybe um guys being |
| 227s | revived they move away the other guy the |
| 230s | sniper b cannot follow them no further |
| 232s | interactions between the two teams |
| 234s | however on the way out c also ambushes a |
| 237s | and b |
| 238s | kills them and takes two of the tokens |
| 240s | keep in mind with two bosses four tokens |
| 242s | as a solo he can only bring two tok like |
| 244s | tokens out of the mission so obviously |
| 246s | he takes what he can get leaving some |
| 247s | behind then c leaves the mission uh um |
| 251s | basically taking the bounty home without |
| 253s | encountering d so it's a very very basic |
| 256s | a very very um straightforward scenario |
| 258s | and let's have a look at what this would |
| 260s | look like afterwards in the team details |
| 261s | and the question is what happened to x |
| 265s | and how many apples he had yeah |
| 269s | so yeah this will become much clearer |
| 272s | but i think it's important to run |
| 273s | through this because you guys will need |
| 274s | some context as the screen usually is |
| 277s | only really readable to you based on |
| 279s | your own session experience so i have to |
| 280s | kind of build a little bit of a fake |
| 282s | session with your hands so we can talk |
| 284s | about it now in this particular case |
| 285s | what you see is this is the perspective |
| 287s | from player b |
| 288s | um |
| 289s | so his teammate player a you will now |
| 291s | have a marked in in the color blue so |
| 294s | kind of like to know that this is your |
| 295s | teammate this is also relevant because |
| 297s | on the right hand side you see how icons |
| 300s | with a blue background are now basically |
| 302s | or from the perspective of your teammate |
| 304s | so what happened in this particular |
| 305s | scenario here is is that |
| 308s | player b |
| 309s | got killed by player d |
| 312s | so that was the sniper in the beginning |
| 313s | he was then picked up probably like a |
| 316s | red scar revive of some sort he might |
| 317s | have died to ai before we don't know |
| 319s | that from the screen |
| 320s | and then later on |
| 322s | he was also downed and then killed by |
| 326s | player c who then took the bounty it |
| 328s | seems because he extracted with two |
| 330s | bounty tokens players see that this so |
| 332s | again you now have a better |
| 334s | understanding that like this guy here |
| 336s | actually downed your partner he killed |
| 339s | you there might have been some revives |
| 341s | going on there and he then took the |
| 343s | bounty and left so just gives you a bit |
| 345s | more detail give a bit more context and |
| 347s | we're gonna look at this now from |
| 348s | different angles as well yeah but just |
| 350s | to |
| 351s | explained again the blue color is always |
| 354s | related to your partner and the white |
| 355s | exactly as always yeah exactly so so |
| 358s | player c has downed your partner and has |
| 360s | killed you |
| 362s | so |
| 362s | what else expired like transpired there |
| 364s | we don't know but that's the key |
| 366s | information now now we look at this from |
| 367s | the perspective of player c that's the |
| 369s | killer like the one that that ambushed |
| 370s | so he sees basically the the duo and he |
| 374s | sees that |
| 376s | he |
| 377s | killed one of the duo so this is a new |
| 378s | variant of the skull icon you see little |
| 380s | headshot icon little little bullet |
| 382s | impact on the top there so whenever it's |
| 384s | affected that player that you see |
| 386s | in the list then it is um with a little |
| 389s | skull it can be blue if it was a |
| 391s | teammate for example or it can be white |
| 392s | if it was you the same for the deaf one |
| 394s | you see right underneath that |
| 396s | and if it's a normal icon the one that |
| 398s | you're familiar with because you see it |
| 399s | when your partner is down or you see it |
| 401s | on the map that is when someone did |
| 403s | something to your partner so it's |
| 405s | important to differentiate between these |
| 407s | two but obviously the tooltips we will |
| 408s | see in a second they'll put context to |
| 410s | it so what we see here is that uh play a |
| 413s | guard down player b got killed |
| 416s | and both of these guys had two tokens at |
| 418s | one point but since there isn't a little |
| 420s | extraction icon to decide they |
| 422s | apparently didn't make it out of the |
| 423s | mission |
| 424s | and then with player d there was no |
| 426s | interaction |
| 428s | and now looking from player d's |
| 429s | perspective again |
| 430s | he also had some interaction with player |
| 433s | b like he sniped him from a distance he |
| 435s | didn't have any interaction with player |
| 437s | a and both of those had like bounty |
| 439s | tokens but again they didn't make it out |
| 441s | but player c the one he didn't have any |
| 442s | interaction with um actually took the |
| 445s | bounty and extracted with it but they |
| 447s | didn't meet at all so rather |
| 450s | straightforward just gives you a bit |
| 451s | more information and we'll see that with |
| 452s | the tooltips now and i think in the next |
| 454s | one what actually means so like if you |
| 456s | if you take a look now at player c's |
| 458s | line um the blue one here is that |
| 461s | uh basically this hunter downed your |
| 463s | teammate and then you see the timestamp |
| 464s | and when exactly it happened |
| 466s | and then with the next one |
| 468s | you can see actually multiple events |
| 470s | here and this is something which is a |
| 471s | little bit of a bug at the moment |
| 473s | because normally if there's multiple |
| 474s | events you would see little yellow icon |
| 477s | on the bottom right corner um of each of |
| 479s | those just to denote that there's more |
| 480s | things that that occur there in case |
| 482s | there's multiple actions that wasn't in |
| 484s | the in this example where we took the |
| 485s | screenshots from but still you see he |
| 487s | kind of downed you at one point and then |
| 488s | he killed you a little bit later so |
| 490s | probably that guy got killed during the |
| 491s | revive or right after uh since it was so |
| 493s | close to one another and then the last |
| 495s | one here is the bounty |
| 496s | point so he kind of took two bounty |
| 498s | tokens here |
| 499s | and then he extracted with a bound a |
| 501s | little bit later down the line so again |
| 503s | just gives you a bit more context of |
| 504s | what's going on adding now the |
| 506s | information of the teammate into this as |
| 507s | the primary thing but also giving you a |
| 509s | bit more context to what happens with |
| 511s | the bounty in terms of possession and |
| 512s | extraction yeah exactly and uh |
| 515s | i saw that some people think this was |
| 516s | confusing it's because we looked at from |
| 518s | three different teams perspective but |
| 520s | when you have the two tips and when you |
| 522s | get used to it it's quite |
| 523s | straightforward and uh you get much more |
| 526s | information out of the game actually |
| 527s | than before so i think it's a great |
| 529s | change yeah so it was important to just |
| 531s | run through this example now because |
| 532s | people want to probably rewind a little |
| 534s | bit afterwards and just like take notice |
| 535s | and and dissect it but this will be so |
| 537s | clear the moment you will be on the |
| 539s | tester and actually try it out |
| 540s | yourselves it just adds more information |
| 542s | to the rules that you already have it |
| 543s | just refines a little bit more |
| 545s | and also please check on the the patch |
| 548s | notes then later on where you can see |
| 550s | this all written down a little bit more |
| 551s | in detail as well |