Unique Profile ID String
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

Unique Profile ID String

Started by Snooze, 14 March, 2008, 17:52:51

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Snooze

To make it easier for large scripts to setup commands rights per profile, it would be sweet if each profile had a unique ID.
This would prevent command rights to change if/when a new profile were created.

This would not exclude having profile listed the way we do today:

0 = Master
1 = Operator
3 = VIP
4 = Reg

What im suggesting is that each profile would also have a extra identifier such as:

0 = Master with ID "WP4Q"

This might be called with ProfMan.ID(tNick) returning string ID or nil for unregged

This would really make AIO scripting a lot easier with custom profiles :-)


If anyone has a better idea of how to control cmd rights, Im all ears :D


/Snooze

[EDIT]
Using custom PtokaX profile rights might be even better...
As in having the option to add a custom profile right in PtokaX and "just" assing this right to the Profiles. (Already suggested by Mutor)
[/EDIT]

SMF spam blocked by CleanTalk