[aldostools]

Originally Posted by gingerbread @jgduff CU will not work on 4.21+ It is because it is not updated yet and the person who hacked it, is not keen to update it to 4.21+. Only time can tell. The alternative is by patching the eboot. Now for cheats for Doom BFG. There is already cheats enabled (Built-in) in the game. So you don't need CU. Here is how. Edit "joy_ps3_3.cfg" (Make sure that you make a backup.) bind "JOY_DPAD_RIGHT" "god" bind "JOY_DPAD_LEFT" "give all" bind "JOY_DPAD_UP" "give ammo" bind "JOY_DPAD_DOWN" "give keys" bind "JOY_TRIGGER1" "_impulse16" bind "JOY_TRIGGER2" "_attack" bind "JOY1" "_use" // use (A/X button) bind "JOY2" "" // (B/Circle button) bind "JOY3" "_impulse13" // reload (X/Square button) bind "JOY4" "_moveup" // jump (Y/Triangle button) bind "JOY5" "_impulse15" // weapPrev (L Shoulder) bind "JOY6" "_impulse14" // weapNext (R Shoulder) bind "JOY9" "" // Menu (Start button) bind "JOY10" "_impulse19" // PDA (Back/Select button) Edit "default.cfg" and change "set com_productionmode" value to 1 or 2. So to enable the cheats, set your controller profile to alternate 3 in the game and press the D-pad to enable the desired cheats. @bungholio @haxxxen Thanks for your information. I requested @aldostools to implement ASM tagging because bungholio mention sometime back (If i remember correctly. ) that some codes where ASM and only ASM codes can be use to patch eboot. Since Aldo, has implemented eboot patching, I believe tagging games would be the next step as users will know which codes can be patch to eboot. And that tag feature is not being used yet. haxxxen, almost every game in the database has codes start with "00002000". And tagging every title is not a efficient way. Why not do it this way? There are also "00001000", "00004XXX" . Are they pointer or memory? @aldostools Why not remove the ASM tag feature. No tagging is needed. We can do it automatically. You have implemented tool tip for the codes. When user mouse over the codes, a tool tip appears. Which is cool! Will it be possible to add a text in the Tool Tip box in the bottom. If the code contains : 0000C00X -> Joker Commands (Works only with CU) 00003000 -> Pointer Code (Works only with CU) 00002000 Only -> Memory Code (Works either as EBOOT hack or with CU)

@gingerbread
Check the version 2.5.0... it has implemented the visual tagging

red icon -> CU only
blue icon -> either EBOOT hack/CU

the tool tip shows the labels: Joker Command/Pointer Code as comments
As "Memory Code" is the default, I didn't add it as comment to keep the tool tip as clean as possible.

A red title is used on the tool tip for CU only codes.
A pale yellow title is used for the normal EBOOT hack/CU codes.

[haxxxen]

now this is godspeed

thanks aldostools for your new additions. this app has evolved to a very advanced level i think, when i look on the very first release, where it has messed up things.

now someone make 4.x version codeunique open source please
these fokkers could have made their first dongle compatible, as i own it, but no, they are greedy once again

[gingerbread]

@aldostools Thanks for the cool update!! So you have removed the ASM tag feature?

I notice some bugs.

1. In the Tool Tip, the red header text is cut off at the second line.
2. The red tool tip is shown even on blue icons.
3. When the code is large, the tool tip is cut off at the 7th or 8th line.
4. For "00000000 00000000 00000000" will it be possible to use black icon like the text and use black header in the tool tip. For the name, instead of "Other Code", "Dummy Code" seems more appropriate.

Thanks Aldo!

[aldostools]

Originally Posted by gingerbread @aldostools Thanks for the cool update!! So you have removed the ASM tag feature? I notice some bugs. 1. In the Tool Tip, the red header text is cut off at the second line. 2. The red tool tip is shown even on blue icons. 3. When the code is large, the tool tip is cut off at the 7th or 8th line. 4. For "00000000 00000000 00000000" will it be possible to use black icon like the text and use black header in the tool tip. For the name, instead of "Other Code", "Dummy Code" seems more appropriate. Thanks Aldo!

1. There is not supposed to be a second line... maybe it's the font size of your Windows theme. Here it looks fine. Send me a pic and I'll try to fix it after I get some sleep.
2. Yes, it was a bug... I already fixed it (I think so)... please, download it again and report any additional bug.
3. The tool tip is not intended to show the full code... double click on the cheat or press enter to read the full code.
4. It shows a red icon, because it is CU Only. Well it's "Other Code" too :P

I will change it for a proper label when you find also what are the meaning of the codes "00001000" and "00004XXX"

[haxxxen]

i have already posted it, but i can say it once again. maybe they do not believe in me or just ignoring?

anyways, 00001000 is a 8bit write code and 0000400X is a condensed codetype, which has several lines of code summarized to one line. for example if you have several characters in a beatem up and their codes do lie next to each other in address, you can make it condensed to only have one line of code for this

8bit writing will be used on small values that only go upto 65536 max

[gingerbread]

Originally Posted by aldostools 1. There is not supposed to be a second line... maybe it's the font size of your Windows theme. Here it looks fine. Send me a pic and I'll try to fix it after I get some sleep. 2. Yes, it was a bug... I already fixed it (I think so)... please, download it again and report any additional bug. 3. The tool tip is not intended to show the full code... double click on the cheat or press enter to read the full code. 4. It shows a red icon, because it is CU Only. Well it's "Other Code" too :P I will change it for a proper label when you find also what are the meaning of the codes "00001000" and "00004XXX"

@aldostools

Here is the screen shot of the tool tip line error.



Thanks for the fix!

@haxxxen Maybe Aldo have overlooked your post. He needs some sleep.

[haxxxen]

ah, no problem. i am used to it that people overlook me...and btw, i also had not much sleep, as i have bricked my (last) ps3 with some stupid mfw task, but now recovered again. it was only some softbrick luckily

[kik4444]

Guys where exactly in the MCodes do I insert the pattern that I want cause in the screenshot I saw there were 2 lines of codes and how do I convert CU codes into the original?

[Crow26]

Resident Evil The Darkside Chronicles HD usa

hacked by XTATU
Usercheats/Codefreak Format
Code:
NPUB30648
zombi freezer mode
L3 on R3 off
C001 00000000 00020000
2000 0002F604 4082FF4C
C001 00000000 00040000
2000 0002F604 4182FF4C

can place some of the problem
zombi speed mod
00002000 0002F730 3C80XXXX

3F80=normal
4000=2x
3f00=-1.5 slow

[aldostools]

Originally Posted by haxxxen ah, no problem. i am used to it that people overlook me...and btw, i also had not much sleep, as i have bricked my (last) ps3 with some stupid mfw task, but now recovered again. it was only some softbrick luckily

My apologies for overlook your post: The reason was that when I posted my reply to gingerbread's request, the forum posted my reply on the next page (skipping your post).

@gingerbread @haxxxen Thanks for the meaning for the codes 00001000 and 0000400X. However, I still need the meaning for others codes that I found: 00010000, 00005XXX, 00000XXX

Examples:
BLUS30790 <Dead Island US> 01.04
<001> Master Code
00000104 424C5553 30790018

BLJM60009 <Bladestorm The Hundred Years' War JP> 01.00
<008> Unit 1
00000000 1A34F8B2 0000001E <-- Apparently code 00000000 does not mean "Dummy"
00000000 1A34F8B3 00000009

BLUS30493 <Aliens vs. Predator US> 01.00
<001> Checkpoints Are Made Nonstop
00010000 0034561C 2F800000

BLES00072 <Ninja Gaiden Sigma EU> 01.00
<004> MP Max
00005100 1028C7EC 1028C7EE
00005000 00000001 00000000


I also have a theory: As the 00001000 are for 16bit codes (0-65535) (8bit would allow only 256) and 00002000 are for 32bit codes (0 - FFFFFFFF), then probably the 00001000 codes could work too on EBOOT patches. The 00002000 code writes 4 bytes, and the 00001000 code probably write only 2 bytes starting at the offset.

I would appreciate if someone could confirm this theory... then I would allow the codes 00002000 and 00001000 when I apply the codes that patch the EBOOT.ELF.

@gingerbread I didn't remove the ASM feature... maybe the feature could be used later... anyway it is more difficult to remove it, than leave it as is

UPDATE:
I have uploaded a WIP (work in progress) version 2.5.1... on the [Patch ELF] button (at the botton right corner) there is a new option: Advance Settings where you can enable the patches for codes 00001000 and 00010000 (they are disabled by default). It should help to make your tests easier

http://ps3tools.aldostools.org/PS3_C..._installer.rar

Please, report any bug that you find