Confirm the prompt to safely push data onto the encrypted server and write down the generated .
In many modern Ren'Py builds, the "This save was created on a different device" text acts as a .
It warns you that loading the file might cause crashes if the game versions do not match exactly.
When you see the message it is due to a security feature in Ren'Py 8.1+ called the Save Token Security system . This system flags saves moved between computers to prevent potentially malicious files from harming your device. How to Fix the "Save Created on Different Device" Error
The warning message " This save was created on a different device a built-in security feature of the Ren'Py engine
Copy the entire saves folder. Do just copy individual .save files.
Open your project's screens.rpy and ensure your confirm screen accepts and correctly loops through unknown warning arguments. Make sure your screen handles strings like gui.UNKNOWN_TOKEN and gui.TRUST_TOKEN natively so users can click "Yes" and proceed to load their transferred files. Method 3: Manually Linking Local Saves (For Players)
In most modern Ren'Py games, you should see a prompt asking if you trust the device the save was created on.
Renpy This Save Was Created On A Different Device Link -
Confirm the prompt to safely push data onto the encrypted server and write down the generated .
In many modern Ren'Py builds, the "This save was created on a different device" text acts as a .
It warns you that loading the file might cause crashes if the game versions do not match exactly. renpy this save was created on a different device link
When you see the message it is due to a security feature in Ren'Py 8.1+ called the Save Token Security system . This system flags saves moved between computers to prevent potentially malicious files from harming your device. How to Fix the "Save Created on Different Device" Error
The warning message " This save was created on a different device a built-in security feature of the Ren'Py engine Confirm the prompt to safely push data onto
Copy the entire saves folder. Do just copy individual .save files.
Open your project's screens.rpy and ensure your confirm screen accepts and correctly loops through unknown warning arguments. Make sure your screen handles strings like gui.UNKNOWN_TOKEN and gui.TRUST_TOKEN natively so users can click "Yes" and proceed to load their transferred files. Method 3: Manually Linking Local Saves (For Players) When you see the message it is due
In most modern Ren'Py games, you should see a prompt asking if you trust the device the save was created on.
This could have to do with the pathing policy as well. The default SATP rule is likely going to be using MRU (most recently used) pathing policy for new devices, which only uses one of the available paths. Ideally they would be using Round Robin, which has an IOPs limit setting. That setting is 1000 by default I believe (would need to double check that), meaning that it sends 1000 IOPs down path 1, then 1000 IOPs down path 2, etc. That’s why the pathing policy could be at play.
To your question, having one path down is causing this logging to occur. Yes, it’s total possible if that path that went down is using MRU or RR with an IOPs limit of 1000, that when it goes down you’ll hit that 16 second HB timeout before nmp switches over to the next path.