[klippy]

Menu character limit is 512 I think, so having like 40-50 characters for each message (just username + message preview) in the menu would look good. When you click on the menu item you can display a new old-style menu that would show more info (nick, steam id, full message, actions to take for that message).
And yes, Bugsy is right, deletion shouldn't be an option, only archiving; Manual or automated after a certain time interval (7 days for example, configurable).
There's actually a lot of potential for this, I may use it turns out to be great and featureful. I'd like to see replying as well - you reply to a message, next time they join they can see it as well. Like a fully featured ticket support system.

[Natsheh]

I once made a plugin with features that kilppy suggested even it supported sql but i didnt publish it and i lost it it was called report, hopefully you will add those features.

[JocAnis]

cool idea...ye good suggestions for adding when admins saw message, and option for replying

[edon1337]

Thanks everyone for your suggestion, I'll start adding some of your suggestions in the up-coming version.

[Bugsy]

Switching to SQL may be a good idea, it will make transactions easier and more efficient than nvault array. If you need help with any of the suggestions let me know, I have nothing on my plate right now.

[HamletEagle]

You should have a deletion option along with archiving. There is no reason to keep troll/insulting messages or messages that are like 6 months/1 year old. Or the message could simply be useless and you don't want the archive to become messy/filled with garbage and make it harder to search for a specific message in the future. You may want to keep in the archive only messages that may be needed at a later date.
And at the end of the day, this gives more power to the end user, which should always be welcome.

[edon1337]

Originally Posted by Bugsy Switching to SQL may be a good idea, it will make transactions easier and more efficient than nvault array. If you need help with any of the suggestions let me know, I have nothing on my plate right now.

I have 0 knowledge on SQL, so for me using nVault Array is easier.

Originally Posted by HamletEagle You should have a deletion option along with archiving. There is no reason to keep troll/insulting messages or messages that are like 6 months/1 year old. Or the message could simply be useless and you don't want the archive to become messy/filled with garbage and make it harder to search for a specific message in the future. You may want to keep in the archive only messages that may be needed at a later date. And at the end of the day, this gives more power to the end user, which should always be welcome.

Yes, I'm adding a Delete option, but not an archive one, I see no point to archive messages, simply delete or keep them.

Can someone tell me what the character limit is for the new menu system title? Or is it same as menu items (512 according to Klippy).

[Natsheh]

There is no such thing is menu title characters limit, but im not sure about this it might be 196.

All i know that menu total characters limits is 512.

You can define the menu title length i dont recommend to be greater than 196 char unless you are using no items which its impossible because the new menu system needs atleast 1 item to can show the menu.


And SQL isnt a hard language you could learn it in less than 48 hours (simple level)

[edon1337]

Originally Posted by Natsheh There is no such thing is menu title characters limit, but im not sure about this it might be 196. All i know that menu total characters limits is 512. You can define the menu title length i dont recommend to be greater than 196 char unless you are using no items which its impossible because the new menu system needs atleast 1 item to can show the menu. And SQL isnt a hard language you could learn it in less than 48 hours (simple level)

Ok thank you. I don't really have time to learn new things till I finish all my exams (probably December).

@Bugsy

Is nvault_set_array meant to push new entries or edit existing entries?

[DJEarthQuake]

#Edon. Make it so it costs to send message. That is within your comfort zone and will control plugin abuse. The plugin I was referring to early post was as adminmod plugin: Updated: Leave messages for *specific* clients as they connect.
This old AMX work reminds me of your style, PostMessage where it charges user to POST messages on server.