Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

2.3 and trunk can play together #1339

Closed
wzdev-ci opened this issue Jan 4, 2010 · 7 comments
Closed

2.3 and trunk can play together #1339

wzdev-ci opened this issue Jan 4, 2010 · 7 comments
Labels
closed component: other normal
Milestone
unspecified

Comments

@wzdev-ci
Copy link
Contributor

wzdev-ci commented Jan 4, 2010

resolution_fixed type_bug | by cybersphinx

error   |02:25:41: [recvMessage] You were kicked because, Data doesn't match!
error   |02:26:41: [recvMessage] You were kicked because, It is not nice to cheat!
error   |02:32:02: [recvDroid] Packet from 0 refers to non-existent template 163056, [Human : p0]
error   |02:32:02: [recvDroidInfo] Packet from 0 refers to non-existent droid 163200, [Human : p0]
error   |02:32:04: [recvDroid] Packet from 0 refers to non-existent template 163056, [Human : p0]
error   |02:32:04: [recvDroidInfo] Packet from 0 refers to non-existent droid 163208, [Human : p0]
error   |02:32:09: [recvDroidInfo] Packet from 0 refers to non-existent droid 163200, [Human : p0]
error   |02:32:15: [recvDroidInfo] Packet from 0 refers to non-existent droid 163208, [Human : p0]
error   |02:32:15: [recvGroupOrder] Packet from 0 refers to non-existent droid 163208, [Human : p0]
error   |02:32:15: [recvGroupOrder] Packet from 0 refers to non-existent droid 163200, [Human : p0]
error   |02:32:17: [recvGroupOrder] Packet from 0 refers to non-existent droid 163208, [Human : p0]
error   |02:32:17: [recvGroupOrder] Packet from 0 refers to non-existent droid 163200, [Human : p0]
error   |02:32:20: [recvGroupOrder] Packet from 0 refers to non-existent droid 163208, [Human : p0]
error   |02:32:20: [recvGroupOrder] Packet from 0 refers to non-existent droid 163200, [Human : p0]

It claimed to kick me, but didn't try very hard. [8981]/[8982].

Issue migrated from trac:1339 at 2022-04-15 20:23:53 -0700
@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jan 4, 2010

cybersphinx edited the issue description

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jan 4, 2010

Zarel commented

Well, are 2.3 and trunk netcode-compatible? I currently have them using the same netcode version since I thought they were.

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jan 5, 2010

cybersphinx commented

Netcode, yes, we played (or drove around with two trucks, in my case) for a few minutes (host was trunk, I 2.3, against two AIs). But the data and calculations 2.3 and trunk use are different, the power changes alone will make the sync code happy. I did play (or drive around with my two trucks) for a few minutes, I could help my ally build, but then the above messages started appearing.

The main question is, why didn't the kick work? The game detected the differing data, and whatever the cheat thing does, but the kick didn't work. Differing numbers in trunk and 2.3, so trunk sends a kick, but 2.3 thinks that means something else?

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jan 5, 2010

Zarel commented

Oh, I forgot about the power code changes.

I'm as surprised as you are that the kick didn't work, though. The netcode itself should be compatible...

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jan 5, 2010

Zarel changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jan 5, 2010

Zarel set resolution to fixed

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jan 5, 2010

Zarel commented

(In [9017]) Fix bug #1339 - trunk and 2.3-branch shouldn't be able to play with each other.

@wzdev-ci wzdev-ci closed this as completed Jan 5, 2010
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
closed component: other normal
Projects
None yet
Milestone
unspecified
Development

No branches or pull requests
1 participant
@wzdev-ci