Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

GMEdit

A high-end code editor for all things GameMaker · By YellowAfterlife

Code Getting Randomly overwritten on Windows 10

A topic by Z. created Apr 03, 2018 Views: 436 Replies: 2
Viewing posts 1 to 2

First off. This tool is incredible and it's changed the way I work with Game Maker so thank you so much.

However, I'm on the most recent version of GMS 1.4 on Windows 10, and I'm having some issues with code not updating or getting overwritten seemingly by GMS. This is how it usually goes down.

  • I make a change to a file in GMEdit
  • I save the edited file, and then run the game to test it.
  • Randomly, a small percentage of the time, I run the game and the changes aren't present. When I go back to GMEdit the code has reverted to an older version of the code (I can see the code physically change as soon as I tab back to the GMEdit window), forcing me to figure out what has changed and what hasn't to get it back to a workable state.

I haven't been able to reliably reproduce the bug but it seems to be more prevalent if I run the game very quickly after I save. To add another wrench to this problem I had a moment last night where I loaded the game up and somehow one of my objects had reverted to a version that was 2-3 revisions old. I had run the game to test 10-20 times just fine after making those edits.

Initially I thought it might be because I was using Dropbox as a backup and a syncing error was happening but turning off Dropbox didn't fix the problem.

For the moment I'm just being very careful and every time I save I do a CMD+A / CMD+C to make a "backup" of what I'm working on in case it doesn't properly take but that's not really tennable when I'm working across multiple files.

Let me know if there's any additional information you need!

Developer(+2)

GMEdit makes backups automatically whenever hit Ctrl+S - you can access them by right-clicking any tab.

I think the primary thing that results in GMS1.4 overwriting changed files is opening them in GMS and then closing while saving changes - this stores the file in the memory and it usually will no longer check for changes on disk and may decide to overwrite the current version with the one from memory when saving. As per other topic, this happens more rarely if you have version control enabled for the project (even if you don't actually use it)

Ok awesome. That's great to know about on version control. I saw the other topic but I wasn't sure if this fell in to the same boat. I wasn't aware of the right-click tab interface but that definitely provides the fallback I needed to deal with the occasional issue. Thanks :)