Orums Quest - Server Disconnect

Ask for help regarding any technical issue or report any bug or OS independent issues.
Post Reply
Ophiel
Peon
Peon
Posts: 12
Joined: 29 Jul 2008, 22:30
Location: Internets
Contact:

Orums Quest - Server Disconnect

Post by Ophiel »

In Orum's quest I am getting "disconnect" when trying to pass trough first torches if I set up colors right.

1. I try to pass trough torches, I'm given a color
2. I go to the torch 1 and set up this color
3. I go back and try to pass trough torches

now two things can happen, randomly:
- I am not allowed trough, even though color is set up correctly
- I am disconnected from the server

ArchLinux [Current :P]
Manaplus 1.5.5.9 (manaplus-git package from AUR)
Character name: Ophiel

If you need any logs please kindly let me know, although I heard this is problem for many people so I think you can easily reproduce it and collect full debug on your dev versions.
User avatar
gumi
TMW Adviser
TMW Adviser
Posts: 797
Joined: 19 May 2014, 18:18

Re: Orums Quest - Server Disconnect

Post by gumi »

- I am disconnected from the server

This bug has been reported countless time. I'm not able to reproduce it but if I was I could simply check the packets sent to manaplus and see what's wrong..



- I am not allowed trough, even though color is set up correctly

This is because when you get disconnected it resets the temporary variables so all torches change color
Ophiel
Peon
Peon
Posts: 12
Joined: 29 Jul 2008, 22:30
Location: Internets
Contact:

Re: Orums Quest - Server Disconnect

Post by Ophiel »

Hello, thanks for the answer. I tried to catch pcap file for you, maybe it will help?

I used

Code: Select all

sudo tcpdump -w mana.pcap -i enp0s25 dst 198.72.6.20 or src 198.72.6.20
https://static.keios.eu/manadebug/orums.pcap

in case you prefer wireshark pcapng, i made this with "host 198.72.6.20" filter:

https://static.keios.eu/manadebug/orums.pcapng

but it seems a bit small, not sure if i'm doing it well.

Let me also provide you full log, but I think that won't be really helpful

https://static.keios.eu/manadebug/orums_crash.log
This is because when you get disconnected it resets the temporary variables so all torches change color
as I mentioned, it is random: sometimes it disconnects me and sometimes not - if it does not, torches don't let me trough even though colors are matching. I know they change after disconnect.
User avatar
gumi
TMW Adviser
TMW Adviser
Posts: 797
Joined: 19 May 2014, 18:18

Re: Orums Quest - Server Disconnect

Post by gumi »

please do Setup > Misc > Other > Enable debug log
then reproduce the crash and send me manaplus.log
Ophiel
Peon
Peon
Posts: 12
Joined: 29 Jul 2008, 22:30
Location: Internets
Contact:

Re: Orums Quest - Server Disconnect

Post by Ophiel »

https://static.keios.eu/manadebug/manaplus.log

Code: Select all

6773: [11:58:26.63] 0000 Receive packet: MessageIn
6774: [11:58:26.63] 0000 readInt16:  135 0x87: packet id
6775: [11:58:26.63] 0002 readInt32:  2330996965 0x8af030e5: tick
6776: [11:58:26.63] 0006 readCoordinatePair: 47,36 48,39: move path
6777: [11:58:26.63] 0011 readUInt8:  0 0x0: unused
6778: [11:58:26.80] Window::Window("Network Error")
6779: [11:58:26.80] Loaded /usr/share/manaplus/data/graphics/gui/ok.xml
6780: [11:58:26.80] state: 13
6781: [11:58:26.80] saving extra layer: /home/jin//.config/mana/mana/server.themanaworld.org/maps/009-4.tmx/extralayer.txt
6782: [11:58:26.79] Disconnected.
yea, like that, as soon as I set up good color in the torch and tried to went trough.
User avatar
gumi
TMW Adviser
TMW Adviser
Posts: 797
Joined: 19 May 2014, 18:18

Re: Orums Quest - Server Disconnect

Post by gumi »

Code: Select all

[11:58:26.46] 0000 writeInt16: 133 0x85: CMSG_PLAYER_CHANGE_DEST
[11:58:26.46] 0002 writeCoordinates: 48,39 1: destination
here the you are on (48,37) and you request to walk to (48,39)

Code: Select all

[11:58:26.54] 0000 readInt16:  135 0x87: packet id
[11:58:26.54] 0002 readInt32:  2330996867 0x8af03083: tick
[11:58:26.54] 0006 readCoordinatePair: 48,37 48,38: move path
[11:58:26.54] 0011 readUInt8:  0 0x0: unused
here the server replies by saying you you can move from (48,37) to (48,38) since there is no collision on that tile

Code: Select all

[11:58:26.58] 0000 readInt16:  145 0x91: packet id
[11:58:26.58] 0002 readString: 009-4: map name
[11:58:26.58] 0018 readInt16:  47 0x2f: x
[11:58:26.58] 0020 readInt16:  36 0x24: y
when you walk on tile (48,38) the server knocks you back to the tile (47,36) if the colors are not correct

Code: Select all

[11:58:26.58] Warping to 009-4 (47, 36)
[11:58:26.61] 0000 writeInt16: 125 0x7d: CMSG_MAP_LOADED
here your client sets your new position and tells the server that your position is changed


and this is where it gets interesting:

Code: Select all

[11:58:26.63] 0000 readInt16:  135 0x87: packet id
[11:58:26.63] 0002 readInt32:  2330996965 0x8af030e5: tick
[11:58:26.63] 0006 readCoordinatePair: 47,36 48,39: move path
[11:58:26.63] 0011 readUInt8:  0 0x0: unused
The server tells the client that they can move from (47,36) to (48,39).

First of all, the client did not send another CMSG_PLAYER_CHANGE_DEST so the server should NOT send this. If it absolutely need to send something to tell your position to the client it should send 0x88.

Secondly, this should only be one tile but it tells the client that you can walk 3 tiles.


I'll look into it and make a patch when I have some time
Ophiel
Peon
Peon
Posts: 12
Joined: 29 Jul 2008, 22:30
Location: Internets
Contact:

Re: Orums Quest - Server Disconnect

Post by Ophiel »

Hello,

I was able to complete the quest with Rill's help today. Seems that disconnect happens only when you force-try to go trough blocked torches. As soon as we did it calmly and properly I was able to go trough without problems.

Sorry for taking your time, but there still is an issue here, it's just it's not a quest blocker. I hope though that logs I've provided may be of some help to make tmw better and get rid of such app behaviour.

To all that experience the same - make sure that you have properly configured torches and take the entrance slowly.
Post Reply