13:04:45.291 CHAR_DEBUG - SAVE
13:04:45.291 player null (dpnid = -1)
13:04:45.291 Identity: playerID = -1 , charID = -1
13:04:45.291 Person : playerID = 534 , charID = 534
13:04:45.291 CHAR_DEBUG - EXIT
13:04:45.291 player null (dpnid = -1)
13:04:45.291 Person : playerID = 534 , charID = 534
13:04:45.291 [Disconnect]: Finish script disconnect -1
13:04:46.421 Client: Nonnetwork object 18147760.
13:04:46.424 !!! [CE][offlineDB] :: Can't save player: database disk image is malformed
13:04:46.425 !!! [CE][offlineDB] :: Can't save player: database disk image is malformed
13:04:46.425 !!! [CE][offlineDB] :: Can't save player: database disk image is malformed
13:04:46.436 !!! [CE][offlineDB] :: Can't save player: database disk image is malformed
13:04:46.437 !!! [CE][offlineDB] :: Can't save player: database disk image is malformed
13:04:46.440 !!! [CE][offlineDB] :: Can't save player: database disk image is malformed
13:04:46.443 !!! [CE][offlineDB] :: Can't save player: database disk image is malformed
13:04:46.451 !!! [CE][offlineDB] :: Can't save player: database disk image is malformed
13:04:46.452 !!! [CE][offlineDB] :: Can't save player: database disk image is malformed
13:04:46.453 !!! [CE][offlineDB] :: Can't save player: database disk image is malformed
Description
Description
Details
Details
- Severity
- Major
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 7
- Category
- General
Event Timeline
Comment Actions
Hello Brasil-Team.
Can you please provide more info in regards to this?
Regards,
Geez
Comment Actions
SQL database does not save player progress, frequent errors are appearing on ( PS4 Pro ) performance loss as will be shown in images below
Comment Actions
Hello Brasil-Team.
The error occurs due to the file containing player database is corrupted (the error message can also pop up when disk itself is not responding correctly in rare occasions).
This is most likely due to manually editting the data in the database file. Only way to fix this now is to completely delete the database file, or revert the server storage to previous point where this did not occur.
Regards,
Geez