M4ttiA's Forum Posts

  • 13 posts

  • My best guess is a browser extension is interfering with Construct and causing a problem. Try disabling any browser extensions you have installed.

    I’ll try that. Anyway I can always export from my iPhone, it works there.

  • The only export option that works is Xcode Export without minifying.

    Any other type fails.

  • Hi, I'm getting this error when I export my project for iOS. I'm using Construct 3 beta r404 with Microsoft Edge on MacOS. I used a backup of my project in version r397 and the same error pops up.

    Here's the console log

  • Event 55, it says set highscore to score without any condition, so it always changes the high score even if the score is lower.

    Ah ok, I didn’t notice it. 😅

  • fex.net/en/s/1ffstv7

    fixed

    Thank you so much.

  • Here’s the project file: 1drv.ms/u/s!AlJYp-O5xIwQ8BsOkfVpv6C84MYN

    Let me know if the link works.

  • If it gets reverted to 0 after a game over, then at what point is it saving correctly ? Because after a game over is the only time we see you save it. I would maybe share the file at this point.

    The GameOver variable gets reverted to 0 after Local Storage is saved.

    The issue is that after the second game over it gets reverted to 0 with no apparent reason.

  • So did you confirm if it is setting high score correctly from local storage on game launch yet ?

    I can confirm that the Local Storage value is set correctly after a new game starts. It gets reverted to 0 if a game over happens after a new game is started though.

    There is a potential bug if game over is set to 1 on game launch but my assumption is it's set to 0 and you set it to 1 when you die.

    You are correct, I set game over to 1 if you die but it gets reverted to 0 on a new game.

  • Update: Local Storage writes the value inside the variable. It only gets reset after a game over.

    I'm going crazy trying to figure out why 😩

  • It's more than likely that Local Storage doesn't write the value inside the HighScore variable, thus leaving it at zero and as a result the Local Storage sets itself to 0 when you play a second time.

  • You can always check what is in your local storage in debug mode.

    The problem is that the LocalStorage gets reset after dying a second time. Basically to test if it was working I would make 2 or 3 points, then do a new game without doing any points to just see if the High Score would be saved.

    The problem is the High Score value inside the Local Storage getting set to the Score value even if it is less than the High Score.

  • Will do. I’ll report back later.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • What could possibly be wrong here?

    Tagged:

  • 13 posts