Bug #299

ET 2.60 can't connect to ET: Legacy (build from git)

Added by Harlekin about 6 years ago. Updated over 5 years ago.

Status:Fixed% Done:

100%

Priority:UrgentSpent time:-
Assignee:Radegast
Category:Client
Target version:2.71rc2
OS: Arch:

Description

ET 2.60 can’t connect to ET: Legacy (build from git).
ERROR:
Couldn’t load an official pak file... see attachment

The pk3 files i am using:
-etmain
–pak0.pk3
–pak1.pk3
–pak2.pk3
–mp_bin.pk3
-legacy
–pak3_v2.70rc1.pk3
–etl_bin_v2.70rc1.pk3

server: et3.hirntot.org:27999

shot0000.jpg (138 KB) Harlekin, 30.04.2013 12:47

175

Associated revisions

Revision 13b43587
Added by Jacker about 6 years ago

server: changed the error to a print until the valinna client connection is fixed, refs #299

Revision e1e7a8f8
Added by Jacker over 5 years ago

client: fix for the mp_bin issue, thanks to spyhawk, fixes #299

Revision 36177ad3
Added by IR4T4 over 5 years ago

qcommon: let 2.60b clients connect again fixes #299

History

#1 Updated by Dragonji about 6 years ago

You mean legacy mod or ET:L server binary?

#2 Updated by Radegast about 6 years ago

  • Assignee set to Radegast
  • Priority changed from Normal to Urgent
  • Target version set to 2.71rc2

I changed that warning to an error after I thought I removed the dependency on mp_bin.pk3. I will fix it when I get back to ET:L development next month.

#3 Updated by Jacker about 6 years ago

Changed the error back to a message until Radegast has the time to get back to the game

#4 Updated by Spyhawk about 6 years ago

There is a bug in the way ET count the packages in the local side, so the count comparison between ET:L server and ET:L client fails. If one package is added (mp_bin.pk3, or any dummy package) the client count is correct, but this seems purely incidental.

I have corrected this client count in my local branch , and can successfully run ET:L without needing the mp_bin.pk3 at all. However, keeping compatibility with 2.60b is a bit annoying as the client count is still buggy on the client side.

One way to bypass this could be to still require the original mp_bin.pk3 in the /etmain directory, or add a dummy pk3 shipped with the ET:L installer.

#5 Updated by Spyhawk about 6 years ago

or add a dummy pk3 shipped with the ET:L installer.

On second thoughts, that would probably not work either, as the dummy pk3 will add to the count of client side pk3. Maybe the way to go is to lie to 260b clients and always return the same value?

#6 Updated by Dragonji about 6 years ago

I am a little bit lost here. Let’s take an example from 2.55+ binary (I do realize you hate when someone starts talking about this but that’s the best example). You install 2.55 server, than copy 2.55+ binary (which is hex modified 2.6b) and all client versions can join with no probs, the server only contains pak0.pk3 but there’s no problem if 2.60b client with all the packages (pak0, pak1, pak2, mp_bin) join. How can there be a problem if etlded server doesn’t have mp_bin and 2.60b client with this package wants to join?

#7 Updated by Spyhawk about 6 years ago

Dragonji wrote:

I am a little bit lost here. Let’s take an example from 2.55+ binary (I do realize you hate when someone starts talking about this but that’s the best example). You install 2.55 server, than copy 2.55+ binary (which is hex modified 2.6b) and all client versions can join with no probs, the server only contains pak0.pk3 but there’s no problem if 2.60b client with all the packages (pak0, pak1, pak2, mp_bin) join. How can there be a problem if etlded server doesn’t have mp_bin and 2.60b client with this package wants to join?

As far as I see it, pakX.pk3 files are counted separately. A 2.60b client without mp_bin.pk3 and trying to connect to a 2.55+ server might be rejected as well(?).

#8 Updated by Dragonji about 6 years ago

Spyhawk wrote:

A 2.60b client without mp_bin.pk3 and trying to connect to a 2.55+ server might be rejected as well(?).

The thing is it isn’t.

#9 Updated by Spyhawk about 6 years ago

Dragonji wrote:

The thing is it isn’t.

No idea then. Maybe this bug happens only in ET:L because of the new path structure.

#10 Updated by Jacker over 5 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

#11 Updated by IR4T4 over 5 years ago

  • Status changed from Fixed to In Progress

Doesn’t work for me. ET:L client is fine, genuine not.

#12 Updated by IR4T4 over 5 years ago

  • Status changed from In Progress to Fixed

Also available in: Atom PDF