Projects » HappyBums - Incontinence System
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. I believe this is the most functional system available (if there actually ARE any other systems like this in OpenSim) and certainly will be once the PHP Web based controller is integrated where an owner can make changes and interact (including sending an IM to the wearer) from a webpage when not even logged in.
Rather than go through everything that is in this system, please look at the following files:- README
- ARCHITECTURE
- MENU STRUCTURE
This system has an optional web-interface that can allow an "owner" of a "diaper wearer" to monitor and control certain aspects. This requires two files to be uploaded to a web host and requires PHP and Sqlite3 to be installed on the host. I have made it as simple as possible to install this - no configuration is needed. IDEALLY the webserver should be configured to NOT return .db files - or the line in the inco.php script that sets the dbfile - could be put OUTSIDE the webroot. Otherwise someone could just go to the database file on your server and download the whole database.
If you do not want to set up your own hosting - you MAY use the hosting I have set up already by setting your website URL in the menus to https://inco.virtualportal.space. You are welcome to use this - but it comes with no promises, so it's up to you.
If you wish to use this project then please read the full README as it explains how to build the item you need to drop the scripts in. Alternatively I plan to shortly make available "pre-build" versions in a new store I am putting in Sub-Version Mall.
These scripts are open source, please do not try and "close source" them by claiming them as your own and trying to stop others using them.
Additional Revisions:
As this product is suitable for multiple target audiences, it may be of interest to daycare simulations. There is nothing sexual about this whole system - it's just a simulation. With this in mind and in particular thinking of daycare centres, I have made a variation of this project called "HappyBumsPlus" which also includes messing. While this has no interest for me - its a small change (well a lot of changes - but easy) to add and I may as well make it suitable for this use too. This could actually significantly add to any daycare roleplay with multiple diaper wearers (either young or adult).
This is implimented as a SEPARATE ALTERNATIVE product though - so those who do not even want to SEE the option for messing can just use the standard HappyBums attachment and those that want the "full experience" can use the HappyBumsPlus attachment. The website works the same for both but looks to see if messing is enabled for the wearer - and if so will display that status too and a couple more options (Mess and change Auto Mess timer). For wearers using the "classic" HappyBums version - owners will simply not see those options when connecting to them.
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.
I do not plan to integrate this into osCollar. Two reasons: One, osCollar seems to have several versions floating around and I have no interest in supporting multiple systems. Two, I likely do not have the skillset for that - the one doing all the coading here is Claude.ai - while it could probably work it out - it would take forever (with free access) to do that. I DO plan to intigrate an RLV Relay into this though - so I think between that and what I have implimented most "useful" features are already added apart from things like leashes etc. There is no reason you cant wear a collar too however if you want leashes and other tools like that.
Added by: Glenys Bieler✦
Last Update: 3 days ago
Project Category: Attachments
Code
| File name | Added By | Last Updated | Actions |
|---|---|---|---|
| HappyBums / HappyBumsPlus Architecture | Glenys Bieler✦ | 3 days ago | View |
| HappyBums / HappyBumsPlus Menu Structure | Glenys Bieler✦ | 3 days ago | View |
| happybums.php | Glenys Bieler✦ | 3 days ago | View |
| happybums_cleanup.php | Glenys Bieler✦ | 3 days ago | View |
| README - HappyBums | Glenys Bieler✦ | 3 days ago | View |
| README - HappyBumsPlus | Glenys Bieler✦ | 3 days ago | View |
| [HappyBumsPlus] Core v4.3 | Glenys Bieler✦ | 3 days ago | View |
| [HappyBumsPlus] Persistence v4.3 | Glenys Bieler✦ | 3 days ago | View |
| [HappyBumsPlus] WebRelay v1.2 | Glenys Bieler✦ | 3 days ago | View |
| [HappyBums] Core v4.2 | Glenys Bieler✦ | 3 days ago | View |
| [HappyBums] HoverText v1.1 | Glenys Bieler✦ | 3 days ago | View |
| [HappyBums] Persistence v4.2 | Glenys Bieler✦ | 3 days ago | View |
| [HappyBums] WebRelay v1.1 | Glenys Bieler✦ | 3 days ago | View |
Comments
If you are putting this together yourself from the supplied scripts - the HappyBums scripts and the HappyBumsPlus scripts are clearly named - the Core, Persistence and WebRelay go in the root prim of the main attachment (only the versions for the one you are building - so EITHER HappyBums or HappyBumsPlus).
Anyone hosting the web package - is of course free to use whatever logos they want - change this as much as you like. However, feel free to copy/download the logo at the top of this project.
Alternatively - shortly you will be able to pick up the HappyBums and HappyBums attachments (together with the optional hovertext attachment) from a new store in Sub-Version Mall.
This is a "complete" release now - with the full Attachment, optional Hovertext attachment, and web based control system. Please see the README file.
All functions are now working (although I expect there are still bugs to be worked out).
I plan to make a full copy version of this system available for free in a store on Sub-Version Mall shortly - but the scripts and guide will always be available free from the script library here on OpenSimWorld.
Please feel free to report any bugs or suggestions - but no support is "provided" with this.
A lot of RLV changes - and now all the RLV features should be all working (still intend to add an RLV Relay later)
Additionally a second wearable has been added to the project - this is a 2 prim linkset that is worn on skull and displays hover text of the status. This is NEVER locked down by RLV so wearing this or not is totally up to the wearer at all times even if their owner has enabled it. This displays the current status of the wearer in colours ranging from green (dry) to dark red (leaking).
Please see the main post for complete list of features. Next up is the web based control. The web interface is nearly complete but there will need to be a new http in script to listen to commands from the website and process them.
* Initial RLV integration completed.
* The wearer can add an Owner (max 6 owners in total). Once the first owner has been added - the wearer can no longer add or remove any owners - only owners can.
* The initial owner can add or remove additional owners (and remove themselves).
* The owner can lock the hud so the wearer cannot remove it (this currently does NOT relog on login - so this is work in progress)
* The owner can lock diaper changes to only owner, or owner+wearer, or leave open to all who have access
* The wearer can SAFEWORD which will remove all restrictions AND wipe the owner list.
* Refactored all the menus to make it cleaner and more organised.
* Adds a new "Change Announcement" so this can be set to Owner IM so it does not display to everyone (also checks minimum region rating before announcing to everyone / local
* Minor changes to setting auto-wet to 0 (no longer goes into negative numbers but correctly displays "Disabled".
* Access mode: switch between open/lists and owner only.
* Added minimum region maturity so it wont do local chat if lower maturity than set.
* Fixed hypergrid reset issues (I think!).
* Added ability to add/delete from whitelist or blacklist and view contents. Current access is owner (and until RLV implimented wearer counts as owner), and any third party. If a whitelist has entries (in UUID form) then anyone NOT in the whitelist is denied access (in this case blacklist is never consulted). If whitelist is empty, and blacklist has entries then all third party access is allowed UNLESS they are in the blacklist. This will change in the next version - as I will be adding an "access mode" that allows switching between the access mode above - and owner (and wearer before RLV) only.
* Added the ability to change the "State Names" (from the default Dry, Damp, Wet, Soaking, Leaking).
* Added an option to "reset to default settings" (this needs additional testing as I think sometimes this may sometimes get called - at least in part - when returning from hypergrid jumps. Some of the "status" may be reset.
* Added an option to change the command prefix from auto generated [first name initial][last name initial]diaper to anything you want, and to reset it to autto generated default by entering "auto".
JUST noticed that I misread Harper's suggestion. The solution I have put in place only looks at the maturity of the region - nothing to do with the origin grid. My bad on reading there! However, I personally think this is a better change as you can set it (for example) to only do local chat on Adult regions (you can choose ANY maturity) and then if you hypergrid somewhere (and re-wear or reset to get scripts working - assuming scripts are enabled there) the hud will still function perfectly well - it just wont announce anything in local chat. This means that you can still do any roleplay with it between yourself and an owner if you wish - and noone else need know anything is going on.
This may not be a particularly eligant way to store persistence - it is the most reliable. Reading from note cards is fine - but that cant store live status. To do so requires writing TO notecards and that requires ossl that may not be enabled - or at least not enabled for "most users" so while I can use that for myself - it may not be useful to anyone else.
Currently 7 or 8 of the linked prims are used for this storage - with the remaining 2 there to store items related to RLV in future. This SHOULD mean that if you are wearing this system and hypergrid, it may or may not WORK on the destination grid, but when you come home it definately will carry on from where it was when you left as it just reads from the description field of the linked prims. It does of course make it high LI but I dont think anyone should really have a problem with an 11 prim attachment these days.
With that in mind, I aim for forward compatibility in any code I create but also have an understanding that the intention, while good, can still fall flat in some areas. Cheers =D