koobas.hobune.stream
How do I get my game to remember player input and perform those actions later?
Hi, I am creating a game which involves the player planning his actions before initiating them.
I have a smaller "ghost" object which is controlled using basic translate position buttons.
What I am wondering is if there was a way to get my game to remember which buttons where pressed and in what order?
The hopes is that once the player has planned out his string of actions they will press an "Action" button which will perform the actions for the player in the sequence they had chosen but on the real player object, not the ghost object which they used to plan their turn.
I hope that made sense.
You could use a Queue since you probably want to execute the first pressed action first. Then you need to decide in what type you store the inputs (strings, ints etc). Assuming you use int this would mean:
Button1 = 0
Button2 = 1
and so on...
Using C# this would look something like this:
// Initialize the queue at start
Queue<int> userInputs = new Queue<int>();
...
// On user input (nuberOfInput is of type int)
userInputs.Enqueue(nubmerOfInput); // Enqueue(0) for Button1
...
// On "Action"
nextButtonNumber = userInputs.Dequeue();
Note Enqueue() puts one element in the queue and Dequeue() removes and returns the first element in the queue so you have to call it repetitive.
Edit Sticking to the queue attempt (maybe not the most elegant):
public class PlayerController : MonoBehaviour
{
private Queue<int> playerInput = new Queue<int>();
public void MovePlayerForward()
{
playerInput.Enqueue(0);
}
public void MovePlayerBackward()
{
playerInput.Enqueue(1);
}
public void MovePlayerLeft()
{
playerInput.Enqueue(2);
}
public void MovePlayerRight()
{
playerInput.Enqueue(3);
}
public void RotateRight()
{
playerInput.Enqueue(4);
}
public void RotateLeft()
{
playerInput.Enqueue(5);
}
public void OnActionButtonPressed()
{
while(playerInput.Count > 0)
{
switch(playerInput.Dequeue())
{
case 0:
transform.Translate (0, 0, 1);
break;
case 1:
transform.Translate (0, 0, -1);
break;
case 2:
transform.Translate (-1, 0, 0);
break;
case 3:
transform.Translate (1, 0, 0);
break;
case 4:
transform.Rotate (0, 45, 0);
break;
case 5:
transform.Rotate (0, -45, 0);
break;
}
}
}
}
You can also put the while in a coroutine or adjust it to fit your needs because now the actions happen pretty fast. Or if you want it turn by turn just remove the while-loop.
In case you also need to record the times between the button presses let me know.
If this is not turn based but rather anlogous movement, you probably also need to record when and how long each button was pressed (record pressed timestamp and released timestamp). If the key presses are used to move physics objects and you need the system to be deter$$anonymous$$istic, you probably have to record and play back all the actions in fixedUpdate() and store the number of fixedUpdate it happened.
good point! I should add that my answer is based on the statement "... which buttons where pressed and in what order?"
I updated my answer have a look. The numbers 0 to 5 stand for the different buttons pressed. I hope this is the behaviour you want to achieve.
Exactly, something like:
public void OnActionButtonPressed()
{
StartCoroutine(StepbyStep());
}
IEnumerator StepbyStep() {
while(playerInput.Count > 0) {
switch(playerInput.Dequeue()) {
// cases same as before
}
yield return new WaitForSeconds(1.0f);
}
}
Good job helping a dude out! One "best practices" kind of detail that everyone should always stick to I$$anonymous$$O... you could use constants ins$$anonymous$$d of "magic numbers" 0-5. So declare
public const int $$anonymous$$EY_FWD = 0;
public const int $$anonymous$$EY_BAC$$anonymous$$ = 1;
public const int $$anonymous$$EY_LEFT = 2;
public const int $$anonymous$$EY_RIGHT = 3;
public const int $$anonymous$$EY_ROT_R = 4;
public const int $$anonymous$$EY_ROT_L = 5;
and use those everywhere
public void RotateLeft()
{
playerInput.Enqueue($$anonymous$$EY_ROT_L);
}
...
switch(playerInput.Dequeue())
{
case $$anonymous$$EY_FWD:
transform.Translate (0, 0, 1);
break;
It makes everything more readable and if you need to change one of those numbers later (lets say you find out you can't use 0 as a code for forward because of some encoding problems),this way you only have to change it in one place!
