Diordany van Hemert

Just an additional comment on the render time warning: I tried your patch again (the one where the render time warning isn't commented out) and realized that I missed the...

> It is commented out, so no worries in there, no? (I had just wanted to test whether any badness was associated with the fix, now no need I guess.)...

> The issue is problematic. One can hypothetically have both an `ad` and an `AD` directory in there on purpose. I agree, I'll await further response.

> For 'correction' purposes though, like the case you described, we can add a `gamereset` command to go back to id1 ??? Yeah, I'd been thinking about a similar solution...

> For 'correction' purposes though, like the case you described, we can add a `gamereset` command to go back to id1 ??? Oh I think I misunderstood your solution. I...

> Oh I think I misunderstood your solution. I guess this could work for your example as well. If the user runs the `gamereset` command before attempting to load `ad`.

> Well, yes, that actually is a problem. (It seems I wasn't carefully reading the issue.) > > Waiting for additional comments Yeah, I also think that it would be...

> side note: does `game ""` break stuff? presumably that should also do the same thing (considering that id1 cannot be unloaded). `game .`/`game ..`? lots of invalid options that...

> for the paks part, loading *.pak (insensitively) avoids the need to check a whole series of potential camelcase names. for stuff within gamedirs/paks/pk3s fte's fs_cache stuff making gamedir access...

> Stuff like this is why FTE's console command names are still case sensitive. tab completion will correct it - both for the name name and for arguments of commands...