Quote:
And when someone will have 0 or less HP, program should stop running.
But your code is wrong.
This code:
while (hp1 > dmg2 || hp2 > dmg1)
loop as long as 1 of both objects have hp remaining.
And this code:
while (hp1 > dmg2 && hp2 > dmg1)
loops as long as both objects have remaining hp.
And with this code, Tiger is not checked when mause won.
if (dmg2 > hp1) { Console.WriteLine("Mause won!"); }
else if (dmg1 >hp2) { Console.WriteLine("Tiger won!"); }
Try this code instead:
if (dmg2 > hp1) { Console.WriteLine("Mause won!"); }
if (dmg1 >hp2) { Console.WriteLine("Tiger won!"); }
Advice: Mixing indices is a bad idea, it just make things more complicated, it is easier to design so indices match. Like:
if (dmg1 > hp1) { Console.WriteLine("Mause won!"); }
if (dmg2 >hp2) { Console.WriteLine("Tiger won!"); }
-----
Your code do not behave the way you expect, or you don't understand why !
There is an almost universal solution: Run your code on debugger step by step, inspect variables.
The debugger is here to show you what your code is doing and your task is to compare with what it should do.
There is no magic in the debugger, it don't know what your code is supposed to do, it don't find bugs, it just help you to by showing you what is going on. When the code don't do what is expected, you are close to a bug.
To see what your code is doing: Just set a breakpoint and see your code performing, the debugger allow you to execute lines 1 by 1 and to inspect variables as it execute.
Debugger - Wikipedia, the free encyclopedia[
^]
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[
^]
Basic Debugging with Visual Studio 2010 - YouTube[
^]
Debugging C# Code in Visual Studio - YouTube[
^]
The debugger is here to only show you what your code is doing and your task is to compare with what it should do.