DOOM Eternal [Engine:idTech 7]

[ScoobyRVA]

[QUOTE="ShaneRR, post: 140735, member: 42671"]

Hey guys,



are there any known issues with the current version of the game and table?

My buildinfo says version 7.1.1, release-patch2.

I downloaded table v1.4, re-installed Cheat Engine 7.1 (someone here mentioned that it helped for him) and checked the installation via Steam.

All seems fine, but the "Unrestrict Console Commands" option is not working for me.



The last time I played was before the whole Denuvo debacle and it worked perfectly back then.

Any ideas? ;)

[/QUOTE]



Just stopped working for me, ironically it would let me check the secondary box for noclip and notarget but they didn't actually work. Had been using successfully until just now. Probably some update to the game. Maybe SunBeam will release an update.

How to use this cheat table?

1. Install Cheat Engine
2. Double-click the .CT file in order to open it.
3. Click the PC icon in Cheat Engine in order to select the game process.
4. Keep the list.
5. Activate the trainer options by checking boxes or setting values from 0 to 1

[Telkom]

Yesterday the game was updated and the table no longer works. SunBeam, could you update your table, please.

[KyleKatarn]

The Table made by Zanzer still works. It's on the first page of this thread.

[Telkom]

I meant the table for unlocking console commands.

[ShaneRR]

Alright, here is a possible solution for the console unlock.

I won't be posting a new table because this is SunBeam's work and I don't want to take any credit for it.

But you can edit the 1.4 table yourself.



In the "Unrestrict Console" script for the hotfix2:

Change (should be line #40) from:

Code: Select all

4C8B0FBA01000000488BCF448BF041FF51??4C6BC507

to:

Code: Select all

4C8B0FBA01000000488BCF448BF041FF51??4C8BCE83

(the last 3 bytes are different).



I tried god and infinite ammo and it works.

[matthewfraser81]

Alright, here is a possible solution for the console unlock.

I won't be posting a new table because this is SunBeam's work and I don't want to take any credit for it.

But you can edit the 1.4 table yourself.



In the "Unrestrict Console" script for the hotfix2:

Change (should be line #40) from:

Code: Select all

4C8B0FBA01000000488BCF448BF041FF51??4C6BC507

to:

Code: Select all

4C8B0FBA01000000488BCF448BF041FF51??4C8BCE83

(the last 3 bytes are different).



I tried god and infinite ammo and it works.

Thanks so much ShaneRR and SunBeam, just bought Doom elemental and immediately disliked it.



The "tweaks" really bring back the Doom2016 gameplay. Wish enabling the pistol still worked.



Edit: Should have confirmed that it worked

[sebastianyyz]

Alright, here is a possible solution for the console unlock.

I won't be posting a new table because this is SunBeam's work and I don't want to take any credit for it.

But you can edit the 1.4 table yourself.



In the "Unrestrict Console" script for the hotfix2:

Change (should be line #40) from:

Code: Select all

4C8B0FBA01000000488BCF448BF041FF51??4C6BC507

to:

Code: Select all

4C8B0FBA01000000488BCF448BF041FF51??4C8BCE83

(the last 3 bytes are different).



I tried god and infinite ammo and it works.

Thank you so much, I can confirm it works

[SunBeam]

Code: Select all

4C8B0FBA01000000488BCF448BF041FF51??4C6BC507

to:

Code: Select all

4C8B0FBA01000000488BCF448BF041FF51??4C8BCE83

(the last 3 bytes are different).

Considering the first post on this page was you asking for a table update, I can only assume the above is taken from someplace? Like some DOOM Discord where some user figured out the array? What I can tell you is if those 3 bytes changed, they will change again. So find the common denominator between the old and new (4C??????). Or just stop at 4C.

[ShaneRR]

Considering the first post on this page was you asking for a table update, I can only assume the above is taken from someplace? Like some DOOM Discord where some user figured out the array? What I can tell you is if those 3 bytes changed, they will change again. So find the common denominator between the old and new (4C??????). Or just stop at 4C.

No, I searched for it myself. Just didn't have the time to look myself at that moment.

Code tends to change, but often not completely. So I looked until the first ??, how often I can find it and what comes after that. The search turned out only one hit, so I tried it out and it worked.

Had I copied it from somewhere, I would have mentioned it.



As to "they will change again". Well, maybe. Eventually

Offsets tends to change. From what I can see the 8C/6C change is a different register which is less common, since the code around it has to change for the compiler to optimize the code differently.

And the last byte is the beginning of the next opcode. Leaving that out might be a good idea.

I can't tell if this code has changed before since the 1.4 is your first table that includes this.

The first array of bytes you look for is identical for all versions since your first table (except the ?? of course), but no op-code changes there.



My instict would be to wait for the next updates and if the last bytes change again (and depending on how they changed) and THEN leave something out or use ??.

But of course all of this can change at any time, especially with all the heavy optimizations the compilers are doing.

[automerge]1593242812[/automerge]

Thanks so much ShaneRR and SunBeam, just bought Doom elemental and immediately disliked it.



The "tweaks" really bring back the Doom2016 gameplay. Wish enabling the pistol still worked.



Edit: Should have confirmed that it worked

I had the same problem.

Doom Eternal is great, but this "constantly out of ammo" thing really saps the fun out of it for me.

SunBeam has brought the fun back for me as well

[SunBeam]

Focus on the reason "bytes change". Not on assumptions or some logic you devised. They change because of compiler optimizations. Offsets, calls, jumps, etc. - all these are covered by those ?? in my array. The problem is this: threads/10253. See under " [ 28 Apr '20 - Update #7 ] ".







Best regards,

Sun

[ShaneRR]

[QUOTE="SunBeam, post: 140866, member: 12587"]

Focus on the reason "bytes change". Not on assumptions or some logic you devised. They change because of compiler optimizations. Offsets, calls, jumps, etc. - all these are covered by those ?? in my array. The problem is this: [URL]https://fearlessrevolution.com/threads/10253[/URL]. See under " [B][ 28 Apr '20 - Update #7 ][/B] ".



Best regards,

Sun

[/QUOTE]

Interesting. That's why I leave creating tables to guys like you! ;)

I am pretty comfortable with assembly on micro-Controllers (µC), it's my job after all.

But code for Windows is a very different beast from code in embedded development.

However, I like to "dabble" and sometimes something useful comes out of it. :)

[Khronos___]

for some reason I can't enable the Unrestrict Console script. Am I missing something?

[svperstar]

I changed the last 3 bytes and its not working.

Can we can an update? Also Id software always supported the mod community in the past so its disgusting we have to use a cheat table just to access the console.

[SunBeam]

I find it hilarious how generations mame words and give them random meanings.

[Khronos___]

for some reason I can't enable the Unrestrict Console script. Am I missing something?

I now know why. I right click the script and it says that line 3 of the script has a Lua error. Is it possible you could fix it? Do I have the right line of code in my Cheat table download? for me line three says {$lua}. Or more possible something about a Syntax Check, which it mentions in the Lua Error button.