VN Ren'Py Being a DIK [v0.11.1] [DrPinkCake]

4.70 star(s) 1,732 Votes
Discussion Reviews (1,732)
A

anony66

Member
Oct 9, 2017
115
251
266
icloutshit said:
What we thinking? February 14 seems like the most likely release date no?
Click to expand...
If by "February" you mean "March", then yes. Rendering is supposed to finish next weekend, and only then the beta begins, so let's say 10.02. Somebody posted some time ago that the beta took 25 days last time, and the trend with that is the same as with dev time: it's only getting longer with every update. 25 days would put us at 07.03., which would mean release 14.03. If we are very lucky and it goes faster, 07.03. If something goes wrong, 21.03.
 
  • Like
Reactions: Gunizz, Rischard, Bubba McSmith and 2 others
Lizzardcheese

Lizzardcheese

Member
May 25, 2024
166
387
149
anony66 said:
If by "February" you mean "March", then yes. Rendering is supposed to finish next weekend, and only then the beta begins, so let's say 10.02. Somebody posted some time ago that the beta took 25 days last time, and the trend with that is the same as with dev time: it's only getting longer with every update. 25 days would put us at 07.03., which would mean release 14.03. If we are very lucky and it goes faster, 07.03. If something goes wrong, 21.03.
Click to expand...
Nicely broken down.
Also, great Sigs.
 
  • Heart
Reactions: anony66
G

grey_shadow

Member
May 21, 2022
310
362
131
ZenoMod said:
I can confirm that cheating via Console or Save Editor is not detectable unless it leads to something that would be impossible in a normal run, like setting your money to more than the maximum or being on two paths at the same time, or being on Quinn's path with a Chick affinity, and so on.

Anyway, that's not automatic. DPC would have to put in his next releases some "if" clause that check for anomalies.
Click to expand...
I can believe that that's true currently, but it would not be hard for DPC to set something up so that editing variables (via console or save edit) sets up a time bomb that he can detonate in any future release.

The simplest (and easiest to work around) would be to create a dummy variable with the sole purpose of recording the value of some flag or other long-term stable variable (like which path you choose at the end of chapter 8) and then ignore that dummy variable entirely until it's eventually checked against the actual variable, which would seem to have been changed successfully up until that check is done...

There are other tricks that can be done, depending on how much effort he wants to put in, but the basic idea remains - redundantly store multiple versions of the same information, only some copies of which are actually used for anything, and then later compare the active versions against the backups.
 
You must log in or register to reply here.
Top Bottom
4.70 star(s) 1,732 Votes