[LenHard]

Description

A gamemode of deception and murder, based off of Murder in the Dark.
One person is a murderer with a knife, who is trying to secretly kill off the other players.
The other players must use their wits to find out who it is and kill them first.
Unfortunately they only have the one gun between them. (Source)


Instructions

After adding all the files in the correct places, you need to add a MySQL database to make the plugin work. Go to configs/databases.cfg and add "Murder" with your own database information.

Example:

"Murder"
{
	"driver"		        "default"
	"host"				"YourHost"
	"database"			"YourDatabase"
	"user"				"YourUser"
	"pass"				"YourPassword"
	//"timeout"			"0"
	"port"				"3306"
}

To add or modify the prop models or voice commands; go to configs/Murder/Props.cfg or Radio.cfg and follow the format.

Example:

"Props"
{
	"Model name"
	{
		"model"		"model's path"
	}
}

"Radio"
{
	"Sound name"
	{
		"sound"		"sound's path"
	}
}

All the models you could use are here. Some of them don't work.

ConVars

Spoiler

murder_players_needed - Amount of players needed to start a murder game.
murder_radio_delay - Amount of time to delay between the uses of the voice commands.
murder_smoke_time - Amount of time to trigger the smoke effect on the murderer.
murder_smoke_addition - Amount of time added to each kill the murderer receives to delay the smoke effect.
murder_models_enabled - Enable Model switching during disguise?
murder_prop_disguise_amount - Amount of clues needed to be able disguise as dead players.
murder_prop_gun_amount - Amount of props collected to receive a gun.
murder_prop_respawn_time - Amount of time till a random set of props spawn.
murder_knife_duration - The time that gives the murderer his knife back after throwing.
murder_footsteps_life - Life time of the footsteps displayed on the ground.
murder_doublejump_enabled - Enable Multi or double Jumping?
murder_doublejump_max - Max amount of jumps allowed in the air?
murder_doublejump_height - Height of each jump?

Natives

Spoiler

/**
* Retrieves the current Murderer.
*
* @noparam
* @return Murderer User ID
*/
native int GetMurderer();

/**
* Sets a client to be a Murderer.
*
* @param Index Client's User ID
* @noreturn
*/
native void SetMurderer(int client);

/**
* Retrieves the current Detective.
*
* @noparam
* @return Detective User ID
*/
native int GetDetective();

/**
* Sets a client to be a Detective or Special Bystander.
*
* @param Index Client's User ID
* @noreturn
*/
native void SetDetective(int client);

/**
* Retrieves client's character.
*
* @param Index Client's User ID
* @param String Client's Character Name (with chat colors)
* @noreturn
*/
native void GetClientCharacter(int client, char[] sCharacterName);

Credits

Bara - Grabber Mod
paegus - Double Jump
I forgot who else.. If I used your code, let me know, so I could credit you.

[iGANGNAM]

what kind of maps for this? same as ttt?

[Mitchell]

Seems a bit of a waste of a needing a database for something that can be stored in a text file. Nice work though.

[LenHard]

Originally Posted by iGANGNAM what kind of maps for this? same as ttt?

It could be any map but yes, mainly TTT maps.

Originally Posted by Mitchell Seems a bit of a waste of a needing a database for something that can be stored in a text file. Nice work though.

True, but I assumed it would be more reliable and quicker than regular Key Values when it came to this.

[Mitchell]

Originally Posted by LenHard True, but I assumed it would be more reliable and quicker than regular Key Values when it came to this.

The way I see it is that a database to hold less than 100 inputs per setup map is a waste of a connection to a MySQL db. Especially when having them as a keyvalue that only loads when the map start, even if it was considered slow, i'm sure it would be faster than a player connecting to the new map. Having them as keyvalues also helps when sharing a map config, instead of posting a sql query for a map.

[LenHard]

Originally Posted by Mitchell The way I see it is that a database to hold less than 100 inputs per setup map is a waste of a connection to a MySQL db. Especially when having them as a keyvalue that only loads when the map start, even if it was considered slow, i'm sure it would be faster than a player connecting to the new map. Having them as keyvalues also helps when sharing a map config, instead of posting a sql query for a map.

Well in the Murder case, the props will respawn every x seconds with different sets. There would be at least a hundred props per map (6 sets). I'll probably push key values for the next version.

[iGANGNAM]

Ah sorry, didn't read post you made in #6
hoping that you can release your sets soon
as Mitchell said, KeyValues thing would be alot easier to share with people.

[Lannister]

Hello! i've uploaded the plugin to my server but i've experienced some bugs and a server crash,

Error log:

L 07/11/2020 - 19:21:50: [SM] Call stack trace:
L 07/11/2020 - 19:21:50: [SM]   [0] CloseHandle
L 07/11/2020 - 19:21:50: [SM]   [1] Line 1716, C:\CSGO-Server\csgo\addons\sourcemod\scripting\Murder\Murder.sp::Menu_RoundData
L 07/11/2020 - 19:21:50: [SM] Exception reported: Handle 147103e is invalid (error 3)
L 07/11/2020 - 19:21:50: [SM] Blaming: murder.smx

Crash log

https://crash.limetech.org/hr4y6o6pr5vt

And i had some text colour bugs too, probably because it's an old plugin, like, it was showing a text instead of the colour,

I know that probably no one use this plugin, but it's a very good mod, and i'd love to have it in my server, but sadly with the crashes i'm not able,

I hope you can fix this! Thanks!

[Sandervraun]

I was wondering if it would be cool, as the killer to have the ability to turn on/off a "night vision", which would be red (to meet the more scary side and make it more cool that the usual green night vision). And normal players(ct) would get a flashlight..

[Affe71]

For anyone wondering the mod is still working fine as long as you configure your database right.