Help with Reposition

Hi I’m trying to make a player’s y position increase by when a certain number when a button pressed so i created 2 functions but when I press then, the y changes but the player’s position also get’s reset to it’s starting position. I have included a video and the code, does anyone know what’s wrong?

https://drive.google.com/file/d/1hYn1i6CD9zBjQO-5eDgV7TmzORX4H-gy/view?usp=sharing

ing System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class MoveY : MonoBehaviour
{
    public Transform playerTransform;
    public Vector2 playerY;
    public Vector2 PlayerY2;
    float goneUp = 0;
    float goneDown = 0;
    void Start()
    {
       
    }

    // Update is called once per frame
    void Update()
    {
       
    }
    public void ButtonUp()
    {
        if (goneUp < 1)
        {
            playerTransform.position = playerTransform.position * PlayerY2;

            goneUp = goneUp + 1;
            goneDown = 0;
        }
     

      
    }
    public void ButtonDown()
    {
        if (goneDown < 1)
        {
            playerTransform.position = playerTransform.position * playerY;

            goneDown = goneDown + 1;
            goneUp = 0;

        }
       


    }
}

To help gain more insight into your problem, I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.

Doing this should help you answer these types of questions:

  • is this code even running? which parts are running? how often does it run?
  • what are the values of the variables involved? Are they initialized?

Knowing this information will help you reason about the behavior you are seeing.

You could also just display various important quantities in UI Text elements to watch them change as you playtest.

If you are running a mobile device you can also view the console output. Google for how on your particular mobile target.

Here’s an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong: