'Couldnt Load Official Pak File'


(wiCkedSiQQ) #1

Hi,

I run a Jaymod 2.55+ server and some of my members seem to be getting the couldnt load official pak file error. I just recently switched from N!tmod because too many of my members couldnt join due to that error. Is it a client side error or a server side error? Is there a fix. My server host dont just normally patch 2.55 they only d 2.55+ and 2.6b so yeah. Please help.

Cheers, David


(Undead_fly) #2

This error is common after downloading new paks, restarting ET a couple of times (Which means more than one!) usually fixes it. You could also upgrade to 2.60b and check the client console to see what paks were missing. With the error above, it will simply say that pak0 is corrupted, if it says something else… something else is wrong. :smiley:


(stealth6) #3

this error normally occurs when people do this:
-install game client
-install 2.60b patch

Then you get the error you described. To fix it you have to reinstall the game, install the 2.60 patch FIRST THEN install the 2.60b patch.

But since you are running 2.55+ I have no idea if that could effect the problem or have other causes.
I’d just say update to version 2.60b since that’s what patches are for…


(gaoesa) #4

If your server installation is 2.60b and then you change the executable to 2.55+, you need to delete files pak1.pk3, pak2.pk3 and the mp_bin.pk3 which is mentioned at http://equalone.hn.vc/index.php?index=6. So that the etmain folder would only have pak0.pk3.

All of these files are in the etmain directory of your server.

The error happens when 2.55 client tries to connect to the server. 2.60 clients of course have no problems connecting.

Just one possible reason and solution to the problem.


(wiCkedSiQQ) #5

Thanks I have deleted pak1.pk3 and pak2.pk3 but there was no mp_bin.pk3 I ran the server and it was still up which is a start :stuck_out_tongue: But im not the one with the problem so ill have to wait for one of my members to check.
Ive also got him to patch up to 2.6b but yeah he still got that problem.

My host must not have 2.55+ patched it correctly. Thanks for your help and if it works ill let you know.


(wiCkedSiQQ) #6

Thanks guys, seems to have worked. :slight_smile: