- May 12, 2018
- 432
- 369
If you go to the MadScience event and follow the path all the way to the end, you should see something like this. Modify the circle I'm pointing to by double-clicking it, it should have a minimum and maximum value, the minimum is least days possible while maximum is most it'll take. If you did a Mad Science and then updated the file it might not trigger immediately, and I don't know if you can force it to do it twice, but I have mine set to 5-7 so I can do it every week.how I reduce the days before I can corrupt the town, I set everything related to days to zero but still no activation of the event ?
I should also note that for anyone who wants to 'really cheat' (like "break the game completely" cheat), there are debug events available in your bedroom (location events, "your bedroom", and then the Btn_Test ones), and if you open either Arousal or Inhibition you can double click certain spots to add different stats to the debug setting. Check the box "Enable Debug Events" at the top of the debug window and the next time you go to your bedroom you'll see new buttons in the room. This is good because if you want to modify everyone's stats, any stat you want high you add to Arousal event (since arousal = sexy, so stuff like charisma or corruption), and anything you want low you can put in Inhibition's event (grunge mostly).
See attached snip for the Arousal event and what you need to double click to modify to add variables (red circles), the circles that relate to those variables (red line into arrow), which you'll need to know because when you add a variable you need to then point BACK to that circle (black arrow near top, pointing from "Appearance" to the respective circle). You'll need to do this for all 3 sections if I remember right. Press the button in the bedroom, set it to one of the numbers given, and everyone in the game will have those stats set to that number.
*save before doing these just in case/make a new save, if I remember right these should be fine but especially with the actual debug events that can cause issues.