Ulysses
General => Developers Corner => Topic started by: Tomzen on May 16, 2015, 01:31:36 AM
-
On my ForceMic command, I use "timer.Create", and "timer.Destroy" (or Remove), however the problem with this is that the timer is recreated every time you join, change map, or restart server as you type !accept which runs timer.Remove( "fmmsg" ), any way to make this so if you type it once, you will never have to again?
Or perhaps I should use something other than a timer?
-
You can use PData to read from and to the server's (or clients) SQLite database. PData is kept across map changes and server restarts. Have a look at the Player:SetPData and Player:GetPData functions.
With PData, set some kind of key for each player that can be true of false. Do or don't do stuff depending on the value of that key.
Alternatively, you can use some kind of data file. Write the SteamID of all players that accept in there... Then read... In that case, you will need to make use of the file library (http://wiki.garrysmod.com/page/Category:file).
Reading SQLite is (probably) a lot faster than reading flat files though. So you should go with PData. :)
Edit: added some details
-
Just use a client convar... http://wiki.garrysmod.com/page/Global/CreateClientConVar (http://wiki.garrysmod.com/page/Global/CreateClientConVar)
Less data and stress on your server (not that it would be much anyway).
-
Ahaha, again with the convar, thanks Aaron113.
-
The only problem with using a convar is that it would remember the decision cross server and then the client might not know a new server is using the addon.
You're better off remembering the decision at the server level.
-
The only problem with using a convar is that it would remember the decision cross server and then the client might not know a new server is using the addon.
You're better off remembering the decision at the server level.
That is true unless it is something custom.
-
I've already finished it, so there's no point of replying to this anymore -.-
-
Except for the fact that you didn't take the advice you asked for.
The way you are doing it could go something like this.
Player joins server A with your addon. They accept the warning. They know that server A might be monitoring their mic.
Player joins server B with your addon. Because of the way you are handling it, they never see the warning. They have no idea that server B might be monitoring their mic.
The warning is pointless at this point because it doesn't warn them at all after they've been to a single server that has the plugin. That isn't the purpose of the warning.
I understand if you want to make the warning have some way of remembering their choice so it doesn't pop up all the time, but you need to make it per server, not per client.
-
Basically, you can't have the warning on client side. You need to have (btw, I haven't look at the code of your addon, so I'm assuming you've decided to use PData) it in your server side. So basically, when a player joins server A, the server side sends a usmg telling them to activate the pop up message. Then when you type !accept (or w/e it is), it reads it in the server side PData.
-
He is currently using a client ConVar.
-
He is currently using a client ConVar.
Yeah, I never have used ConVar's in any of my addons because I don't really understand them correctly, they caused issues and such, so I've always just use PData, usmg, and net messages. That's the only way to go in this life.
Pdata 4 life dog
-
I guess I didn't read that is was for his forcemic command. I would definitely use something serverside then. Otherwise players will not get notified over different servers.