AlliedModders

AlliedModders (https://forums.alliedmods.net/index.php)
-   xREDIRECT (https://forums.alliedmods.net/forumdisplay.php?f=128)
-   -   Protocol mismatch/different mod error (https://forums.alliedmods.net/showthread.php?t=83867)

BRIGADIER 01-16-2009 19:04

Protocol mismatch/different mod error
 
First of all, I would like to say that I love this plugin. I recently upgrade to:
xREDIRECT 1.0.4b x0R xredirect.amxx running

and it worked great for over a day, and now when I try to switch servers it gives the error. It works on 2 of the servers, but not the others, one of which is GunGame. This is currently how the serverlist.ini is set up:

[Redirect DO NOT CONNECT!!]
address=8.9.16.128
port=27015
cmdbackup=5
redirect_manual 1
redirect_check_method 0
redirect_follow 1
redirect_retry 1
nodisplay 0

[NEW 32 SLOT 24/7 ASSAULT]
address=8.9.16.44
port=27015
cmdbackup=5
redirect_manual 1
redirect_check_method 0
redirect_follow 1
redirect_retry 1
nodisplay 0

[GunGame Deathmatch]
address=8.12.20.11
port=27015
cmdbackup=5
redirect_manual 1
redirect_check_method 0
redirect_follow 1
redirect_retry 1
nodisplay 0

[24/7 Dust2]
address=8.9.3.69
port=27015
cmdbackup=5
redirect_manual 1
redirect_check_method 0
redirect_follow 1
redirect_retry 1
nodisplay 0

[Aim_ak-colt/fy]
address=8.9.16.46
port=27015
cmdbackup=5
redirect_manual 1
redirect_check_method 0
redirect_follow 1
redirect_retry 1
nodisplay 0

I could always go back to the last stable version, but I figure this is worth a shot. Any other info needed please let me know, thanks!

edit: error logs:
L 01/16/2009 - 18:46:32: [AMXX] Run time error 4 (plugin "xredirect.amxx") - debug not enabled!
L 01/16/2009 - 18:46:32: [AMXX] To enable debug mode, add "debug" after the plugin name in plugins.ini (without quotes).
L 01/16/2009 - 19:02:24: [AMXX] Run time error 4 (plugin "xredirect.amxx") - debug not enabled!
L 01/16/2009 - 19:02:24: [AMXX] To enable debug mode, add "debug" after the plugin name in plugins.ini (without quotes).

Will try and see what the logs say and post back again.
Edit 2:
L 01/16/2009 - 19:33:51: [xredirect.amxx] Loaded server Redirect DO NOT CONNECT!! (8.9.16.128:27015)
L 01/16/2009 - 19:33:51: [xredirect.amxx] Loaded server NEW 32 SLOT 24/7 ASSAULT (8.9.16.44:27015)
L 01/16/2009 - 19:33:51: [xredirect.amxx] Loaded server GunGame Deathmatch (8.12.20.11:27015)
L 01/16/2009 - 19:33:51: [xredirect.amxx] Loaded server 24/7 Dust2 (8.9.3.69:27015)
L 01/16/2009 - 19:33:51: [xredirect.amxx] Loaded server Aim_ak-colt/fy (8.9.16.46:27015)
L 01/16/2009 - 19:33:52: [xredirect.amxx] Not auto-redirecting <Sixx> (13), automode: 2, current players/bots/max: 1/0/32
L 01/16/2009 - 19:33:52: [xredirect.amxx] Not auto-redirecting <Goose> (2), automode: 2, current players/bots/max: 2/0/32
L 01/16/2009 - 19:33:52: [admin.amxx] Login: "[LNG] preesh<808><STEAM_0:1:xxxxxxx><>" became an admin (account "STEAM_0:1:xxxxxxx") (access "bcfs") (address "xxxxxxxxxxxxxxx")
L 01/16/2009 - 19:33:52: [xredirect.amxx] Not auto-redirecting <[LNG] preesh> (15), automode: 2, current players/bots/max: 3/0/32
L 01/16/2009 - 19:33:52: [admin.amxx] Login: "Pant<749><STEAM_0:1:xxxxxxx><>" became an admin (account "STEAM_0:1:xxxxxxx") (access "abcdefghijklmnopqrstu") (address "xxxxxxxxxx")
L 01/16/2009 - 19:33:52: [xredirect.amxx] Not auto-redirecting <Pant> (3), automode: 2, current players/bots/max: 4/0/32
L 01/16/2009 - 19:33:52: [xredirect.amxx] Not auto-redirecting <al kida> (14), automode: 2, current players/bots/max: 5/0/32
L 01/16/2009 - 19:33:52: [xredirect.amxx] Not auto-redirecting <Are You ShpOngleD?> (16), automode: 2, current players/bots/max: 6/0/32
L 01/16/2009 - 19:33:52: [xredirect.amxx] Not auto-redirecting <lobo> (11), automode: 2, current players/bots/max: 7/0/32
L 01/16/2009 - 19:33:52: [xredirect.amxx] Not auto-redirecting <Captain Planet> (7), automode: 2, current players/bots/max: 8/0/32
L 01/16/2009 - 19:33:52: [xredirect.amxx] Not auto-redirecting <BOOOOOOOOOOOM> (1), automode: 2, current players/bots/max: 9/0/32
L 01/16/2009 - 19:33:52: [xredirect.amxx] Not auto-redirecting <[LNGr] X3||3nT> (4), automode: 2, current players/bots/max: 10/0/32
L 01/16/2009 - 19:33:52: [xredirect.amxx] Not auto-redirecting <KreMe> (9), automode: 2, current players/bots/max: 11/0/32
L 01/16/2009 - 19:33:57: [xredirect.amxx] Not auto-redirecting <Sixx> (13), automode: 2, current players/bots/max: 3/0/32
L 01/16/2009 - 19:33:59: [xredirect.amxx] Not auto-redirecting <[LNG] preesh> (15), automode: 2, current players/bots/max: 4/0/32
L 01/16/2009 - 19:33:59: [xredirect.amxx] Not auto-redirecting <KreMe> (9), automode: 2, current players/bots/max: 7/1/32
L 01/16/2009 - 19:33:59: [xredirect.amxx] Not auto-redirecting <lobo> (11), automode: 2, current

Mordekay 01-17-2009 05:10

Re: Protocol mismatch/different mod error
 
What error do you talk about? That one you put in after your first edit?
Code:

L 01/16/2009 - 19:02:24: [AMXX] Run time error 4 (plugin "xredirect.amxx") - debug not enabled!
L 01/16/2009 - 19:02:24: [AMXX] To enable debug mode, add "debug" after the plugin name in plugins.ini (without quotes).

Add "debug" in plugins.ini and post the debugged info here. But most likely it is because of the welcome message. An error that can be ignored.
All other looks fine.
BTW: your first server, if you want no one be able to redirect himslef to it set
Code:

redirect_manual 1
to
Code:

redirect_manual 0
in all serverlist.ini files.

xOR 01-17-2009 13:33

Re: Protocol mismatch/different mod error
 
i don't understand the initial posting. is it a mix of your serverlist.ini files and the CVARs set on the servers? if this is really your serverlist.ini contents then they are horribly wrong. things like redirect_manual 1 are CVARs and don't belong into this file, they belong into amxx.ini of that server as usual.
so basically everything that starts with redirect_ does NOT go into your serverlist.ini. also, unlike CVARs, the settings in serverlist.ini ALWAYS need to have an equal sign on them. so also the last setting that every server has, "nodisplay 0", is wrong. it should be "nodisplay=0".

as most of these settings are useless there you can simply cut everything from below the line with cmdbackup=5 from every server and the serverlist.ini file should be clean. if you don't want people to redirect to the first server just set nomanual=1 below that server in every server list files of all servers.

i am currently ill, most time in bed and when sporadically at the computer only with low concentration i guess. anyway i'd say you should first get your server list file sorted before we do any more searching for errors, it could still be an issue with the beta, that's what it's a beta for in the end :wink:

here is my suggestion for the serverlist.ini files for all of your servers:
Code:

[Redirect DO NOT CONNECT!!]
address=8.9.16.128
port=27015
cmdbackup=5
nomanual=1

[NEW 32 SLOT 24/7 ASSAULT]
address=8.9.16.44
port=27015
cmdbackup=5

[GunGame Deathmatch]
address=8.12.20.11
port=27015
cmdbackup=5

[24/7 Dust2]
address=8.9.3.69
port=27015
cmdbackup=5

[Aim_ak-colt/fy]
address=8.9.16.46
port=27015
cmdbackup=5

be careful when copy pasting it from here. some browsers put a space character at the end of each line and xREDIRECT wouldn't be able to read it correctly then. you can check it by simply pressing the "end" key on your keyboard on any line in that file after you copied it. delete the space characters if you find any.

BRIGADIER 01-17-2009 16:05

Re: Protocol mismatch/different mod error
 
Thanks guys for the help. I've had someone helping me, and we've tried a few different things thus the messed up serverlist.ini. I replaced it with the one supplied, and still get the same error. After adding debug yesterday, there are no error logs and the only entries in the regular log are about the servers loading, and redirect automode being 2:
L 01/17/2009 - 15:50:24: [xredirect.amxx] Loaded server Redirect DO NOT CONNECT!! (8.9.16.128:27015)
L 01/17/2009 - 15:50:24: [xredirect.amxx] Loaded server NEW 32 SLOT 24/7 ASSAULT (8.9.16.44:27015)
L 01/17/2009 - 15:50:24: [xredirect.amxx] Loaded server GunGame Deathmatch (8.12.20.11:27015)
L 01/17/2009 - 15:50:24: [xredirect.amxx] Loaded server 24/7 Dust2 (8.9.3.69:27015)
L 01/17/2009 - 15:50:24: [xredirect.amxx] Loaded server Aim_ak-colt/fy (8.9.16.46:27015)

L 01/17/2009 - 15:53:33: [xredirect.amxx] Not auto-redirecting <CmX> (1), automode: 2, current players/bots/max: 17/15/32
The following cvars are in my amxx.cfg:
redirect_active 1
redirect_auto 2
redirect_manual 3
redirect_follow 1
redirect_announce 100
redirect_announce_mode 3
redirect_retry 1
redirect_check_method 2

oh, xOR, I'm in no hurry. Health is first priority, I hope you get well soon!

xOR 01-18-2009 10:50

Re: Protocol mismatch/different mod error
 
1 Attachment(s)
it's the first day i am feeling better again so we could stark looking into the issue. i just checked and found i have included a debug message that tells me why the mod check "thinks" the server mods mismatch in my internal test version 1.0.5a. so i appended it here. please use this with debug mode enabled and let it run for some time, go onto the server and open the menu, close and open it again. then some time later check the normal log (not the error log) for a message starting with "mod comparison:" and copy it here.

BRIGADIER 01-18-2009 19:55

Re: Protocol mismatch/different mod error
 
Hello xOR, and thanks again. I tried the last one out, and checked the logs and here they are:
L 01/18/2009 - 18:51:54: [xredirect.amxx] mod comparison: local mod: "cstrike" remote mod (server 3): ""
L 01/18/2009 - 18:51:55: [xredirect.amxx] mod comparison: local mod: "cstrike" remote mod (server 2): ""
L 01/18/2009 - 18:51:31: [xredirect.amxx] mod comparison: local mod: "cstrike" remote mod (server 4): ""
L 01/18/2009 - 18:51:42: [xredirect.amxx] mod comparison: local mod: "cstrike" remote mod (server 1): ""

xOR 01-19-2009 15:27

Re: Protocol mismatch/different mod error
 
ok i now i know into which drawer this sort of problem goes. your server information is not correctly read when it comes to the mod. it's a new feature in the beta version so maybe there is an error in it. i will do some tests against your servers and see where i get with that.
btw, is the other information correctly displayed (number of players and current map)?

BRIGADIER 01-19-2009 17:27

Re: Protocol mismatch/different mod error
 
Yes, the other information is displaying correctly. Thanks again for the response, hopefully we can get this all sorted out 8)

xOR 01-20-2009 20:30

Re: Protocol mismatch/different mod error
 
strange, i can get this info from other servers, tried CS 1.5, CS 1.6 and NS servers. works just fine and then i also added your server and get the same result you had: that information is empty. i queried your server with a UDP packet analyzer but can't see any obvious difference.

i must be overlooking something here, i didn't have much time. maybe i'll get around to do some more intense testing tomorrow.

BRIGADIER 01-20-2009 20:34

Re: Protocol mismatch/different mod error
 
That is strange, all of ours are cs 1.6 and all from the same host (gameservers.com). I can always go back to the latest stable release, however if you'd like me to keep the beta and work with you on this error I'd be more than happy to, just let me know. Thanks again!


All times are GMT -4. The time now is 03:32.

Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.