Disclaimer:

I know this is a polarizing subject, but no-one is forced to look at this if they don't want to.    

Out of respect for others - I would strongly recommend this is not used (or at least not set to announce to local) in locations that are not going to appreciate it.   I created this for use on my own grid - and its fine there, but many grids may not like this so either dont use it there - or have it only announce to you or your owner.

Overview:

This system is designed to add some "functionality" to any diaper wearers.   This is worn separately to any diaper which means it works with any you may wear - and even works without wearing any (so its more stealth).

This system was created by Claide.ai - over much trial and error and testing by myself (Glenys Bieler).

Code is totally free to use and change but no support is offerered other than the basic instructions:  Please see README for setup instructions.

Functions working:

• White/Black lists 
• Lock/unlock (this should lock/unlock the option for changing - as well as seperately lock the item on.  (This really doesnt have much functionality until RLV is added)
• Manually wet (mostly added to test - but may be wanted for roleplay)
• Check status (others can check your diaper status depending on white/blacklists)
• Change diaper (others can change your diaper depending on white/blacklists) (when RLV is added - will have option to restrict changing to "owner, owner + wearer, all".  Diaper changed is displayed in local chat - together with the name of who changed it)
• Click enabled 
• Command prefix (defaults to first name initial + last name initial + diaper - for Joe Blogg's diaper - it would be jbdiaper for example)
• Command channel (defaults to channel 0 - local chat but can be changed to another channel.  For example change to channel 5 then command would be /5 jbdiaper to use the example above)
• State names can be changed (default dry, damp, wet, soaking, leaking)
• Owner title can be changed (default = Daddy but can be anything - examples given are Daddy, Mummy, Master, Mistress)
• Notify Wearer (of state changes.  Defaults to yes)
• Announce Full (Who should be told when diaper is full - options are Owner IM, Local Chat, Everyone.    Wearer is told if the "Notify Wearer" is enabled above).
• Leak Announce (Who should be told when diaper is leaking - options are Owner IM. Local Chat, Everyone.   Wearer is told if the "Notify Wearer" is enabled above).
• Auto-wet Timer (Allows you to change the interval before you wet yourself automatically - defaults to 30 mins).
• Safeword (defaults to SAFEWORD - not used yet - will be used when RLV is enabled so if your owner locks you in you CAN safeword)
• Reload status 
• Ability to set minimum region maturity level to send any public messages.  If set to Adult for example and the wearer  is in a Moderate area - the script would still work, but willl not send any messages to local chat regardless of announcement settings.  It will only send any messages to the owner/wearer if the region maturity is lower than the setting.
• Initial RLV integration (owner lists, lock hud, lock diaper changes to owner, owner+wearer, open access)

To Add:

• RLV Option: Setting to announce to the owner when the wearer logs on or wears the system.
• RLV Option: Setting a "change limit" - owner could set how many changes are allowed before they change it themselves.  Wearer and third parties could change (if allowed by access mode) but only until that limit is reached.  After that it would simply report to them "No fresh diapers available."
• RLV Option: Setting the minimum state a diaper needs to be in to change.   With the limit of changes implimented above - a third party could change several times to use up the available changes and put the wearer in an unfair position.   If there is an option to set the minimum state needed before allowing change this fixes this issue.  If the minimum state needs to be "wet" for example and someone tried to change when the current state is "Dry" or "Damp" it would reply "Diaper does not need changing yet."
• RLV Option: Allow the owner to set a floating text of the current diaper state so everyone can see (this would be hidden based on the maturity level of the region as above).  The owner could customise the message.   It would be down to the Owner to set this responsibly.  It could be fun in the right scenario (in a region / location that people can expect people wearing diapers) but could upset some people if used without consideration.
• RLV Option: A "stand alone" PHP page (that should be possible to host anywhere with no other settiing up) where an "owner" can go to to check their users status, wetness, online status, and even initiate a wetting (taking more control away from the wearer).   This would of course be disabled by defalt and only the wearer would be able to turn this on - not the owner. This basic script would not have security beyond the owner entering a UUID that would be provided to them by the hud.  This system relies on "security by obscurity" - anyone else getting hold of the UUID could go to that page and access.   The HUD needs to update the PHP page with its current HTTP IN address each time it loads of moves to another region.  The HUD would also need to store the URL of the webpage.  

Any suggestions?

If you have suggestions then please feel free to drop me a notecard to Glenys Bieler on my grid (grid.sub-version.space:8002) or message me here on OpenSimWorld and I will take a look at it.  Obviously no promises and it also depends if Claude.ai can work out what to do (it is actually pretty good at this having created this whole system), but definately interested in any suggestions.