Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Can't see what i did wrong Here.
#1
I added some new codes and this is the error i get

(Patch) Error Parsing: patch=1,EE,Cheat Name: items inf
Expected 5 data parameters; only found 3

witch is odd the code worked fine before i added these

// Game Title: FF X
// Game Region: NTSC



// Start of Cheat
// Cheat Name: inf X
patch=1,EE,200FFF00,word,3C030064
patch=1,EE,200FFF04,word,8C636360
patch=1,EE,200FFF0C,word,10030008
patch=1,EE,200FFF14,word,2402270F
patch=1,EE,200FFF18,word,AC62027C
patch=1,EE,200FFF1C,word,AC620280
patch=1,EE,200FFF34,word,24030070
patch=1,EE,200FFF38,word,080B6CB6
patch=1,EE,202DB2D4,word,0803FFC0
// End of Cheat


// Start of Cheat
patch=1,EE,Cheat Name: items inf
patch=1,EE,101BECEA,word,0000A266
patch=1,EE,201BECA4,word,24020064
patch=1,EE,End of Cheat
// End of Cheat



// Start of Cheat
// Cheat Name: money
patch=1,EE,1031A028,word,0000FFFF
// End of Cheat



// Start of Cheat
// Cheat Name: tranny
patch=1,EE,20319FF0,word,03FFFFFF
// End of Cheat



// Start of Cheat
// Cheat Name:Auron Super HP
patch=1,EE,1031B9FC,word,0000270F
// End of Cheat




// Start of Cheat
// Cheat Name:Auron SuperMP
patch=1,EE,1031B9F8,word,0000270F
// End of Cheat
Reply

Sponsored links

#2
change "word" to "extended"

just edit it on notepad
MAIN RIG:i5-7600(3.5ghz)GTX 1050Ti 4GB/128bit/gddr5,Win 10 Pro(x64),ASUS ROG B250G,16GB HyperXFury ddr4 RAM,Samsung M.2-SSD 500GB
SUB RIG:i5-4670(3.4Ghz),ATi Radeon HD7770(GDDR5+128-bit+1GB),Win 10 SL(x64),ASUS H8M-E,8GB DDR3 RAM
Reply
#3
Thanks but this is what i got


Cheats found!
(Patch) Error Parsing: patch=1,EE,Cheat Name: items inf
Expected 5 data parameters; only found 3
(Patch) Error Parsing: patch=1,EE,End of Cheat
Expected 5 data parameters; only found 3
Cheats Loaded: 15
Reply
#4
(12-16-2013, 04:23 AM)treeofdeath Wrote: Thanks but this is what i got


Cheats found!
(Patch) Error Parsing: patch=1,EE,Cheat Name: items inf
Expected 5 data parameters; only found 3
(Patch) Error Parsing: patch=1,EE,End of Cheat
Expected 5 data parameters; only found 3
Cheats Loaded: 15

Take these lines out:

Code:
patch=1,EE,Cheat Name: items inf
patch=1,EE,End of Cheat
[Image: vwah44]
Gaming: Intel i7 3770k @ 4.2Ghz | R9 290 | 16GB RAM | 480GB(240GB+240GB RAID0) SSD | 3 TB HDD | 1 TB HDD | 500GB HDD
Server: AMD FX 6300 @ 4.4Ghz | GTX 670 | 16GB RAM | 240GB SSD | 320GB HDD
PCSX2 General Troubleshooting FAQ
Reply
#5
They are all comments like "// Start of Cheat".
Remove or comment out("// ...") them from the pnach file.

Also, in order to convert raw codes to pnach format, there is a handy tool PCSX2CE and read Step 6 of a guide A simplistic guide to pnach files.
Reply
#6
Still there is invalid data in there, for instance here:

// Start of Cheat
patch=1,EE,Cheat Name: items inf
patch=1,EE,101BECEA,word,0000A266
patch=1,EE,201BECA4,word,24020064
patch=1,EE,End of Cheat
// End of Cheat

Line 2 and 5 are not a valid patch lines.
[Image: vwah44]
Gaming: Intel i7 3770k @ 4.2Ghz | R9 290 | 16GB RAM | 480GB(240GB+240GB RAID0) SSD | 3 TB HDD | 1 TB HDD | 500GB HDD
Server: AMD FX 6300 @ 4.4Ghz | GTX 670 | 16GB RAM | 240GB SSD | 320GB HDD
PCSX2 General Troubleshooting FAQ
Reply
#7
Pnach cheats can make certain parts of FFX hang or freeze. I recommend you use the save editor.

http://forums.pcsx2.net/Thread-FFXED-Fin...ave-Editor
OS: Linux Mint 17.2 64 bit (occasional Antergos/Arch user)
(I am no longer a Windows user)
CPU: Intel Pentium G3258
GPU: Nvidia GTX 650 Ti



Reply
#8
Both smartstrike and Blys Sarania are right, the use of the older direct length token (byte, short and word) should be avoided from new files since after extended was implemented.

The main reason being "extended" keeps the original code format, no need to change the first digit at the address offset. On the other hand one must be careful when trying to simply changing to extended, many original codes started with 0 or 1 may have that bit changed to 2 as was the "recommended" once upon a time and proved catastrophic. You see, 0 means the value is byte length and 1 means it is short length and if changed, the token "extended" will interpret them as "word" maybe causing issues.

The worst case is using addresses starting with 1 with any the tokens byte, short or word, this will most probably crash the emulator for poking out of game's data memory area. The problem is less grave with using 0 or 2 wrongly because pnach will mirror them to the correct address starting with 2xxxxxxx.

One final advice about parsing errors. If using non English language, open the cheat file in a decent text editor and change the encode to unicode. Non ASCII characters might confuse the parser even when the line is commented, or simply remove or change lines having any non ASCII characters, like special language characters, accentuated characters and so on.

PS: and yes, in the special case of the FF games which have the save editor, it's a lot better using them as suggested by DaTank Smile
Imagination is where we are truly real
Reply
#9
(12-16-2013, 02:16 PM)nosisab Ken Keleh Wrote: Both smartstrike and Blys Sarania are right, the use of the older direct length token (byte, short and word) should be avoided from new files since after extended was implemented.

The main reason being "extended" keeps the original code format, no need to change the first digit at the address offset. On the other hand one must be careful when trying to simply changing to extended, many original codes started with 0 or 1 may have that bit changed to 2 as was the "recommended" once upon a time and proved catastrophic. You see, 0 means the value is byte length and 1 means it is short length and if changed, the token "extended" will interpret them as "word" maybe causing issues.

The worst case is using addresses starting with 1 with any the tokens byte, short or word, this will most probably crash the emulator for poking out of game's data memory area. The problem is less grave with using 0 or 2 wrongly because pnach will mirror them to the correct address starting with 2xxxxxxx.

One final advice about parsing errors. If using non English language, open the cheat file in a decent text editor and change the encode to unicode. Non ASCII characters might confuse the parser even when the line is commented, or simply remove or change lines having any non ASCII characters, like special language characters, accentuated characters and so on.

PS: and yes, in the special case of the FF games which have the save editor, it's a lot better using them as suggested by DaTank Smile

I know this is an off topic, but you seem familiar with the pnach cheating system of pcsx2.
If you know about here and could give some comments, I appreciate it.
Reply




Users browsing this thread: 1 Guest(s)