WEBVTT 00:00.050 --> 00:00.530 Hello guys. 00:00.530 --> 00:01.460 Welcome to the video. 00:01.460 --> 00:03.650 So we are in the end of this section. 00:03.650 --> 00:06.560 I did show pretty much everything I wanted to show. 00:06.560 --> 00:09.500 There is one behavior that might feel like a bug. 00:09.500 --> 00:14.450 So I would like to explain, um, if we go to the game. 00:15.400 --> 00:17.110 With two players. 00:19.010 --> 00:19.730 Two players. 00:19.730 --> 00:20.810 Normal. 00:22.190 --> 00:27.830 Okay, so we are in the game and player joins the game one and two. 00:28.250 --> 00:29.240 Here's the second one. 00:29.240 --> 00:36.440 So the live system how it works now allows you not to respond but to die certain amount of times. 00:36.440 --> 00:41.090 So that's like a bit the opposite from expectations that some people could have. 00:41.090 --> 00:44.210 I just realized that in like yesterday. 00:44.210 --> 00:46.310 So let's say we have two players in the game. 00:46.310 --> 00:47.420 One of them died. 00:47.420 --> 00:51.440 There is a second one and you can die one more time. 00:51.440 --> 00:54.920 You can respawn as many times as you like, but you can die only twice. 00:54.920 --> 01:00.200 So if there is still one player in the game and one more dies, you could finish the level. 01:00.200 --> 01:08.090 Potentially this is fine, but if you are in the game with two players, one of you dies and the second 01:08.090 --> 01:10.970 one dies before you respawn just now. 01:10.970 --> 01:13.100 Then game will restart immediately. 01:13.100 --> 01:15.770 It will not allow you to respawn again. 01:16.070 --> 01:20.780 I took inspiration for this from the game that is called It Takes Two. 01:20.810 --> 01:21.890 You probably know the game. 01:21.890 --> 01:23.510 It's a game that you cannot play alone. 01:23.510 --> 01:25.160 You always need two players. 01:25.160 --> 01:26.330 It's called It Takes Two. 01:26.330 --> 01:30.410 So in that game you actually can respawn as many times as you want. 01:30.410 --> 01:31.700 But the game is different. 01:31.700 --> 01:35.210 So here we have to put some limitations because otherwise it would be too easy. 01:35.210 --> 01:41.180 So basically what I'm trying to say that in that game, if two players are dying, they have to restart 01:41.180 --> 01:42.170 from a checkpoint. 01:42.170 --> 01:43.640 That's what they have to do. 01:43.670 --> 01:47.390 And in this case, I did kind of take a similar approach. 01:47.390 --> 01:49.880 So yeah, it's not a bug, it's a feature. 01:49.880 --> 01:54.860 But if you want to have a system where you would have to respawn the player as many times as lives you 01:54.860 --> 01:58.790 have, then probably you would have to rework system just a bit. 01:58.790 --> 02:00.260 Now there are a bunch of errors. 02:00.260 --> 02:05.390 Um, I'm not sure what they are about as they do not interfere with the gameplay, so I don't see a 02:05.390 --> 02:10.070 reason to worry about them on the skin selection UI. 02:11.730 --> 02:13.650 I would like to do one change. 02:14.960 --> 02:16.700 Over here in. 02:18.540 --> 02:19.800 In update screen display. 02:19.800 --> 02:23.400 I have two texts that I update and I do it in two different places. 02:23.400 --> 02:26.640 So I want to place this line of code so it's a bit prettier. 02:27.030 --> 02:28.320 Yeah, and that's it. 02:30.080 --> 02:32.960 Also, there are these variables. 02:34.030 --> 02:35.200 Over here. 02:36.430 --> 02:38.890 With a current skin index. 02:39.070 --> 02:43.270 Skin indexes and player index and current player index. 02:43.270 --> 02:45.640 So now we know how the entire system works. 02:45.640 --> 02:48.520 We don't have a reason to keep it exposed because we don't need to debug it. 02:48.550 --> 02:51.790 We know how it works so we can just hide it. 02:51.790 --> 02:52.660 It's okay. 02:52.750 --> 02:57.610 We don't need to see it in the inspector, although if you want to see it in the inspector, just keep 02:57.610 --> 02:58.240 it as it is. 02:58.240 --> 02:59.170 It doesn't really matter. 02:59.170 --> 03:00.460 It does not change much. 03:00.460 --> 03:00.940 Okay. 03:00.940 --> 03:04.510 When I do this as a private, I'm going to hide it in a. 03:05.400 --> 03:07.080 And let's hide this one as well. 03:07.830 --> 03:13.380 Okay, because we don't need to see those variables now in the inspector unless you really want to. 03:13.380 --> 03:14.430 Then keep it exposed. 03:14.430 --> 03:15.090 It's fine. 03:16.200 --> 03:16.590 All right. 03:16.620 --> 03:19.140 Now my inspector is a bit cleaner. 03:19.140 --> 03:21.330 I know what the things do here. 03:21.570 --> 03:24.990 And other than that, I did not see anything that came to my mind. 03:24.990 --> 03:29.280 So I think it's okay if something comes up, I'll let you know as always. 03:29.280 --> 03:35.250 Also, if someone will report something that have not been fixed, then I'll update video later on or 03:35.250 --> 03:37.110 I will answer in Q&A with a bug fix. 03:37.110 --> 03:37.530 Okay. 03:37.530 --> 03:38.130 Bye bye.