![]() My PC parts have finally arrived, and I’ll put the final rig together this weekend when I feel a bit better from this cold I got yesterday – I have a nasty fever. THIS is the creator of being a dik words on patreon: – Fixed an issue with the fast travel map in the final free roam event – Fixed a variable regarding a dialogue with Derek – Fixed a pet name issue. – Fixed an issue with a missing image during a Quinn scene – Fixed an issue with Rusty’s Bios that said the opposite of what was expected with the mansion mini-game. – Fixed an issue where you couldn’t win the body shot competition with Becky. – Fixed an issue with Rooster that incorrectly indicated that a new cluck was available after a Josy and Maya event. – Hid the quick menu during the Party Planner mini-game. – Fixed an issue where the MC name in the scene gallery wasn’t updated to use your MC name. If your save file have duplicates of any Bios, I’d recommend restarting that save file from the Import screen of Season 3 again. – Fixed a game breaking issue where importing multiple saves during one game caused duplicated entries of lists such as Contacts and Bios. If your save file has this issue, restart from episode 9 to fix it. If I had the ability, I'd ban you from ever touching one of my games, given your obvious lack of respect for the people who create them.V0.9.1 – Fixed a game breaking issue with Neil’s chat that caused the replies to be out of sync with Neil and MC. What's not right is getting up on a high horse and throwing around personal insults because someone's vision of how their work should be made doesn't exactly match your own preferences. Will it stop some people? Sure, but that's their right. Will I be annoyed if I can't roll back to read something I missed? Sure. And what about minigames? Rollback could completely confuse any programming related to that.Įven without thinking of all the technical reasons, I think 'artistic vision' is a good enough reason all on its own. There are also scenes with lots of animations that could get destroyed by rollback. My first thought is certain persistent variables that could get really messed up by rollback. There's plenty of legit reasons to disable things like this. ![]() That means players can still roll back to read anything they might have accidentally clicked past, but can't use that to change choices. However, if you really do want to keep the players from using rollback to change choices, then it's best to use the first option. ![]() Like someone else mentioned, most players are going to abuse saves to get around disabled rollback anyway. Unless you have a really good reason to disable it (like a persistent variable that would mess up really badly if a player rolled over it), then it's best to leave it as-is. Very important to note that most players expect rollback. You could also disable rollback entirely by putting the code define config.rollback_enabled = False at the top of your script. You can also allow rollback, but block players from rolling back past menus. To do that, use something like the example here. The one I recommend the most is setting it so the players can roll back, but can't change choices during rollback. There area a few ways that you can do this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |