04-25-2017, 01:34 PM
(04-25-2017, 07:54 AM)magearden Wrote: "you will have to ask ppsspp team to fix poniter code and support double ponter codetype" - Lee4
not sure what he meant by that :/
It means the person who you asked for help didn't bother to actually understand what happens, probably has no experience with emulation.
When creating cwcheats there are basically two ways to go:
1) Code your own cheat that actually does something you want(which has no limitations, but can be time consuming when actually trying to prove that;p) and inject it using cwcheat to the game which then runs the cheat as it's own code.
Doing so is pretty much free performance wise, executes instantly and is also very compatible between real hardware and emulators.
2) Freeze some variables in memory, hoping it will always stay same and call it a cheat.
As can be guessed this is the opposite, it actually costs a lot to run easily slowing down real hardware when trying to execute it too often, it will also horribly fail if memory differs even by a tiny bit which due to imperfect emulation is fairy common.
The thing is most people can't do #1, because they are unable to learn simple programming in MIPS which is required making cheats for psp and #2 might be good enough for lots of basic cheats in many less troublesome games.
As far as I know pointer code type works fine, however pointer code type despite it's mighty name merely reads existing pointers stored at some place in game memory, then freeze some variable the game points to - meaning they will read garbage and write to wrong place when emulated game memory differs from real hardware.
PPSSPP supports all basic CWC code types(aside from the 0xB which no cheats should ever use), so multi level pointer codes are also there, but they will share exactly same problem as single level pointer or any other cheat made by method #2.
I belive some of those more complex and badly documented code types didn't behave as people who used them wanted in actual PSP plugins, honestly I have no idea if they're currently implemented following plugin code or people desires since they're useless to me, but if someone out there actually cares about those special codes and thinks some of them should be implemented differently or handle common typos/mistakes better as possibly some plugins had a better handling for users not following cwcheat standard, they should just step in and open a pull request implementing those things as desired, nothing is going to happen by itself.
Either way if all you need is HP cheat to make the game easy, here:
Code:
_S ULUS-10410
_G Phantasy Star Portable
_C0 Max HP
_L 0xE0071821 0x002A5428
_L 0x202A5428 0x0A200140
_L 0x20000500 0x3C03089D
_L 0x20000504 0x24630004
_L 0x20000508 0x507F0001
_L 0x2000050C 0xAC820020
_L 0x20000510 0x0A2A950C
_L 0x20000514 0x00401821
_C0 Max HP [Disable]
_L 0x202A5428 0x00401821
http://forums.ppsspp.org/showthread.php?tid=6594 - Custom PPSSPP Shaders!
http://forums.ppsspp.org/showthread.php?tid=3590&pid=117172#pid117172 - simple CE scripts to help creating CWCheats,
https://github.com/LunaMoo/PPSSPP_workarounds - CWCheat workarounds.
http://forums.ppsspp.org/showthread.php?tid=3590&pid=117172#pid117172 - simple CE scripts to help creating CWCheats,
https://github.com/LunaMoo/PPSSPP_workarounds - CWCheat workarounds.

