I had a player contact me to inform me the {MHM} server "Refused to send SkyBox" when he tried to connect to the server to play and thus, he could not connect and play.
I connected and it did the same thing to me.
I checked the server and found the SkyBox file was not there which was odd but no biggy. I put it back in the high-speed redirect folder and tested.
When I tested, I then saw it download to me like it was supposed to but then the server refused to send a file called MOUNTAIN.
Again, no biggy. I added it to the high-speed redirect and tested again and it worked fine so I let the player know I had fixed the issue(s).
He let me know he has two installs. One that is basic/regular and the other uses the S3TC High Detail Textures.
He also explained his basic install can connect but the S3TC install still gets the error: Refused to send SkyBox.
I'm going to dig in on this issue but I'm willing to be told the answer if someone knows it. I'm listening!
Interesting technical issue
-
Hermskii
- Site Admin
- Posts: 8677
- Joined: Sun Jul 10, 2005 9:56 pm
Interesting technical issue
~Peace~
Hermskii
Hermskii
-
RICOTTA_19216
- Posts: 11
- Joined: Sun Jun 01, 2025 4:07 pm
Re: Interesting technical issue
Hi
The Package in question has to be conformed, this means, that this package is compatible with the old version... They have to share a same ID.
It is the creator of these S3TC textures to adjust the ID version of their packages, to avoid sending the client a "mismatch" because it is not needed, after all, the difference between the original texture, and the S3TC texture, is none, there's no less or no more content other than the textures themselves having different information - in this case, a texture with the same name, but with increased resolution using S3TC clever compression method to compress hi-quality textures
These package's conforming occur with Epic Games/Digital Extremes original version releases, to maintain compatibility with previous version, say version 436 with 432, or 451 with 436 and likewise 432, they all have to share the same ID to maintain all clients from any versions in one server.
I believe the UCC command tool has that ability, however I have minor experience with the ancient Unreal engine. I know this info because I work with UE3 and the documentation over there explains this stuff a lot more accurately. (Naturally my UnrealScript wizardry easily carries over, tooo )
To sum up, the flaw occurs with the S3TC version of the package, I have a faint recall that the S3TC textures that are installed from the 2nd CD from Unreal Tournament GOTY have this problem... Curse them! (grab any Deemer of your choice and blow the doors & windows out of the guy responsible for not conforming the packages lol)
Installing any other S3TC Texture pack is the solution
Or you can conform the package yourself... That could work! - This one is a client problem/fix remember, the server has got nothing left it can do about connection issues, for instance the client can open the editor, check the box in the Botpack package, and save it... That'd leave me unable to connect!! Unless I conform it... But I could be deeeeply wrong now, for example the whitelist/blacklist system would detect my modified file even after conforming. But no... I'm not experienced enough in this I realize
Ah dear 
Someone correct me I think that system only detects .u files and keeps clients from entering with a modded version.
The Package in question has to be conformed, this means, that this package is compatible with the old version... They have to share a same ID.
It is the creator of these S3TC textures to adjust the ID version of their packages, to avoid sending the client a "mismatch" because it is not needed, after all, the difference between the original texture, and the S3TC texture, is none, there's no less or no more content other than the textures themselves having different information - in this case, a texture with the same name, but with increased resolution using S3TC clever compression method to compress hi-quality textures
These package's conforming occur with Epic Games/Digital Extremes original version releases, to maintain compatibility with previous version, say version 436 with 432, or 451 with 436 and likewise 432, they all have to share the same ID to maintain all clients from any versions in one server.
I believe the UCC command tool has that ability, however I have minor experience with the ancient Unreal engine. I know this info because I work with UE3 and the documentation over there explains this stuff a lot more accurately. (Naturally my UnrealScript wizardry easily carries over, tooo )
To sum up, the flaw occurs with the S3TC version of the package, I have a faint recall that the S3TC textures that are installed from the 2nd CD from Unreal Tournament GOTY have this problem... Curse them! (grab any Deemer of your choice and blow the doors & windows out of the guy responsible for not conforming the packages lol)
Installing any other S3TC Texture pack is the solution
Or you can conform the package yourself... That could work! - This one is a client problem/fix remember, the server has got nothing left it can do about connection issues, for instance the client can open the editor, check the box in the Botpack package, and save it... That'd leave me unable to connect!! Unless I conform it... But I could be deeeeply wrong now, for example the whitelist/blacklist system would detect my modified file even after conforming. But no... I'm not experienced enough in this I realize
Ah dear Someone correct me I think that system only detects .u files and keeps clients from entering with a modded version.