To simplify game management in TWGS, I would like to remove the ability to specify a custom game directory for a game. Instead, the game will always go into the directory at [TWGS]\GAME\GAMEA, [TWGS]\GAME\GAMEB, etc, depending on the menu letter of the game. Does anyone rely on the ability to set a custom directory for games?

Also, the game will no longer support changing the root directory. Of course it will be possible to do this from the registry, but that will not be supported behavior. If the root directory is changed, the next time the game is run it will move all of the games from the old directory to the new one.

Are there issues with this change?

I'm saying that the directory you install into will always be the root directory. But you can specify that directory when you install.

Ok, I was afraid that there might be too much dependence on game directories. What if I allow you to specify a game directory before you create a game, but once it's created, the directory is locked in?

Basically, I'm moving all of the game management out of the Configure area and into the Command Center so you can manage games entirely while the server is online. This means adding new games, activating/deactivating games, banging games, etc. I'm concerned that it's going to be messy to change a game's directory here. I could probably do it, I was just hoping it wouldn't be necessary. Theoretically, if a game is always in the same directory and you are told what that directory is, there's no reason you'd need to move it, is there? The main problem is that having given people that ability, there are some who would miss it if I took it away, right?

Yeah, my goal is to not break anything for anyone. So it will definitely recognize your custom directories. If it's a problem to move those into standardized directories, I won't do that.

I realized that it's probably still best to do this, because it will allow gameops to swap games in and out of a limited number of game slots. I worked on allowing unlimited game slots but with a limited number of active games, and there were just too many complications. Things like when you're on remote connection and you want to activate a game, what happens if you have like 100 games in your list? I have to deal with multiple pages or menus and sub-menus, it's just messy. Having a limited number of slots (25 slots) should work fine, as long as the op can point those slots to other directories where games reside. So you could have 100 games ready to go, but only 25 pointed to by TWGS, and then only a limited number you can activate based on the number of active slots you registered (25 for existing owners, but new owners may have fewer). For the vast majority of ops, 25 slots is plenty.

I'm guessing you'll want to be able to set the directory for a game slot in the remote command menu so that can be scripted? That should be easy enough to do.

To simplify game management in TWGS, I would like to remove the ability to specify a custom game directory for a game. Instead, the game will always go into the directory at [TWGS]\GAME\GAMEA, [TWGS]\GAME\GAMEB, etc, depending on the menu letter of the game. Does anyone rely on the ability to set a custom directory for games?

Also, the game will no longer support changing the root directory. Of course it will be possible to do this from the registry, but that will not be supported behavior. If the root directory is changed, the next time the game is run it will move all of the games from the old directory to the new one.

Are there issues with this change?