Adding an extra dot simply tells Windows that this is gonna have a blank extension, and the extra dot is then removed automatically. newdir /with leading dot/ make sure to write also enclosing dot on Windows - it will be removed, but when not typed it will throw an error and your dir won't be renamed - it's a bug that causes Windows think the dot as file extension separator. Make an archive directory (may be inside baseq3 folder and can contain a dot at the beginning of the dir /This is considered hidden on Unix systems/ - when making. It's no good to store all goodies in live installation of engine. In fact the file extension doesn't even matter, you could call it mywad.butts and any compliant port will still know what to do with it. To be more clear, PK3/7 files aren't a unique file format, they are just a renamed. To the pk3 amount: as far as I know Skirmish has limited access for maps listing (map won't show up in Skirmish menu even with valid arena code, but is still loadable via console), but if you have really huge amount of pk3 files in your installation, it's possible that engine just ran out of memory when tried to load all of these pk3 files in RAM. A PK3 file, but using a 7z/LZMA container rather than zip. You NEVER should alter contents of original pak#.pk3 files where # is number from 0 to 8 (8 is point release 1.32) - of course you never should alter any downloaded pk3 file as well as some servers use custom maps in rotations and thus it might be considered unpure client at the server side. When does it say? At startup or when trying to access some server? It's possible that it's only a server's response to your connection and might point to that you do not have original installation.
0 kommentar(er)
