Thread
:
VoteManager API (votekick/ban/map/burn/gravity/etc)
View Single Post
ferret
SourceMod Developer
Join Date: Dec 2004
Location: Atlanta, GA
07-08-2007 , 14:37 Re: VoteManager API
#
4
Known Issues
If you wish VM_UnregisterVote and VM_IsCoreReady(), your plugin will become dependant on VMgr_Core being loaded. This will be resolved when Non-Required Natives are fixed. See SM Feature Request
#292
. Since you DO want to Unregister your votes, this is a biggie
Unfortunately, using VMgr at all makes it a requirement right now.
vmgr_ban does not call the OnClientBanned forward like Basic Votes' voteban and sm_ban do. SM Bug
#581
To-Do
Add a sixth VoteType that treats the first argument of a vote as it's title. This is necessary to implement a generic vm_vote.
Add a forward for when the core unloads, so plugins can make sure they know their vote is no longer valid. This is important but not high priority because the core shouldn't unload. Just keep it in mind if you're playing around with it. This is also waiting on an SM Feature Request.
Add a forward for when a vote fails due to no votes received. Someone might care.
Add a native for triggering a vote directly without registering it. This will require the sixth VoteType as well. For example, RTV or MapChooser could use VMgr and the Trigger native, instead of maintaining and building votes themselves.
Add a native for a plugin to set a minimum and maximum range for MultiInt and MultiFloat
Waiting on a new version of ShowActivity that doesn't automatically prefix messages with [SM]. Until them, Vote initiated messages will have "[SM][VM]" instead of just [VM].
__________________
I'm a blast from the past!
Last edited by ferret; 07-08-2007 at
23:13
.
ferret
View Public Profile
Send a private message to ferret
Find More Posts by ferret