I fully understand.Ġ: no universal “supposed to do” process 1a: no 1b: yes, usually 2a+b: update former to next version – prob 2b, else/big version jump – 2a 3: in theory no limit, okay analogy actually (P.S. We are not all socially inept zoomers and millens. I don’t want to get into a long-running game and shoot myself in the foot by losing all progress by making a dumb rookie mistake.Īpology accepted. I would appreciate any suggestions from users or moderators. If it is fine to “patch” instead of fully replace, is there a functional limit to HOW MANY TIMES patching can be expected to work perfectly before the risk of errors starts to increase and replacing the whole dang thing is a better option? Probably a bad analogy, but if a pipe starts to spring leaks you can patch with duct tape a few times, but at some point you are better off replacing the pipe. Is it always OK to DL the smaller PATCH file because there are never any problems with patching and I can safely assume that everything will recognize what it’s a-supposed to recognize and be fully compatible without fear of errors such as lost saves, etc.?ģ.

Is it better to DL the FULL NEW version – whenever host limits allow – because all changes are seamlessly pre-integrated by the dev in that big file?Ģb. Am I supposed to COPY/REPLACE the new files into the existing folder containing the previous version is (overwriting some existing files like you do with many mods & other patches)?Ģa. Am I supposed to always leave the update patch as a STANDALONE FOLDER and start play from there?ġb. Is there a universal “you’re supposed to do this” with Update Patches? (I have not seen guidance/instructions for updates like there always is for other add-ons like mods, incest patches, etc., and there is nothing in the FAQ.)ġa.

Revenga walkthrough