Chips' Fun House ~ View topic

Is there any way to let the everyone have access to the command admin_vote_nobots? or even just a few cfh people... because the bots get annoying at times, and there is no need when there are 12+ people playing to have bots. they just ruin the game.

Personally, I prefer a 2 v 3 OvD setup to a game with 12 bots shooting me with super shottys in the yard. Especially when they teleport like they do.

If this is possible (I imagine, if it is on a lower admin setting than others, giving other people this limited access) I would like it. Even though I can turn them off whenever I need.

Allowing access at that level would mean allowing access to voting for maps...we'd run into the same problems we ran into before with that. I did take another look and it seems there are voting plug-ins for every imaginable facet of TFC...except bots. Any admin can start a vote...but then again, any admin can simply turn them off. Perhaps I'll just lower the bot number again. I'll come up with something.

An admin being around seems to be the answer. Perhaps there will be a new admin...who knows. Razz

Forum Soldier Joined: 10 Mar 2005 Posts: 352

couldn't you just assign usernames to an individual command, and in this list include lots of people?

Unfortunately, giving someone access at a level that would allow them to start a vote on the bots would also give them...

The ability to cancel ANY vote...including a map votes.
Set a "frag limit" on the server".
Change the map time limit.
Change maps.
Deny votes for a map already voted for.
Restarting a round (or map)

That's the way adminmod works with that access level, I can't control that. And that's a lot of access to give out to simply allow for bot voting.

I do have two ideas that I think will work...I need to test them first.

please do it

Forum Soldier Joined: 10 Mar 2005 Posts: 352

couldn't you set the fox bot voting at a lower level but assign a password to it, and tell only certain people said password?

Again, the voting access required is set by adminmod...I can't change access levesl within it...they are what they are. Assigning password to adminmod functionality is not possible.

Are you sure chips? On the .id servers they give .id members just access to the rockthevote and admin_vote commands(tis all i can do as a member, you too i'd guess), couldn't something of the sort be done here?

Yes...on the .id servers, only members can start a map vote and a couple of others. That is simple and only allows those certain commands.

The way the bot plug-in was written for adminmod requires a higher access level than that and would allow the other admin commands I stated above to be used also by someone given this higher level of access.

I'm thinking at this point that I may be able to rewrite the "hook vote" plugin to work with the bots...I'm not sure since I've only glances over the script quickly. But it should be possible. Another option I'm looking at is a plug-in to that can basically be set to change any server variable. However, bots are not set as server variables and this may not work at all.

These are the two options I discussed above that I'll look into.

but chips, of the admin_vote commands, there is the command admin_vote_nobots
shouldn't this be possible? it just disables the bot program/script...

Yes...it is entirely possible to give someone access to admin_vote_nobots.

But, as stated above...all these other options below would be open to a user this priviledge would be given too also. That's quite a bit of access.

The ability to cancel ANY vote...including a map votes.
Set a "frag limit" on the server".
Change the map time limit.
Change maps.
Deny votes for a map already voted for.
Restarting a round (or map) "

maybe you can talk to the .id people? cuz i sure as heck cannot do that. the commands i have are:
admin_vote_nobots
admin_vote_map
admin_vote_kick
rockthevote
which for anyone you'd bother given the power to kick bots too, should be able to do those commands ok too.

Hmmm...I obviously haven't been clear. Let's start over.

Adminmod access is driven by number codes from 0 thru 135536.
"0"...is no access whatsoever. That what access the average player has here and at the .id servers.
"1"...is "default" access that allows map voting, and kick voting. (this is what we have at the .id servers)
"2"...is the level needed to start a vote for no bots...but whoever I gave that to would be able to change too many other things as described above...timelimits, maps etc.

If I gave out level 1 access like we have on the .id servers, you still couldn't start a vote for the bots.

You could simply alter the vote bots script to permission level 0, then recompile it.