Dev Update - 06/24/2025
Good Day Everyone!!
I want to start off by apologizing again for yesterday! My poor planning led to me not meeting my goal of providing you with an update on my progress. I hope that I can make it up to you today!
To kick off the update I want to talk about the changes to the Main Screen.
Text will now show properly in the Text Box on the main screen. There are still a couple of things that need to be implemented for this, but most of the Text is being properly displayed.
You may notice that the Merits Counter, Clock, Timer, and Reset Button have been moved to the bottom, below the Progress Bar. This was done in an effort to clean up the UI, and present the information in a streamlined fashion.
The Ask Permission, Confess, and Report options in the Communication menu have been implemented, however some of the logic is still a work in progress to ensure that everything is working correctly.
The Report Clothing Menu is working correctly, and allows for Adding Clothing, Removing Clothing, Marking Clothing as Worn, Deleting Clothing, Editing Clothing, and Marking Yourself as Naked. Additionally, there is a quality of life change that I made (in my opinion) that will show what Cloth Type an item belongs to when in the "You are wearing:" list on the left side of the screen. There is however, an issue that causes it to attempt to add the item twice, which results in an error message when adding a new clothing item. The error message is something that I implemented to prevent items with the same name from being added to the same Cloth Type. This issue does not occur when Editing Items, which means that it is an issue with the logic that adds the item to the "Clothes Available:" list. I am working on resolving this. The Add Type option is working as well, to allow for adding custom Cloth Types.
Next up is the Assignments Window. This page has under gone a small redesign, primarily with it showing you a color coded section next to each assignment that tells you if the Assignment is a Job or a Punishment. Other than that the Deadlines are being correctly calculated from the .ini scripts, and the Severity for Punishments being correctly calculated with the formula. Additionally, they are correctly pulling the ValueUnit settings from the punishments to ensure that they are being tracked properly according to the Clock.
The Rules menu is properly loading the Rules from the .ini scripts and displaying them in the menu so that you can see what rules must be followed. This functions the same as the original app.
The About page is properly loading the information about the script to display the name of the .ini file, the Version (pulled from the Version= value from the .ini script), and the Path to the script on your drive.
I will be posting more information in a separate message due to Character Limits in Discord Threads. This information will be more like bulleted points on how certain systems work, and what is next.
More Information
Clock
- The clock will display time in the AM/PM format.
- The app uses an Internal Clock to keep track of time and allow for modifying time using the Test Menu.
- The app pulls the System Time from your computer upon the first time a script is loaded, and then sets that as the time on the Internal Clock.
- The Internal Clock and System Time are saved to as session.cdt file upon closing the application. Upon opening the application, it will check the System Time on your computer against the Last System Time from when the application was closed previously and will calculate the time between those two dates and times and add that difference to the Internal Clock, allowing for time to have passed in the app as well. This is used to Punish the user for not checking in when they should have, or to assign jobs that were missed during that time.
Timer
- The Timer pulls the SignInInterval value from the .ini Script for the Status that you are in, and uses that as the time for the Timer to countdown from.
- The Timer will countdown from the SignInInterval (30 Minutes in my test), and once it reaches 00:00:00 the text will change to a red color, and will begin counting up, showing you how far beyond the SignInInterval you are.
- Punishments and De-Merits are still a work in progress, but should be coming soon.
Debugging
- I have added a debug_output.log file that will generate when the application runs and will show what was loaded, whether it was the first time the script was ran, how large the loaded script was in bytes, whether the file exists, and what information was loaded from the script. This can help me to identify if the issue is with the script itself as opposed to being with the program.
- I have also added a crash.log file that will generate if the application crashes while running. This will show the stacktrace for the application and allow for me to see exactly what the application was doing at the time that it crashed, so that I can identify what went wrong with it. Unfortunately (or fortunately ♂) I don't have an example of it to show you at the moment, however I will provide an example if a situation comes up where one is generated during testing.
- There is a session.cdt file that stores the information from the program including Active Jobs, Active Flags, Deadlines for Jobs and Punishments, Active Punishments, the Internal Clock date and time, the Last Clothing Instructions, Last Instructions, Last System Time, current Merits, Script Path, and last Status. This can help me identify if the data that is being loaded is in a manner that the application can't work with, but the main two methods for debugging issues will be with the crash.log and debug_output.log.
Permissions
- Punishments that have the Forbid= value in them will correctly prevent the user from asking for a Permission that the Punishment forbids (e.g. No Hot Showers).
- I have to make changes to the current system for asking the Permissions as currently they simply grant the permission as opposed to using any logic to determine if the user is allowed to be granted the permission.
Assignments
- The Assignments window correctly determines the Deadline based on the EndTime= value.
- Assignments that do not have an EndTime= value will be assigned a deadline of 11:59:59 on the day that the assignment was assigned.
- Assignments in the list will be shown as either a Job or Punishment in the Type column with both text and with a color coded system (Green for Jobs, and Red for Punishments). My potential plan for this later on will be to possibly allow for adding other types of categories by possibly adding a Category= value to the scripts allowing for categories such as Chore, Humiliation, Personal Care, etc.
Rules
- Rules are correctly loading into the correct menu (e.g. Rules -> Permissions will show all [permission-*] sections in the .ini Script.
- Currently all Rules are listed in lower case, however I will be implementing a change to ensure that the first letter of the Rule is capitalized.
Ask for Clothing Instructions
- Currently it only loads the [Clothing-*] sections into the dropdown to allow for asking for clothing instructions for specific situations, but will not provide clothing instructions.
- Clothing Instructions will be one of the next sections that I work to implement, but it may take a little time due to how in depth the system is intertwined with other systems.
List and Delete Assignments
- Correctly shows all Jobs and Punishments that have been assigned
- Displays the Deadlines for each
- Shows in parenthesis if the assignment is a Job or Punishment
- Now allows for selecting multiple Jobs or Punishments and Deleting all selected at once.
Set Flags
- I added the ability to see all available flags for the script, and check a box next to each that you want to apply. This is an improvement over the old program where you had to know the name of the flag and type it into an input box in order to apply it.
List and Remove Flags
- Added the ability to select multiple flags that you want to remove and then remove all of the selected flags at the same time, as opposed to removing them one at a time.
Things to Implement
- Make a Report
- Ask for Punishment
- Ask for Other Instructions
- Clothing Instructions and Tracking
- Import and Exporting Clothing
- Always Permit & Deny
- Quick Popups
- Popups
- Randomize
- Ignore Remind Punishments
- Pop-up Launch
- First Run Questions
- Report, Confess, and Permissions logic
- Punishments for failing to Check In on time
- Detention
- Writing Lines
As always, I thank everyone for their support and patience on this, and I promise to have another update for you much sooner than this one occurred! I apologize for the delay! ♂
If you wish to support the Project, then you can do so over at my
