Skip to content

Privacy issue with game.json files? #867

@ghost

Description

In game.json files, in the properties section, there's a projectFile key whose value is the absolute path to that game.json file on the developer's computer. I'm wondering if, considering these game.json files are often distributed online (be it for testing, support, or release), there's a privacy issue here...?

This value allows you to potentially see:

  • The directory structure of the developer's computer
  • The developer's computer username
  • Various directory names on the developer's computer

Is this key/value necessary? When I download someone else's game.json file and run it, it works perfectly fine (even though that directory path doesn't apply to my computer).

In addition, I can change the name of my game.json file (e.g. to my-super-awesome-game.json) and it still works, even though this directory path value still points to the old, now non-existent, game.json file... It's only when I save the game in GDevelop that this value is updated.

That leads me to think this key/value isn't needed, but maybe there's a purpose I'm missing...?

Metadata

Metadata

Assignees

No one assigned

    Labels

    question👌good first issueGood issue if you want to start contributing to GDevelop

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions