[this has no bearing on the protocol itself] One good reason for the name being quite different is when the requested file is part of a pak file (and downloading the pak file is permitted), the entire pak file can be sent instead. QF does not yet do this, but it should be easy enough to implement: if file_from_pak (from FOpenFile) is set, and pak file downloading is permitted, do a rename (-2 for non-http, set newname in http) and send that instead. The client can check for a ".pak" extension in the rename, permit it, and then cause a rescan of the game directory in order to pick up the new pak file.