[xOR]

Originally Posted by pl2003 Wow, I can't believe I had overseen this plugin for two weeks ! Good idea, excellent realization and a perfect description/changelog - great!

thanks

Originally Posted by pl2003 I want to use this on my servers, actually running a simple adminslot plugin. This brings me to my first questions regarding: This only affects players already on the server, trying to connect to another? So I can keep my adminslot/redirection plugin, handling the players connecting on a 'full' server (slotmax+adminslot)?

my plugin considers a server "full" when there are (maxplayers-1) players. so e.g. if there are 12/13 players and someone connects he will be redirected. as i don't know how your adminslot plugin works i can't predict how the plugins would work together but in general i guess it won't work very good.
i thought of adding reserved slots myself already but think of the following situation:
there are 12/13 players and you connect. you don't get redirected, because you are admin, so now we have 13/13. players that connect now will see the default message "server is full". they don't come far enough into the connection process to get handled by the plugin. aside from the fact that most people won't even try to connect to a full server anyway, when they see in server browser/steam browser (or their connect tool like HLSW or ASE) that the server is full. so, in fact, the redirection is broken in this case just because an admin connected to his reserved slot (which i believe will happen often).

so to your question again ("This only affects players already on the server, trying to connect to another?"): no it doesn't. it does affect people connecting. you can set redirect_auto 0 to prevent the plugin from handling connection people. in this case only manual redirects work (either when redirect_user is used by an admin or people used /server or /follow command). and these manual redirects, again, are prevented if the target server is "full" (maxplayers-1).

wow, i hope i did not confuse you more than even before now

Originally Posted by pl2003 Furthermore, the options of redirect_auto do not fit my needs: I want everyone, who tries to connect to a full server be redirected to a 'hardcoded' server, not a random, not the next in the list - could I realize this?

just add "noauto=1" to every server in the list except the one you want to have people redirected to. i'd suggest to set redirect_auto 2 for this though, so it can't happen that the plugin is wasting time calculating random server numbers where in the end only one can be used anyway

Originally Posted by pl2003 Another question regarding this: Hopefully I got it right and did not overread something. Is it possible to let the plugin assume a server is full, if it's connectedplayers-1/maxplayers (e.g. 20/21)? I have a reserved admin slot on every server, hence they are never full (21/21). But maybe I just don't understand the sentence "one free slot left, that is", do you mean it IS considering a server with one slot left as a full server?

yes, see above

Originally Posted by pl2003 As you can see in my sig, I run a couple of servers on two boxes (=two IPs). This makes me a victim of point 1 of your known issues section . Nevertheless I will give it a try, because the information about map/players is one of the most important features for me. Please keep trying to fix this.

yeah please try and tell whether it works for you. for now my experience is that on some servers it works and on some doesn't (e.g. my server works fine with several game servers on it checking each other with mode 2). i am afraid i can't fix this, it's no error in the plugin but either in AMXX sockets module or in sockets drivers of the machine running the server. it could be the firewall there as well.
regardless of whether mode 2 is crashing for you or not, it would greatly appreciate when you could tell me your system specs (if it's a root machine and you have access to such information). maybe someday we can at least find out what versions of what modules/drivers/firewalls calls the problem to have some workaround.

Originally Posted by pl2003 I got an error with 0.7.5b:

my bad, download 0.7.5b2, it's fixed there

[Waylay]

+karma

[Guenhwyvar]

My redirect/adminslots plugin keeps a free slot without exception. If an admin connects on the max slot (e.g. on the 15th/15), the player on slot number 14 is redirected to a server defined by cvar.
If you want to look about it, it's called "AdminReservation 1.1 by [RST] FireStorm" (posted here, 3rd post).
This solution is absolutely neccessary in my eyes as it avoids the problem you described ("server full" for steam/hlsw) and does not loose the connecting players by kicking.

Maybe you can add this feature. If not or till you do, I hope setting redirect_auto to 0 will let both plugins (redirect by firestorm and your redirect) let do their work. Or am I overlooking something?

and these manual redirects, again, are prevented if the target server is "full" (maxplayers-1)

That's nice, I got that now . Confusion reduced ;). It's the way I hoped it would work.

I start to test it and will setup it on the gameserver step by step. The system specs of the two roots I will send by pm.

Thanks for the nice answer and again for making this nice plugin .

[Guenhwyvar]

Hm, please have a look on the attached screenshot. Server 1 is grayed out, ok, it's the server Iam on. But the servers 4, 5 and 7 are full as well, but I was able to choose them and got redirected.
Did I something wrong?

[xOR]

are you sure with the thread? after some searching i found this thread which i believe contains what you were talking about in the third post ;)

but see, this is a completely different plugin with a different philosphy. this is an adminslots plugin with a simple redirection function, while my plugin is an extended and full-featured redirection plugin ONLY (so no adminslots).
so basically what you request is either one of the following:

1. i add support for adminslots to my plugin
2. the original author, you, or me, or anyone else adds support to this adminslots plugin, so for redirecting it uses the newly added native from my plugin

solution 1 would actually render your adminslots plugin useless, as the base functionality would be in my plugin. the disadvantage is, that i wouldn't rebuild the complete adminslots functionality of this plugin (this would just go too far, it would be like starting to develope a second plugin within the plugin), so you might end up with missing some features you had before.

solution 2 would be good for me at first, because it is a good test case to check whether my new native works. in the end i am not sure whether this would satisfy all your needs and for now i can't imagine how the complete end result will look like.

so my suggestion is let me play around with solution 2 a bit on my server and see what this gives us

Originally Posted by pl2003 Hm, please have a look on the attached screenshot. Server 1 is grayed out, ok, it's the server Iam on. But the servers 4, 5 and 7 are full as well, but I was able to choose them and got redirected. Did I something wrong?

no, you did not do anything wrong. i just remembered that wrong. the plugin is only preventing redirection when the server is really full (maxplayers). i also remembered that the initial idea behind this was that the target server might not have any redirection or reservation features and in this case it would be right to redirect there even if 12/13.

so to fix this i could think if a version where you can set a new variable in the serverlist.ini for a server: adminslots=x. the default for x will be 0, which is the same behaviour as before. but if you set it to 1 redirection will be prevented if it is 12/13 already. you can even set it to 3, then redirection won't be possible with 10/13 players on the target server already.
redirection WILL be possible if you're an admin until 13/13 of course. regardless of the adminslots setting.

would this help you?

[Guenhwyvar]

Originally Posted by xOR are you sure with the thread? after some searching i found this thread which i believe contains what you were talking about in the third post ;)

Oups, sorry, you're right. I mixed the Tabs up .

You are right with solution 2 and, more important, you should not have to develop a plugin in a plugin, that would be really overdone. I confirm, bringing the adminslots to work with yours would be the more useful way.

Let me recapitulate: On a "full" server (14/15), everyone gets redirected (redirect_auto 1/2), players and admins.

I hope your experients (preferably with the plugin by firestorm) are successful . A reserved slot for the admins/selected players is neccessary for me.

Originally Posted by xOR so to fix this i could think if a version where you can set a new variable in the serverlist.ini for a server: adminslots=x. the default for x will be 0, which is the same behaviour as before. but if you set it to 1 redirection will be prevented if it is 12/13 already. you can even set it to 3, then redirection won't be possible with 10/13 players on the target server already. redirection WILL be possible if you're an admin until 13/13 of course. regardless of the adminslots setting. would this help you?

This would be nice. It could confuse players, using a serverside server-change feature which let the player connect to another server and immediately back to origin ;). On the other hand it's no big problem for my server farm. A (manually) redirecting player would get redirected only once (if I set "noauto=1" to every server except one).

More important (for me) would be the cooperation between an adminslot and your plugin, to benefet from all features of your plugin (announcing redirected connecting people).

[xOR]

to have kind of a compromise i added some small adminslots functionality now. the adminslots feature is turned off by default, to enable it set redirect_adminslots 1.
there is no need to define a number of adminslots, because the plugin just redirects the player that is on the server for the shortest time period when someone with a reserved slot connects. the plugin reads the flag "b" (ADMIN_RESERVATION) for this. of course it is smart enough not to redirect someone that as well has this flag
this redirection can happen again and again and again for everyone with the "b" flag connecting, so you actually have infinite admin slots (= depends on how many people have "b" flag on the server)

furthermore there is as suggested by me in my last post the new server list option "adminslots". other than stated before this option only recognizes the parameters 0 and 1 for enabled and disabled. 0 is default and the same behaviour like it was before: people are connected to a target server even when there are 12/13 players and are not redirected with 13/13 on it.
as soon as you set adminslots=1 for a server this changes:
people are not allowed to get redirected to the server when it has one player less playing than maximum allowed players, except admins (means people with flag "b" again).

note that the setting redirect_adminslots and the server option adminslots in server list file are completely independant from each other.

the reason why the adminslots option can't take the number of slots is that it would not help to know when there are 2 admin slots instead of one. the plugin can never know whether both admin slots are already in use or one is free. so in fact, it can't know for sure if a redirection is possible and has to try blindly anway.

@pl2003: maybe redirect_adminslots satisfies your needs already and there is no need for the other plugin anymore?
but independant from that i will still use this plugin suggested by you to try my native. just that i haven't done it yet and will do it some time later.

[Guenhwyvar]

Wow, you are fast . Thanks for the modifications. But I have to question this:

there is no need to define a number of adminslots, because the plugin just redirects the player that is on the server for the shortest time period when someone with a reserved slot connects.

Does it mean, the player with the shortest time gets redirected on admin join, indepentent of the number of players on the server? (Meaning if an admin connects on 1/15 server, the only playing person gets redirected)
Or is this behavior limited to the last free slot, which would make more sense? As you described it concretely, I have to question it.

@pl2003: maybe redirect_adminslots satisfies your needs already and there is no need for the other plugin anymore? but independant from that i will still use this plugin suggested by you to try my native. just that i haven't done it yet and will do it some time later.

It does fit my needs! Now I start testing it on my servers.

[xOR]

Originally Posted by pl2003 Does it mean, the player with the shortest time gets redirected on admin join, indepentent of the number of players on the server? (Meaning if an admin connects on 1/15 server, the only playing person gets redirected) Or is this behavior limited to the last free slot, which would make more sense? As you described it concretely, I have to question it.

of course people are only redirected when an admin connects AND there are (maxplayers - 1) players on the server.
so the old example: there are 12/13 players, you as admin connect, and "UnnamedPlayer" who connected one minute ago is sent to another server so that it stays 12/13 and does never get 13/13.
so with 11/13 or less players noone is redirected ;)

[Guenhwyvar]

Ok .

I setup your plugin on 6 of 7 servers now. Players without the "b" flag can still connect (manually) to a full server (e.g. 20/21). Maybe I made something wrong with the settings, here we go:

Originally Posted by serverlist.ini [italy RUSH ONLY] address=85.214.36.125 port=27015 adminslots=1 [sHclachthaus funmaps] address=87.106.1.37 port=27035 noauto=1 adminslots=1 [TittyTwister DeathMatch] address=85.214.36.125 port=27025 noauto=1 adminslots=1 [chilled kreedzing] address=87.106.1.37 port=27135 noauto=1 adminslots=1 [DeathMatch I] address=85.214.36.125 port=27055 noauto=1 adminslots=1 [DeathMatch II] address=87.106.1.37 port=27015 noauto=1 adminslots=1 [DeathMatch III] address=87.106.1.37 port=27025 noauto=1 adminslots=1

Originally Posted by part_of_amxx.cfg redirect_active 1 redirect_auto 2 redirect_manual 1 redirect_follow 1 redirect_external_address 0 redirect_check_method 2 redirect_announce 300 redirect_announce_mode 3 redirect_show 1 redirect_adminslots 1