I installed the debug mod and this is what i got: 
Before installing it i was able to go through the character creator and it would freeze once it loaded the mansion, now I can't even go through the character creator, and I mean freeze in the sense that game is literally frozen, I neither get a crash error or something like that, it's more as if i'm trying to run a new gen game on my PC.
Could you also tell me what type of info you need? I could screen shot it if you want.
It appears that you clicked nearly every button on the screen before taking that image. Unfortunately this means that it scrolled the first errors off screen and the first errors are generally the most important ones. So I would need an screenshot just like this, but without all the button clicking(the added errors don't reveal anything useful) or at least scroll to the top first. Though as I will explain later, that screenshot may not help.
The Debug mod has 2 effects: the terminal that provides error messages, and the uniquely dangerous effect of causing the game to not crash when it should otherwise crash. Specifically it changes the response to errors to fail out of the current code rather than stop the entire program. There are some rare problems where the debug response is more detrimental than the default response, but even so the error messages are more important.
As far as getting better explanations from you, you have already provided some. Previously you only mentioned that you had problems loading the game, which to me means before reaching the main menu but for others it can mean any time until the mansion shows. The fact that you could reach the main menu and use any buttons eliminates a lot of annoying potential problems.
The reason you can't progress the game menus as far with the Debug mod is that your game had an error while setting up the core game data and failed out before finishing, thus the main menu cannot function because it lacks critical data. Prior to the Debug mod, you had the same error but it Godot decided not to crash for it thus allowing it to quietly corrupt part of the data, which was probably needed for the part that it did stop working. The "frozen" game state that you are referring to is actually called a softlock, as the program has not stopped responding it is not frozen. In a softlock you cannot progress but the program is still responding, or in other words it recieves user input and uses CPU time in a normal fashion. The fact that the button presses do not function as normally expected does not mean that it isn't responding.
I need you to list which mods you have installed as well as their versions, because your current problems are almost certainly caused by installing mods that cause conflicts in the game's code. Resolving conflicts between mods so that they work together is tedious work. The screenshot mentioned above will likely identify the point in the code that the conflict occurs, but I could probably tell you where it was just from the list of installed mods. Fixing a program folder with conflicting mods installed is a headache even for skilled programmers. The easiest fix is to extract a new Strive program folder and try to install a difference order or combination of mods. I have looked at the code of most of the mods so I can tell you which of them will likely be compatible.
If you have trouble remembering which mods are installed, the details.ini file in your Strive program folder will have them listed by name but not the versions.
Yeah, no surprise that you are having problems. Most of the time players can manage about 3 to 5 mods before conflicts occur. If you are very persistent and careful then you might manage 8 to 10 smaller mods. There just isn't any way that the game can possibly work with all 16 of these mods. The mod system mainly works by making text edits to the game's code by applying changes found in mod files. When two mods change the same code we call it a conflict or overlapping changes, which usually result in bugs, errors, or crashes.
The error messages consist of multiple parse errors, which happens when multiple mods change the same code thus mutilating it beyond comprehension. After a parse error, the engine fails to load the entire file, thus your game has no code to run person descriptions nor quest-line events. In debug mode, the game will fail out of the code to report a problem as soon as it tries to use these non-existent files. In normal mode, the game will tend to ignore the non-existent files until a fatal problem occurs. Some of the game's files don't load until a progress is started, so the problems in those files have not been processed yet.
Constants, randomportraits, and Quick Defeat Animation are probably the exceptions to conflicts as they mod very unique places in the game that almost never change and have very small code profiles. They are very unlikely to conflict with any other mods when applied last in the list, though they can still be harmlessly erased by mods replacing specific parts of the code.
AricsExpansion is probably the largest mod to ever be created and touches nearly every part of the game. It requires the Bugfix mod and is known to be compatible with Constants and randomportraits. It fatally conflicts with both Es-01, Es-02, MoreGenderOpions, ProtagMod, and Drake's Descriptions. It is probably conflicts with most other mods.
The Bugfix mod is probably the second largest mod on the list and touches many parts of the game though it tends not to significantly change the game mechanics. It will still conflict with any mod that attempts to mod the same code, such as the Chastity Belt mod and the ProtagMod.
The Expanded Sex mods, Es-01 and Es-02, are fairly large mods that are mostly focused on interactions. However, the current version of the Bugfix mod cleans up a lot of code related to interactions so there are some minor conflicts.
MoreGenderOpions is a relatively small mod, however it changes some rather common files. It fatally conflicts with AricsExpansion, As long as it comes after the Bugfix mod it only has harmless(some quest text will display wrong) conflicts. Changing the gender assignment can behave weirdly on characters with a chastity belt from the Es-02 mod.
The ProtagMod has leading spaces instead of tabs in spells.gd so the Domination spell will not work unless that is fixed before applying. It also harmlessly conflicts with the Bugfix mod.
Many of these mods appear to be Drake's mods, which are rather new so I'm not entirely familiar with them. They appear to be quite small thus unlikely to conflict with most mods. I don't know of any conflicts with the following: Alchemy For Dummies(will not change potions added by other mods), Perfect Trait, and Line 126. Gender Equality appears incomplete and mostly mods an unused file and though it can result in some odd descriptions it does not appear to conflict with anything; however, the increased breast size on males can result in them changing into Dickgirls with AricsExpansion.
Drake's Descriptions appears to only conflict with AricsExpansion, which will bypass most of the changes and cause a parse error for one.
Beauty Adjustment appears to only conflict with AricsExpansion, which will bypass some of the changes and erase the rest if AricsExpansion is lower in the list.
No I in Race would conflict with AricsExpansion, but some typos mean that this mod does nothing.
Combat Stress Reduction conflicts with AricsExpansion and will likely result in parse errors.
Hopefully that covers most conflicts, there are a lot of combinations to check for so I may have missed some.
