Question Lives Remaining until player is dead returns to main menu

Hi,

Hope someone can help on this,

I'm just looking for the best approach for Player Lives Icons and lives remaining until the player is dead and returns to main menu. At the moment I have devised something like this which works but not very well, is there a better way than this am I doing the right approach here or is booleans not the best way?

public GameObject Live1;// Image for lives
public GameObject Live2;
public GameObject Live3;

private bool threeLives;// defines what happen under this condition
private bool twoLives;
private bool oneLive;

if (twoLifes &&! isDead)
{
Live2.SetActive(false);// removes image of live
oneLive=true;// bool set true
}

if (oneLive && !isDead)
{

yield return new WaitForSeconds(2.0f);//
Live1.SetActive(false);
Gameover.enabled = true;//
isDead = true;
SceneManager.LoadScene(loadLevel);/
Time.timeScale = 0;
}

yield return new WaitForSeconds(2.5f);//
isDead = false;// important to bring the player to life again
Live3.SetActive(false);
twoLifes = true;
GetComponent<Playerhealth>().HurtPlayer(-1000);// returns health so can start with health

 

Oh.. I am not able to get my head around this.. Why this complicated? Why not just use a counter?

 

Thankyou for the responses, I know I do that a lot at the moment tend to over complicate things. I think its because of my limited knowledge I'm resorting to just what springs to mind at the moment, but I really like the sound of a counter Idea. I have never used that method before do you have any examples at all?

 

This is not Google. You want to start there. You want to iteratively ask yourself, "Can I...??"

Like this:

Imphenzia: How Did I Learn To Make Games:

Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration:

How to do tutorials properly, two (2) simple steps to success:

Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That's how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.

Fortunately this is the easiest part to get right: Be a robot. Don't make any mistakes.
BE PERFECT IN EVERYTHING YOU DO HERE!!

If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.

Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.

Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.

Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there's an error, you will NEVER be the first guy to find it.

Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!

Finally, when you have errors, don't post here... just go fix your errors! Here's how:

Remember: NOBODY here memorizes error codes. That's not a thing. The error code is absolutely the least useful part of the error. It serves no purpose at all. Forget the error code. Put it out of your mind.

The complete error message contains everything you need to know to fix the error yourself.

The important parts of the error message are:

- the description of the error itself (google this; you are NEVER the first one!)
- the file it occurred in (critical!)
- the line number and character position (the two numbers in parentheses)
- also possibly useful is the stack trace (all the lines of text in the lower console window)

Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors. Often the error will be immediately prior to the indicated line, so make sure to check there as well.

Look in the documentation. Every API you attempt to use is probably documented somewhere. Are you using it correctly? Are you spelling it correctly?

All of that information is in the actual error message and you must pay attention to it. Learn how to identify it instantly so you don't have to stop your progress and fiddle around with the forum.

 

Thanks, I like this. Just creating half the solution with trial and error I'm pretty much there, it's probably not the best solution but hey it's fun and working and I can improve on, need more patience