[gingerbread]

@aldostools

Found a major bug. The are cheat files are fine on my backup folder and look fine when I open them in notepad. I use BSD to DL them, they get messed up, the cheat files get messed up. All the text in the patch file are in single line.

Edit: Nope, it is one my github end.
************* [ - Post Merged - ] *************
@aldostools Ignore my last PM. Manage to get it working. I had to change the github CRLF settings.

[aldostools]

Originally Posted by haxxxen @aldostools i have noticed some minor bug. if you select decrypt pfd->selected file on a single file, you are not able to decrypt any other files if there are more. can you change this by any chance? also the cheat files from git are encoded in unix standard. they should be encoded in dos\windows to make them work with bsd

The decrypt pfd button is disabled intentionally to prevent accidental double decryption.

if you need to decrypt more than one file, select "decrypt all files" or mark multiple files pressing Ctrl + click, then use "decrypt selected files".

if you already decrypted one file and need another file decrypted, encrypt back the file already decrypted, then select decrypt all files or use decrypt selected files as explained above.

The line break issue is now fixed in the github and in the build 3.2 too.

Among the features of BSD 3.2 are:
- Added support to upload selected saves to the PS3 via FTP (multiMAN)
- Added new "Encrypt Decrypted Files" as default encrypt option: the program stores which files were decrypted in "~files_decrypted_by_pfdtool.txt" and select these files for encryption. The old options are still there.
- The program detects the type of line break in the ps3savepatch and convert it to CRLF (DOS/Windows format).
- Bug fix: Double click on a decrypted save now asks to encrypt it (instead of rebuild it)
- Bug fix: the (blue) Rebuild button is now hidden when a save is decrypted.
- Added the version 0.5 of the ps3savepatch database to the installer
- The installer now asks if the user wants to replace the files in local database of save patches.

[haxxxen]

i think i have now understood the search code type as described at crunch. i will use the example from darkness 2


8001000C 4861734E
65774761 6D65506C
08000013 00000031

8001000C <- search code type with an occurance of 1x and a search pattern of length 0xC bytes
4861734E <- search pattern
65774761 <- search pattern
6D65506C <- search pattern
08000013 <- patch offset is 0x8 bytes from last search pattern with a length of 0x13 bytes to skip (1st search pattern upto the patch offset)
00000031 <- value to patch

@aldostools
is it possible to implement such function?

[aldostools]

Originally Posted by haxxxen i think i have now understood the search code type as described at crunch. i will use the example from darkness 2 8001000C 4861734E 65774761 6D65506C 08000013 00000031 8001000C <- search code type with an occurance of 1x and a search pattern of length 0xC bytes 4861734E <- search pattern 65774761 <- search pattern 6D65506C <- search pattern 08000013 <- patch offset is 0x8 bytes from last search pattern with a length of 0x13 bytes to skip (1st search pattern upto the patch offset) 00000031 <- value to patch @aldostools is it possible to implement such function?

It is already implemented since build 3.0

[haxxxen]

oh, now thats embarrassing. sorry for my stupidity

@aldostools
but it does not include md5 correcting as i can see it now. darkness 2 has a md5 checksum at beginning of both save files. but this has to be checked on every save file if there are checksums

edit
if i try to apply the cheat to bles version it does not work for me

[aldostools]

Originally Posted by haxxxen but it does not include md5 correcting as i can see it now. darkness 2 has a md5 checksum at beginning of both save files. but this has to be checked on every save file if there are checksums

Could you offer more details about that? I can calculate MD5 easily if you give me the technical specifications on what should be done.
Example files would be appreciated too.

[haxxxen]

here is a picture to make it easier. above SETTINGS file is original, bottom is patched with gamegenie. it is a md5 checksum made from offset 0x10-end of file

this is the cheat i want apply, but bsd does not patch:

;The Darkness II

;BLES01388

;From Game Genie For PS3

:SETTINGS

[Unlock New Game+]
8001000C 4861734E
65774761 6D65506C
08000013 00000031

:CONTINUE.SAV

here are both save files and the patch. original and patched with gamegenie:
http://rghost.net/43969964

edit
to correct my mistake from above
8001000C <- search code type with an occurance of 1x and a search pattern of length 0xC bytes
4861734E <- 1st search pattern
65774761 <- 2nd search pattern
6D65506C <- 3rd search pattern
08000013 <- skip length of 0x13 bytes from 1st search offset
00000031 <- 8bit value to write

but this is confusing:
80010003 C0FFEE00 search C0FFEE occurence=1x length=0x3byte
93000000 00000180 step back? 16bit length=0x180byte from search offset
28000000 000F423F write 32bit value at new offset directly/no skip

[aldostools]

Originally Posted by haxxxen here is a picture to make it easier. above SETTINGS file is original, bottom is patched with gamegenie. it is a md5 checksum made from offset 0x10-end of file edit i would need another gamesave to look at. this is confusing

I have updated the program to build 3.2.3

I have added some new cheats commands:

set md5: 00000000 <- writes md5 as binary @ address
set md4: 00000000 <- writes md4 as binary @ address
set md2: 00000000 <- writes md2 as binary @ address

** if address is 0, hash is calculated starting from offset 0x0010 to end of file.
** if address > 0, hash is calculated starting from 0 to end of file - 0x0010

set sha1: 00000000 <- writes sha1 as binary @ address

** if address is 0, hash is calculated starting from offset 0x0014 to end of file.
** if address > 0, hash is calculated starting from 0 to end of file - 0x0014

set crc32: 00000000 <- writes crc32 as binary @ address

** if address is 0, hash is calculated starting from offset 0x0004 to end of file.
** if address > 0, hash is calculated starting from 0 to end of file - 0x0004

set psid: 00000000 <- writes psid as binary @ address
set userid: 00000000 <- writes userid as binary @ address
set titleid: 00000000 <- writes titleid as binary @ address
set np_account: 00000000 <- writes np_account as binary @ address
set profile: 00000000 <- writes np_account as text @ address
set "text": 00000000 <- writes text @ address

Your example would be:

;The Darkness II

;BLES01388

;From Game Genie For PS3

:SETTINGS

[Unlock New Game+]
8001000C 4861734E
65774761 6D65506C
08000013 00000031

;write md5 checksum at 0x00000
set md5: 00000000

I also fixed a bug getting the file size when the file was already open.

[gingerbread]

@aldostools FTP feature is really cool!!

There are some unknowns.

When I click "Download Save from PS3 via FTP" nothing happens.
There should be a setting where users could set on which ACC to Download from. "0000000X\savedata"
Also, there should be a setting where users could set on which ACC to Upload to. "0000000X\savedata"

Thanks Aldo!!

[gingerbread]

@aldostools Just tried you latest DL.

I created a folder in Desktop. I point BSD to that folder. When I click "Download Save from PS3 via FTP" it show "User ID not available."