Ahh. Right on. There's the problem. I should have seen that. Thank you.
Good morning (late morning but I stayed up way too long last night). I can't really recommend this approach for two main reasons out of several:Hard to Love [v0.03] Multi-Mod [Sancho1969]
For
Hard to Love [v0.03] [Qori Gaming] Compressed by CRAZY X WIZARD
Note - this version of the mod only works with CRAZY X WIZARD compression - Hard to Love [v0.03] Q80 Compressed
Original Mod - Hard to Love [v0.03] Multi-Mod [Sancho1969]
Like my posts, if you like my Compressions and Mods
Can you test this
Sure, give me a bit after I get breakfast sorted. FYI, as a compressor you don't have to repack it honestly. You can do that if you wish (you will always have to make sure you have the correct version of RenPy for the VN specifically though which can be a pain in the arse). An alternate way is to simply remove all the loose scripts (rpy & rpyc) and copy/paste the original rpa files (that aren't related to images/animations of course). The latter is easier since you can't bork it except if you don't know where all the loose script files are. The latter is also what most of the compressors are doing to make their jobs easier and less prone to fubar/borked releases.Make sense?
P.S. Remember (of course) some devs don't archive properly or at all. Those that don't have have loose code scripts in their original packaging then none of what I said matters. We all have to deal with that as it is... which is there's nothing we can do about it. The issue always centers around most proper VN's that have packaged (archived) content.
That's not the worst guide. FAP does good work the majority of the time, I know him well. Personally (it doesn't matter, it's just habit) in step one I don't dig inside the "script_version" but I actually fire up the game once virgin from the dev, it produces a "log.txt" file automatically, inside that log file has almost all the info you need. Again, it's not right or wrong, it's just the way I personally work. Any insight you get from those more experienced compressors is going to help you. I know most of them personally and have worked with a few to get things were we all can live in harmony. It's a bit of a pain in the ass for all of us involved but at the end of the day the reason we do it this way is to insure it's as efficient and painless for the end user as possible... as they are the only point of doing any of this to begin with.
Indeed. There's a full legend in the OP if needed bud. "Player's choice" is my way of saying no stat or event variables are altered but dialogue is obviously impacted, possibly throughout the story. Regards.
You're on the right track... you just got off into the ditch a bit. Change what you had to this:I really hate to "click" or have to "press enter" every screen so I even dug around a script to set an auto forward for me when a game doesn't have one. It works good but I don't really know how to "set a speed" so to speak on it.
I know I'm pushing a little here but is it possible for you to tell me how to set a changeable value on the script so I can finally find a suitable "speed" for my reading?
You are the best buddy, sorry to bug you on this.
init 200 python: # SanchoNote: before you simply defined at the same time the VN did, now it's changed last (doesn't need to be over 200 imho)
preferences.text_cps = 25 # SanchoNote: change this number for how fast the text displays in the diabox
preferences.afm_time = 18 # SanchoNote: change this number for how fast the transition is to the next screen/scene