General > Developers Corner

Advice

<< < (2/3) > >>

Aaron113:

--- Quote from: MrPresident on May 17, 2015, 12:12:17 AM ---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.

--- End quote ---
That is true unless it is something custom.

Tomzen:
I've already finished it, so there's no point of replying to this anymore -.-

MrPresident:
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.

Bite That Apple:
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.

MrPresident:
He is currently using a client ConVar.

Navigation

[0] Message Index

[#] Next page

[*] Previous page