Renaming the Game File

[Bernie]

I'd like to rename my game executable to something like game.run (instead of game.exe). The reason is, I want to have a splash screen with buttons such as 'play game', 'help' and 'run setup'.

This works great so far. The only problem is, the AGS setup refuses to work with a renamed file. Yet all it seems to do is set a bunch of values in a config file.

Any ideas? I tried renaming the folder, but that doesn't work in this case.

Thanks!

[Khris]

All winsetup does is call the exe with the additional parameter "--setup".

You could try a batch file with "game.run --setup"
Might not work because of the missing ".exe", though.

[Bernie]

It works just fine with that parameter, and I don't even need the setup file now. Thanks!

[Gilbert]

If it's your own game, rename the folder for the original game files and recompile, the reason is when you save a game in AGSedit the executable's name was added to the content of winsetup.exe so what winsetup.exe does is just launch [game.exe] --setup, and so if you rename your game winsetup.exe won't work anymore.

But of course if you have a frontend, just invoke game.exe --setup directly with the frontend.

[Bernie]

There's a chance you may have misunderstood my original question. Renaming the folder always makes .exe game files. I wanted a .run game file you can't execute with a double-click, so renaming the folder wasn't a solution. Using the parameter works just fine, so all is well!

If it's your own game, rename the folder for the original game files and recompile, the reason is when you save a game in AGSedit the executable's name was added to the content of winsetup.exe so what winsetup.exe does is just launch [game.exe] --setup, and so if you rename your game winsetup.exe won't work anymore.

But of course if you have a frontend, just invoke game.exe --setup directly with the frontend.

[Gilbert]

Ah you renamed also the extension.

But then:

But of course if you have a frontend, just invoke game.exe --setup directly with the frontend.

which is better than the indirect way of further invoking a setup.exe anyway.