Insane Limits - Examples

[ImportBot]

Originally Posted by Froz3nTundra*:

 

Which part are you referring to? ... The announcement or the !adminlist command?

 

I have not tested it ... but it seems that if you are admin, and joining, you won't see the announcement because you'd be in the loading screen when the announcement is sent, which is ok.

Hmm, well I made sure I wasn't in any whitelist when I tried it, is this dependent upon procon user account?

[ImportBot]

Originally Posted by micovery*:

 

Hmm, well I made sure I wasn't in any whitelist when I tried it, is this dependent upon procon user account?

No this example is independent of the ProCon accounts. What I meant by "admin" .. is that your name is in the "admins" list. The example asks you to create an "admins" list.

[ImportBot]

Originally Posted by Froz3nTundra*:

 

No this example is independent of the ProCon accounts. What I meant by "admin" .. is that your name is in the "admins" list. The example asks you to create an "admins" list.

Ok yes of course, I do have my name in that list and will have a buddy help me to check it, thank you.

[ImportBot]

Originally Posted by PapaCharlie9*:

 

I can help with one of your problems:

i use this Limit Copy and paste but after doing it got this error...

 

[21:18:13 11] [insane Limits] Compiling Limit #18 - Kick Players Without Battlelog - OnSpawn

[21:18:13 12] [insane Limits] ERROR: 1 error compiling Expression

When you see that error message, check to make sure you have followed the instructions in the example post when setting a check to Code. The error means you have something set to Expression that ought to be Code.

 

Ok yes of course, I do have my name in that list and will have a buddy help me to check it, thank you.

You can also set the delay in the Action longer, to give yourself a better chance of seeing it. Try setting it to 180 instead of 60, that's 3 minutes. Of course, if you deploy faster than 180 seconds, you have to be patient and wait for it to show up in chat.

 

To verify that it is working, you don't need a buddy, just look in your Console log in PRoCon. If you see the admin.say after the OnJoin event, it's working.

[ImportBot]

Originally Posted by PapaCharlie9*:

 

I am trying to set my server name based on what Limits are enabled. Is there a way to check the state of a given limit?

 

So I could do something like OnInterval check if limit#1 is enabled.

I would do this in the Limit itself but i don't want to change the server name OnKill.

There are a couple of ways of doing this.

 

If you know the limit id number and you know that number is not going to change (you will not re-order your limits at some point in the future), you can look up the plugin variable by name. Suppose the limit is id #3. The name of the variable it "limit_3_state". The name you see in the Plugin settings panel is the name of the variable. You can use code like this:

 

Code:

String state = String.Empty; // unknown state
try {
    state = plugin.getPluginVarValue("limit_3_state");
} catch (Exception e) {}

You'll have to deal with the logic of having several limits enabled and figuring out which one takes priority.

 

The other way of doing it would be more robust, since it won't rely on the limit id number. You can build it into each limit. Just have each limit set vars.serverName itself. Textbook encapsulation.

 

You are right to worry about updating it too often, like every OnKill, but you can control that in a number of ways, by writing code in second_check to test the count of activations or by writing code to set a variable in plugin.Data to indicate that the server name has already been set. That's what I'd do. Each plugin would check to see if the plugin.Data variable is set or if it is set, it has a different value (String) than this limit would set. Either way, it changes vars.serverName and updates the plugin.Data variable. If it is set and it does match, do nothing (already set).

 

BTW, Battlelog is notoriously slow at updating the server browser data, so even if you change your vars.serverName, there's no telling when people will actually see the change in Battlelog.

[ImportBot]

Originally Posted by Mootart*:

 

I can help with one of your problems:

 

When you see that error message, check to make sure you have followed the instructions in the example post when setting a check to Code. The error means you have something set to Expression that ought to be Code.

 

 

When i set it to Code i got this error....

 

[05:03:05 30] [insane Limits] ERROR: 1 error compiling Code

 

this is the Code

 

player.Battlelog404 == true

[ImportBot]

Originally Posted by PapaCharlie9*:

 

When i set it to Code i got this error....

 

[05:03:05 30] [insane Limits] ERROR: 1 error compiling Code

 

this is the Code

 

player.Battlelog404 == true

I think you changed the wrong one. first_check should be Expression, second_check should be Code. Also, are you using 0.0.0.7? Battlelog404 requires 0.0.0.7 or later.

 

There should be some additional error information in the plugin log window before the "1 error compiling" message, which gives the line and column number where the error occurs, as well as exactly what the compilation error is.

 

In general, please provide all information related to the error, such as log snippets, dump files, source code, etc. In the case of an "error compiling", do a

 

!dump limit (id)

 

where (id) is the number of the limit in the console command field of Insane Limits, get the file that is created and attach it to a post. The line and column numbers in the compilation error details refer to that file, not to the cut&paste.

[ImportBot]

Originally Posted by QUACK-Major-Pain*:

 

Which part are you referring to? ... The announcement or the !adminlist command?

 

I have not tested it ... but it seems that if you are admin, and joining, you won't see the announcement because you'd be in the loading screen when the announcement is sent, which is ok.

If it acts like the other plugin that announces admin join, you might see the message in the chat panel of Procon as you join.

[ImportBot]

Originally Posted by micovery*:

 

If it acts like the other plugin that announces admin join, you might see the message in the chat panel of Procon as you join.

Chat-Tab notifications are not supported yet. It's coming in 0.0.0.8.

[ImportBot]

Originally Posted by Mootart*:

 

I think you changed the wrong one. first_check should be Expression, second_check should be Code. Also, are you using 0.0.0.7? Battlelog404 requires 0.0.0.7 or later.

 

There should be some additional error information in the plugin log window before the "1 error compiling" message, which gives the line and column number where the error occurs, as well as exactly what the compilation error is.

 

In general, please provide all information related to the error, such as log snippets, dump files, source code, etc. In the case of an "error compiling", do a

 

!dump limit (id)

 

where (id) is the number of the limit in the console command field of Insane Limits, get the file that is created and attach it to a post. The line and column numbers in the compilation error details refer to that file, not to the cut&paste.

i bring it back as before expression first check and second on code.

 

 

[22:37:47 72] [insane Limits] Compiling Limit #18 - Kick Players Without Battlelog - OnSpawn

[22:37:47 74] [insane Limits] ERROR: 1 error compiling Expression

 

 

also PapaCharlie9 the limit ingame per weapon headshot percentage kicker. its working tho. but every end of the round layer procon is restarting. if if disable it eveything is working fine.

 

what do you think?

 

im using 0.7

[ImportBot]

Originally Posted by Mootart*:

 

Where i can grab the dumb file_?

[ImportBot]

Originally Posted by pharbehind*:

 

Where i can grab the dumb file_?

With that attitude I'm not going to tell you!

[ImportBot]

Originally Posted by ganjaparadise*:

 

Where i can grab the dumb file_?

With your FTP access Plugins/BF3/InsaneLimits.dump

[ImportBot]

Originally Posted by Mootart*:

 

With that attitude I'm not going to tell you!

what attitude sir? i just quick post... what is wrong with my post sir?

[ImportBot]

Originally Posted by Mootart*:

 

With your FTP access Plugins/BF3/InsaneLimits.dump

Thank you so much..... got it now! thanks for you time...

[ImportBot]

Originally Posted by pharbehind*:

 

what attitude sir? i just quick post... what is wrong with my post sir?

Sir, it was just a joke on your typo, you said:

 

"where can i grab the *dumb* file___" instead of "where can i grab the *dump* file_"

 

When reading it like that it sounds like you're upset.

 

sigh...

 

dumb? ?[duhm] adjective, -er, -est, verb

adjective

1.

lacking intelligence or good judgment; stupid; dull-witted.

 

dump? ?[duhmp] noun

16. an accumulation of discarded garbage, refuse, etc.

[ImportBot]

Originally Posted by droopie*:

 

any update on !punish limits? like i said before, im looking for a !punish count. once counted to 5, kick the person who has reached that number.

 

so im currently just using the punish plugin but its conflicting with votekicks and votebans with this plugins limits. can i then just use limits for !punish kill tker?

[ImportBot]

Originally Posted by PapaCharlie9*:

 

any update on !punish limits? like i said before, im looking for a !punish count. once counted to 5, kick the person who has reached that number.

 

so im currently just using the punish plugin but its conflicting with votekicks and votebans with this plugins limits. can i then just use limits for !punish kill tker?

I don't quite understand. I've never used a "punish" plugin, so I'm not familiar with how it is supposed to work, but it sounds interesting.

 

Are you saying an admin can type in a command like this:

 

!punish (count) (player name) (action) (message)

 

So say I want to kick micovery if he TKs 5 or more times, I might use this command:

 

!punish 5 mico kick too many teamkills

 

What happens on TK 1 through 4? Nothing? Warning message?

 

Does it only work for teamkills? What about team switching, base camping, failing to join a squad, etc.?

[ImportBot]

Originally Posted by droopie*:

 

also any chance of adding (revision #) in the op list of examples to know which is updated?

[ImportBot]

Originally Posted by droopie*:

 

I don't quite understand. I've never used a "punish" plugin, so I'm not familiar with how it is supposed to work, but it sounds interesting.

 

Are you saying an admin can type in a command like this:

 

!punish (count) (player name) (action) (message)

 

So say I want to kick micovery if he TKs 5 or more times, I might use this command:

 

!punish 5 mico kick too many teamkills

 

What happens on TK 1 through 4? Nothing? Warning message?

 

Does it only work for teamkills? What about team switching, base camping, failing to join a squad, etc.?

if a player teamkills, the victim can type !punish and what that does is it kills them. thats all i use for the Insane Punisher plugin. since that plugin contains a votekick and voteban, it conflicts with this plugins vote system. i have tried changing it but people are now so used to the universal !votekick/!voteban from other plugins in bf3.

 

what i am really wanting is a that everytime a player teamkills and the victim types !punish, for it to count how many times he has been !punished in a round. once the tker gets 5 !punish from any players on the same team, kick the tker.

 

 

micovery teamkills droopie

droopie: !punish micovery

Admin: micovery you have 1/5 punish. 4 more = autokick.

 

micovery teamkills PapaCharlie9

PapaCharlie9 : !punish micovery

Admin: micovery you have 2/5 punish. 3 more = autokick.

 

micovery teamkills droopie

droopie: !punish micovery

Admin: micovery you have 3/5 punish. 2 more = autokick.

 

micovery teamkills PapaCharlie9

PapaCharlie9 : !punish micovery

Admin: micovery you have 4/5 punish. 1 more = autokick.

 

micovery teamkills droopie

droopie: !punish micovery

Admin: micovery you have 5/5 punish. goodbye.

> micovery has been kicked by the server.

 

 

just an exmaple of how i wish a punishing system should work. all Admin: is the limits counting the tkers !punish so once it reaches 5, he is kicked from the server.

 

since having a tk value on the server of 5, no way to tell which is accidental so the server kicks no matter what once it is reached, accidental or not. this way, have the option to kick if a real tker is on and not worry about the server kicking for accidental tks. even though some teammates will still punish even if its accidental but when tking a clan member they are more understanding and not so quick with !punish. you can last longer in the server if tking.

[ImportBot]

Originally Posted by PapaCharlie9*:

 

if a player teamkills, the victim can type !punish and what that does is it kills them.

Oh, I have seen that. Actually, I got !slap-ped and !insult-ed, but not killed. Same plugin, I guess. I'll leave this one to micovery, since he's the Insane Punisher.

[ImportBot]

Originally Posted by micovery*:

 

if a player teamkills, the victim can type !punish and what that does is it kills them. thats all i use for the Insane Punisher plugin. since that plugin contains a votekick and voteban, it conflicts with this plugins vote system. i have tried changing it but people are now so used to the universal !votekick/!voteban from other plugins in bf3.

 

what i am really wanting is a that everytime a player teamkills and the victim types !punish, for it to count how many times he has been !punished in a round. once the tker gets 5 !punish from any players on the same team, kick the tker.

 

 

micovery teamkills droopie

droopie: !punish micovery

Admin: micovery you have 1/5 punish. 4 more = autokick.

 

micovery teamkills PapaCharlie9

PapaCharlie9 : !punish micovery

Admin: micovery you have 2/5 punish. 3 more = autokick.

 

micovery teamkills droopie

droopie: !punish micovery

Admin: micovery you have 3/5 punish. 2 more = autokick.

 

micovery teamkills PapaCharlie9

PapaCharlie9 : !punish micovery

Admin: micovery you have 4/5 punish. 1 more = autokick.

 

micovery teamkills droopie

droopie: !punish micovery

Admin: micovery you have 5/5 punish. goodbye.

> micovery has been kicked by the server.

 

 

just an exmaple of how i wish a punishing system should work. all Admin: is the limits counting the tkers !punish so once it reaches 5, he is kicked from the server.

 

since having a tk value on the server of 5, no way to tell which is accidental so the server kicks no matter what once it is reached, accidental or not. this way, have the option to kick if a real tker is on and not worry about the server kicking for accidental tks. even though some teammates will still punish even if its accidental but when tking a clan member they are more understanding and not so quick with !punish. you can last longer in the server if tking.

Droopie, last week I updated the Insane Punisher to work well with BF3, and added a feature to do exactly this. It has a new "Automation" section, that allows you to set two variables auto_action , and auto_action_max.

 

Here is the link:

 

www.phogue.net/forumvb/showth...ch1-(beta-BF3)*

 

EDIT:

 

If you do not want to use that, then wait for 0.0.0.8. It will be possible to make a simple !punish/!forgive example for Insane Limits since I will be including by default the victims/killers tracker from PapaCharlie9 ( it will also contain team-kill information).

[ImportBot]

Originally Posted by PapaCharlie9*:

 

Would anyone be interested in a "make room for clan member" in-game command? Whenever our server gets full and there is a queue of players and one of our mates wants to get on, we manually pick and kick players until they get on. I'd rather that the reserved list worked, but whatever. It occurs to me that the picking-and-kicking part can be automated. We usually use some simple conditions, like:

 

* Not in a squad

* Low score/kills

* Kick from the winning team before the losing team, but keep teams balanced (or maybe this should be the other way around, if the replacement player will help the losing team_)

* If the round is about to end, don't do any kicking, just wait

 

Exactly the sort of conditions that could be made into an Insane Limit.

 

I assume player.SquadId is 0 if the player is not in a squad, so that part is easy. Low score/kills super easy. Winning team over losing team, easy. Near end of round, easy.

 

The whitelists can be used to exempt certain tags or player names from the pick-and-kicker.

 

The command could be something like:

 

!makeroom

 

It will apply the conditions and kick one player. Type the command again to kick another, until your bro gets on.

 

If there's sufficient interest, I'll write this example up.

[ImportBot]

Originally Posted by pharbehind*:

 

@PapaCharlie Definitely interested. We do the same manual labor method as you.

[ImportBot]

Originally Posted by QUACK-Major-Pain*:

 

Would be nice.

After hearing people say it wasn't possible.

 

Only issue you would have to work around is if 4 people in the queue, and JoePlayer wants on the server.

You would have to kick a player to allow the next person in the queue to join, and repeat until JoePlayer connects.

 

Maybe a command like !makeroom JoePlayer, where if kicks until this person connects.

Kicks would have to be so many secs apart to allow the person from the queue to join.

 

Also a check so that if the queue = 0, stop kicking.

[ImportBot]

Originally Posted by micovery*:

 

Would be nice.

You would have to kick a player to allow the next person in the queue to join, and repeat until JoePlayer connects.

Keep kicking the people who just joined (that were in queue), unless is the VIP you are looking for.

 

You could set the kick-message to something like

 

Something went wrong

You were disconnected from EA Online (1)

They'll never know jeje.

 

Or if you don't want to be sneaky, you tell them the truth ...

 

You were bumped from the Join Queue to make room for a VIP

[ImportBot]

Originally Posted by QUACK-Major-Pain*:

 

I like the typical EA error better. lol

[ImportBot]

Originally Posted by WaxMyCarrot*:

 

Yes this would be great.. but rather than "!makeroom joeplayer" maybe "!makeroom 4" if 4 people are in que.. that would be easier than typing out a playername each time.

[ImportBot]

Originally Posted by micovery*:

 

Yes this would be great.. but rather than "!makeroom joeplayer" maybe "!makeroom 4" if 4 people are in que.. that would be easier than typing out a playername each time.

You don't know each time how many people are in queue ... though you could get the info from Battlelog.

 

But it does not matter ... first kick 1 player from server, wait 10 seconds, kick next player that joined, wait 10 more seconds, kick next joiner, and so forth.

 

 

This process has two ways to stop.

• The player that just joined is in the VIP list, so you don't kick him (let him in)
• The 10 seconds time-out expired and no-one joined.

Eventually if you keep doing this, you will clear entire queue,

 

So the real command should be more like flush/clear/empty queue.

 

The main problem with this is that if your queue is really big, and you run "!clear queue" by accident (or the VIP leaves the queue) you would have bumped them all for no reason.

 

The # argument you suggest could serve as a third (fail-safe) stopping condition ... to specify how many players to bump from queue in the worst case that none of the other 2 stopping conditions are met.

[ImportBot]

Originally Posted by droopie*:

 

Droopie, last week I updated the Insane Punisher to work well with BF3, and added a feature to do exactly this. It has a new "Automation" section, that allows you to set two variables auto_action , and auto_action_max.

 

Here is the link:

 

www.phogue.net/forumvb/showth...ch1-(beta-BF3)*

 

EDIT:

 

If you do not want to use that, then wait for 0.0.0.8. It will be possible to make a simple !punish/!forgive example for Insane Limits since I will be including by default the victims/killers tracker from PapaCharlie9 ( it will also contain team-kill information).

ill give it a try. it sounds like its just what i need. but if i could do it in this plugin with the next update then its 1 less plugin to manage.