[Synthax]

Can this plugin support SourceComms as well as SourceBans? there's no simple way to view who is punished via voting and no easy way to modify that punishment or override it. Also, perhaps disabling voting for normal players when players with certain flags are on the server? (eg. admins/moderators)

[Phaiz]

Originally Posted by Synthax Can this plugin support SourceComms as well as SourceBans? there's no simple way to view who is punished via voting and no easy way to modify that punishment or override it. Also, perhaps disabling voting for normal players when players with certain flags are on the server? (eg. admins/moderators)

Several people, myself included, have asked for this feature. The plugin uses local databases on the game server rather than remote databases. This is why it doesn't integrate with sourcecomms. From what I've been told, it would be a rather easy fix to change it. However for whatever reason he doesn't want to make this an option. Even if it means having two released versions (one for local, one for remote) it would still help. You can see his response to the idea here
https://github.com/neatek/GameVoting...mment-77686747

Dependence I dont respect Sourcecomms. By the way, GameVoting using own style for mute and silence. I dont want to be dependent from other plugins, so, because i remove basecomm.smx and clientpref.smx dependence. Dependence from other plugins is problems, because if one plugin was broken, my plugin will not working, i dont want it.

edit-
Vote bans however do make it to the sourcebans database and are therefor displayed on the bans page and can be edited. I would venture to guess it is because the plugin still uses the /sm_ban command for this, which is picked up by sourcebans if you have it installed. I would also venture to guess that if the plugin were to use the SM gag/mute commands, they would also be picked up by sourcebans. However this is not the case as it enters the data directly into the local database rather than using a command

[mazdarx8]

I use newest SM and MM and if we type votekick Player A
after sucessfull vote he will kick Player B and not Player A

Why?

[keigel2001]

Yeah I have the same problem. At least with small values. I messaged him months ago but he didn't respond.
Just try out yourself:

L 06/05/2015 - 08:34:37: [GameVoting.smx] Player DeutscheMark(STEAM_x:x:xxx) voted for kick Bender Bending Rodríguez(STEAM_x:x:xxx) (1/2)
L 06/05/2015 - 08:34:46: [GameVoting.smx] Player BoOm(ٿ)(STEAM_x:x:xxx) was kicked.

It's just kicking the one that did the 2/2 vote. The wrong person.

Another Example:

L 08/29/2015 - 21:37:19: [GameVoting.smx] Player shurgalFly(STEAM_x:x:xxx) voted for kick Obelisk(STEAM_x:x:xxx) (1/4)
L 08/29/2015 - 21:37:32: [GameVoting.smx] Player Wupkins(STEAM_x:x:xxx) voted for kick Obelisk(STEAM_x:x:xxx) (2/4)
L 08/29/2015 - 21:37:48: [GameVoting.smx] Player Hurensöhne(STEAM_x:x:xxx) voted for kick Obelisk(STEAM_x:x:xxx) (3/4)
L 08/29/2015 - 21:38:36: [GameVoting.smx] Player Masterpiece(STEAM_x:x:xxx) was kicked.
L 08/29/2015 - 21:38:49: [GameVoting.smx] Player Masterpiece(STEAM_x:x:xxx) was autokicked. Need to wait 287 before connect.

I think it's working correctly with bigger values like 10 or 12. But sometimes it's just kicking/banning the wrong person...

[yomox9]

You should change "1.7" to "1.7.5" in ConVars.sp.....>neatek

[poel]

Hi !!

I got some spam errors :

Displaying call stack trace for plugin "gv.smx":
L 12/13/2015 - 19:01:02: [SM] [0] Line 832, G:\steamcmd\cs_go\cstrike\addons\sourcemod\sc ripting\gv.sp::gvResetVote()
L 12/13/2015 - 19:01:02: [SM] [1] Line 273, G:\steamcmd\cs_go\cstrike\addons\sourcemod\sc ripting\gv.sp::OnClientDisconnect()


If someone can fix

[Randommagic]

As mentioned in
https://forums.alliedmods.net/showpo...&postcount=159
It would be really nice if the players are kicked as soon as they are votebanned.

[Dency]

#174 Kiegel2001


Same problem. i'm using source mod 1.7.3 build 5283

[Nerus]

Same problem here.

[Wilczek]

Partially it also happens to voteban. Plugin bans correct player, but write in logs another one.