Talk:Left 4 Voting 2 - Revision history

Dr. Greg House at 07:39, 13 June 2013

2013-06-13T07:39:06Z

Dr. Greg House at 07:37, 13 June 2013

2013-06-13T07:37:49Z

Powerlord at 03:46, 13 June 2013

2013-06-13T03:46:48Z

Dr. Greg House: Use a hook into "VoteRegistered" instead of hooking the vote command?

2013-06-13T03:23:40Z

Use a hook into "VoteRegistered" instead of hooking the vote command?

New page

Wouldn't it be a better idea to hook the user message "VoteRegistered" and use const players[] (which length would be 1 and would contain the userid or clientid(?)) to determine which player did the vote? This would be more accurate than parsing the vote command and filtering out who has already voted since "VoteRegistered" would only be sent when the vote was actually accepted and not when someone attempts to vote (again or isn't allowed to).

@@ Line 5: / Line 5: @@
 :--[[User:Powerlord|Powerlord]] ([[User talk:Powerlord|talk]]) 22:46, 12 June 2013 (CDT)
-:You're right, it's already mentioned in the explanation on how it works. However, the usermessage is not created and sent in the example. At this point I'm wondering what might happen in that case considering visual acknowledgement aka box getting checked. Does the engine handle it automatically with/on each vote command that's been received, is it the "vote_changed"-event that checks the box or is there no box-checking at all (and it's the usermessage that actually triggers this)? I guess I'll just check that out by my own later when I'll have time to play around with the usermessages.
+::You're right, it's already mentioned in the explanation on how it works. However, the usermessage is not created and sent in the example. At this point I'm wondering what might happen in that case considering visual acknowledgement aka box getting checked. Does the engine handle it automatically with/on each vote command that's been received, is it the "vote_changed"-event that checks the box or is there no box-checking at all (and it's the usermessage that actually triggers this)? I guess I'll just check that out by my own later when I'll have time to play around with the usermessages.
-And yes, your plugin should usually be used as a wrapper, however, I'm actually interested in making it possible for a plugin to register votes and their momentary status and parameters. I was only mentioning the above because it crossed my mind during the read.
+::And yes, your plugin should usually be used as a wrapper, however, I'm actually interested in making it possible for a plugin to register votes and their momentary status and parameters. I was only mentioning the above because it crossed my mind during the read.
---[[User:Dr. Greg House|Dr. Greg House]] ([[User talk:Dr. Greg House|talk]]) 02:37, 13 June 2013 (CDT)
+::--[[User:Dr. Greg House|Dr. Greg House]] ([[User talk:Dr. Greg House|talk]]) 02:37, 13 June 2013 (CDT)

← Older revision		Revision as of 07:37, 13 June 2013
Line 4:		Line 4:
	:Granted, at this point you might as well use the SourceMod NativeVotes plugin as it's a wrapper for the L4D, L4D2, TF2, and CS:GO vote systems.		:Granted, at this point you might as well use the SourceMod NativeVotes plugin as it's a wrapper for the L4D, L4D2, TF2, and CS:GO vote systems.
	:--[[User:Powerlord\|Powerlord]] ([[User talk:Powerlord\|talk]]) 22:46, 12 June 2013 (CDT)		:--[[User:Powerlord\|Powerlord]] ([[User talk:Powerlord\|talk]]) 22:46, 12 June 2013 (CDT)
		+
		+	:You're right, it's already mentioned in the explanation on how it works. However, the usermessage is not created and sent in the example. At this point I'm wondering what might happen in that case considering visual acknowledgement aka box getting checked. Does the engine handle it automatically with/on each vote command that's been received, is it the "vote_changed"-event that checks the box or is there no box-checking at all (and it's the usermessage that actually triggers this)? I guess I'll just check that out by my own later when I'll have time to play around with the usermessages.
		+	And yes, your plugin should usually be used as a wrapper, however, I'm actually interested in making it possible for a plugin to register votes and their momentary status and parameters. I was only mentioning the above because it crossed my mind during the read.
		+	--[[User:Dr. Greg House\|Dr. Greg House]] ([[User talk:Dr. Greg House\|talk]]) 02:37, 13 June 2013 (CDT)

← Older revision		Revision as of 03:46, 13 June 2013
Line 1:		Line 1:
	Wouldn't it be a better idea to hook the user message "VoteRegistered" and use const players[] (which length would be 1 and would contain the userid or clientid(?)) to determine which player did the vote? This would be more accurate than parsing the vote command and filtering out who has already voted since "VoteRegistered" would only be sent when the vote was actually accepted and not when someone attempts to vote (again or isn't allowed to).		Wouldn't it be a better idea to hook the user message "VoteRegistered" and use const players[] (which length would be 1 and would contain the userid or clientid(?)) to determine which player did the vote? This would be more accurate than parsing the vote command and filtering out who has already voted since "VoteRegistered" would only be sent when the vote was actually accepted and not when someone attempts to vote (again or isn't allowed to).
		+	:If you're manually creating the vote, the game server won't handle the vote processing for you and ''you'' will be responsible for sending the VoteRegistered UserMessage yourself based on what Vote command they send to you.
		+
		+	:Granted, at this point you might as well use the SourceMod NativeVotes plugin as it's a wrapper for the L4D, L4D2, TF2, and CS:GO vote systems.
		+	:--[[User:Powerlord\|Powerlord]] ([[User talk:Powerlord\|talk]]) 22:46, 12 June 2013 (CDT)