[EFFx]

One-Shot Multikill Detection

First release: 03/01/2017
Last update: 04/15/2017



- Description
This plugin allow players to see if someone has killed two or more players just with one bullet.

- Cvars

// (c) One-Shot MultiKill Detection

// Used for check the type of message that will show when someone
// kill two or more players with one bullet
// 2 = CHAT, 1 = LOG MESSAGE, 0 = HUD MESSAGE
osmd_messagetype "0"

// Used for turn on/off the plugin
osmd_enabled "1"

- Change Log

Spoiler

01/03/2017 - v1.0
* First release

01/04/2017 - v1.1
* Code optimization
Observation:

If you want to add different colors to the message on CHAT mode, always use ^4, ^3 or ^1. In the current moment I don't know how I can fix the problem using !g, !t and !y, because the format replace_all() is replacing only ^4, ^3 and ^1 for don't show that icons to the hud and log message. An example: if you add !g, the word 'grenade' will show renade because the replace_all() is removing the !g..

01/07/2017 - v1.2
* Code optimization

01/09/2017 - v1.3
* Code optimization
Observation:

Now, the cvars that was organizing the messages, are now changed.

2 = CHAT, 1 = LOG MESSAGE, 0 = HUD MESSAGE
osmd_messagetype "0"

01/11/2017 - v1.4
* Code optimization
* Added +0.5 seconds to show the message on Death Msg. This is the unique solution I got for fix the problem that shows the message aleatory.
* Added MultiLanguage

Observation about ML: https://forums.alliedmods.net/showpo...4&postcount=60

03/07/2017 - v1.5
ºAdded forwards:
. I have added two forwards, they're:

PHP Code:

client_OneShot(id, iKills, iWeaponID)
client_OneGrenade(id, iKills) 


For use them, just put

PHP Code:

#include <oneshotmd> 


in your custom plugin.

ºCode edited:
. Removed a check for see if is not a TK because a condition 1>0 at register_event() already checks it.

04/15/2017 - v1.6
. Added osmd_api_only cvar for the case if someone want the plugin only with the API.
. Removed the userWeapon global.
. Using the set_task() for parse all the API infos
. Uploaded the .cfg file.

- How to install?
Put the .sma file on dir/addons/amxmodx/scripting
Put the .amxx file on dir/addons/amxmodx/plugins
Put the folder OneShotMD on dir/addons/amxmodx/configs
Put the file osm_detector.txt on dir/addons/amxmodx/data/lang

After it, put the plugin's name on plugins.ini

[Craxor]

litttle horribile for the moment ( i mean the code and the indentation ) .. but i'm waiting :p

Also what about Laser Mod ? You should focus to only 1 plugin until you get something with it ...

Can pleaseeeeeee name it "kill two birds with one stone" : ) )

[EFFx]

Sorry about the code, its my style
Sorry about the indentation, here in my Text editor* its nice.

I hate the name you said.

[klippy]

Originally Posted by EFFx here in my compiler its nice.

Text editor*, compiler is something else.
Indentation looks alright to me, not sure what Craxor is talking about.

Originally Posted by EFFx I hate the name you said.

"Kill two birds with one stone" is a very popular phrase in English language. Naming your plugin "Two birds, one stone" (or similar) sounds much better and will be much more recognizable. Your current name actually is awful and doesn't make much sense. Even just "One-Shot Multikill Detection" would sound much better.


As for my suggestions, you should add a multiplugin forward in my opinion, so other plugins could detect such kills (with parameters: who did it, weapon used, array of victim ids, how many victims, array of "was it headshot" booleans for every victim). This would be useful for giving bonus XP and such in other mods, for example. That means that you should add an option to your cvar to disable the message completely and use this only as an API.

[aEEk]

It's possible to make this plugin to look like csgo? I mean that 'dead icons' in right corner (I'm not so advanced in coding, maybe is possible using DLL). Did you understand?

PS: Thanks for source

[EFFx]

One-Shot Multikill Detection

Its look much better for me

Originally Posted by aEEk PS: Thanks for source

I appreciate it

That was the first name I found, but I was going to change him, I just was searching a better than the original
Sorry about the popular phrase on english, I don't knew it.

[EFFx]

Originally Posted by aEEk It's possible to make this plugin to look like csgo? I mean that 'dead icons' in right corner (I'm not so advanced in coding, maybe is possible using DLL). Did you understand? PS: Thanks for source

I don't know nothing from CSGO, but you can make a thread on SourceMod requesting that.

Originally Posted by KliPPy As for my suggestions, you should add a multiplugin forward in my opinion, so other plugins could detect such kills (with parameters: who did it, weapon used, array of victim ids, how many victims, array of "was it headshot" booleans for every victim). This would be useful for giving bonus XP and such in other mods, for example. That means that you should add an option to your cvar to disable the message completely and use this only as an API.

I just see it right now, its a great idea and I had that idea too.

Edit:
But how suggest you to I add this? Because the event DeathMsg will run only when someone has killed someone. If someone want to give a bonus for who has killed more than 1 player with one bullet, need just add on my source code.

[fysiks]

Line 303 (shown below) is wrong and will give an error every time.

PHP Code:

set_pcvar_num(iMessageType, 0) 


Also, in GetMessageType(), you should use a switch for iMessageType.

More importantly, using GetMessageType() to populate a global variable every time that you use that global variable is unnecessary and confusing (confusing particularly because of the name). Simply do this:

PHP Code:

MessageTypes:GetMessageType()
{
    new MessageTypes:iMessageType = MessageTypes:get_pcvar_num(cVars[pCvarMessageType])
    new MessageTypes:returnValue
    
    switch( iMessageType )
    {
        case CHAT, HUD, LOG:
        {
            returnValue = iMessageType
        }
        default:
        {
            returnValue = CHAT
            // set_pcvar_num(cVars[pCvarMessageType], _:CHAT) // Not entirely necessary
        }
    }

    return returnValue
} 


Now, the name makes more sense and you would use it like this:

PHP Code:

SendMessage(0, GetMessageType(), /*...*/) 


This:

PHP Code:

    register_plugin
    (
    .plugin_name = PLUGIN,
    .version = VERSION,
    .author = AUTHOR
    ) 


Is formatted unnecessarily and is ugly. Don't use dot notation unless you are going to be skipping several parameters. If you are using all parameters, simply supply all three parameters normally. Also, there is no real advantage to putting such a short command on multiple lines. Use a single line, even with dot notation, it will be shorter than many other lines of your code.

About indentation, the only thing that is ugly is that there are three tabs after an equal sign in an assignment statement. Trying to line things up with multiple tabs is guaranteed to look bad in someone's editor. Most of the time, lining assignment statements up like this is adds no value.

[EFFx]

Sorry about the error, it doesn't give an error for me.

PHP Code:

MessageTypes:GetMessageType() 
{ 
    new MessageTypes:iMessageType = MessageTypes:get_pcvar_num(cVars[pCvarMessageType]) 
    new MessageTypes:returnValue 
     
    switch( iMessageType ) 
    { 
        case CHAT, HUD, LOG: 
        { 
            returnValue = iMessageType 
        } 
        default: 
        { 
            returnValue = CHAT 
            // set_pcvar_num(cVars[pCvarMessageType], _:CHAT) // Not entirely necessary 
        } 
    } 

    return returnValue 
} 


Hm, I was searching how can I use that function like this:

PHP Code:

new szMessageTypeName[32]
GetMessageType(szMessageTypeName,charsmax(szMessageTypeName)) 


But I don't know how do that.

This,

PHP Code:

SendMessage(0, GetMessageType(), /*...*/) 


That give an error.

Look what I made:

PHP Code:

MessageTypes:GetMessageType(MessageTypes:returnValue) 
{ 
    new MessageTypes:iMessageType = MessageTypes:get_pcvar_num(cVars[pCvarMessageType]) 
     
    switch(iMessageType) 
    { 
        case CHAT, HUD, LOG: 
        { 
            returnValue = iMessageType 
        } 
        default: 
        { 
            returnValue = CHAT 
        } 
    } 
    return returnValue 
} 


PHP Code:

SendMessage(0,GetMessageType(MessageType),"^4%s^1's grenade killed^4 %d^1 players!",szName,iKills) 


The MessageTypes:MessageType is a global.

PHP Code:

SendMessage(const index, MessageTypes:MsgType,const message[],any:...) 


[HamletEagle]

Is formatted unnecessarily and is ugly. Don't use dot notation unless you are going to be skipping several parameters. If you are using all parameters, simply supply all three parameters normally. Also, there is no real advantage to putting such a short command on multiple lines. Use a single line, even with dot notation, it will be shorter than many other lines of your code.

Saying it's ugly is only a matter of subjectivity and should never be part of a review. Don't try to enforce your own style.
Also, about when one should use the dot or not, here it's just a style.

Also, there is no real advantage to putting such a short command on multiple lines. Use a single line, even with dot notation, it will be shorter than many other lines of your code.

No one is doing that for practical advantages. I'm personally using that way of writting the register_plugin line as my signature, for visual purpose only.