We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This would be quite nice is to reset the Services database Entity ID umber.
When you register a nick or group you get an Entity ID number AAAAA AAAAB etc etc.
When a nick or group gets dropped, it would be quite nice to reset the database Entity ID number.
-- F gets dropped to reset it back to F instead of next one G -- C and E get dropped to re-sort it back in order. A B C D E F
Instead of missing / skipping the ones dropped.
Could be done automatically or an option in xtheme.conf or OperServ command to reset it back.
Or another thought an option to sort the Entity ID number into alphabetical order / date order.
The text was updated successfully, but these errors were encountered:
This has been discussed before, similarly at: https://gist.github.com/alyx/4a73491df0f8a1abffbf but seems to have gone "stale,"
I will leave this open for more discussion on the issue, but at this time - this is not a pressing issue.
Sorry, something went wrong.
No branches or pull requests
This would be quite nice is to reset the Services database Entity ID umber.
When you register a nick or group you get an Entity ID number AAAAA AAAAB etc etc.
When a nick or group gets dropped, it would be quite nice to reset the database Entity ID number.
-- F gets dropped to reset it back to F instead of next one G
-- C and E get dropped to re-sort it back in order. A B C D E F
Instead of missing / skipping the ones dropped.
Could be done automatically or an option in xtheme.conf or OperServ command to reset it back.
Or another thought an option to sort the Entity ID number into alphabetical order / date order.
The text was updated successfully, but these errors were encountered: