High On Life

Upload your cheat tables here (No requests)
Aceofgods
Cheater
Cheater
Posts: 34
Joined: Sun Sep 22, 2019 11:20 pm
Reputation: 8

Re: High On Life

Post by Aceofgods »

I've a silly request, if anyone is capable of it: Would it be possible to make a cheat that unlocks/adds the 4 base weapons to your inventory?

I played through the game on launch version, and at the end of the game you make a decision regarding your guns. I initially made a decision I didn't like, so I loaded Last Checkpoint within the game and made a different decision... but now, during the postgame, I do not have access to one of my guns (Which means 1/4th of the puzzles etc are impossible xD)

Reading some of the patch notes on twitter it seems that the cause of this bug may have been fixed, but I'm still suffering from the bug itself, but I think simply adding the gun back to my inventory would possibly fix it. The pawn shop still sells upgrades for the gun, and the upgrades I had before are still in my inventory, so I do not think it's intentional.

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

booxihuan
What is cheating?
What is cheating?
Posts: 1
Joined: Sun Dec 18, 2022 1:09 am
Reputation: 0

Re: High On Life

Post by booxihuan »

Any possibility of hiding the HUD? :)

evilebob
What is cheating?
What is cheating?
Posts: 3
Joined: Sun Apr 25, 2021 3:15 am
Reputation: 1

Re: High On Life

Post by evilebob »

rambo99jose wrote:
Wed Dec 14, 2022 6:33 am
Game Version: UWP 20221213_R1911
Table Last Update:20221214_v0.5
Changelog

Code: Select all

[20221214_v0.5]
.....modified fuel script to prevent stuck visual bug

Steam version AOB for inf fuel:
aobscanmodule(INJECT_ptrFuel,Oregon-Win64-Shipping.exe,48 85 FF 0F 84 2A 01 00 00 E8 D3) // should be unique

*only difference is exe name and 1byte

acecel
Expert Cheater
Expert Cheater
Posts: 848
Joined: Sun Apr 09, 2017 1:32 am
Reputation: 142

Re: High On Life

Post by acecel »

A small script that allow to edit the game's FOV and force its value to stay put (when you sprint for example).

Copy the code below and paste it inside a table. Tell me if you have any issue with it.

@Akira : you can add the script in your table if you want to.


Gamepass version :

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<CheatTable>
  <CheatEntries>
    <CheatEntry>
      <ID>334345</ID>
      <Description>"Edit FOV (Gamepass)"</Description>
      <Options moHideChildren="1" moDeactivateChildrenAsWell="1"/>
      <LastState/>
      <Color>FFFF00</Color>
      <VariableType>Auto Assembler Script</VariableType>
      <AssemblerScript>{ Game   : Oregon-WinGDK-Shipping.exe
  Version: 
  Date   : 2022-12-20
  Author : acecel

  This script does blah blah blah
}

[ENABLE]

aobscanmodule(aob_fov,Oregon-WinGDK-Shipping.exe,F3 0F 10 8B 3C 02 00 00 4C 8D 85) // should be unique
alloc(newmem,$1000,aob_fov)
alloc(fov,$8)
registersymbol(fov)

label(code)
label(return)

newmem:

code:
  mov [fov],rbx
  movss xmm1,[rbx+0000023C]
  jmp return

aob_fov:
  jmp newmem
  nop 3
return:
registersymbol(aob_fov)




aobscanmodule(aob_fov2,Oregon-WinGDK-Shipping.exe,CC F3 0F 11 89 3C 02 00 00 C3 CC CC) // should be unique
alloc(newmem2,$1000,aob_fov2)

label(code2)
label(return2)

newmem2:

code2:
 // movss [rcx+0000023C],xmm1
  jmp return2

aob_fov2+01:
  jmp newmem2
  nop 3
return2:
registersymbol(aob_fov2)


[DISABLE]

aob_fov:
  db F3 0F 10 8B 3C 02 00 00

unregistersymbol(fov)
unregistersymbol(aob_fov)
dealloc(newmem)

{
// ORIGINAL CODE - INJECTION POINT: Oregon-WinGDK-Shipping.exe+1481E05

Oregon-WinGDK-Shipping.exe+1481DE5: 48 8B C8                 - mov rcx,rax
Oregon-WinGDK-Shipping.exe+1481DE8: 48 8B 46 30              - mov rax,[rsi+30]
Oregon-WinGDK-Shipping.exe+1481DEC: 48 39 14 C8              - cmp [rax+rcx*8],rdx
Oregon-WinGDK-Shipping.exe+1481DF0: 74 03                    - je Oregon-WinGDK-Shipping.exe+1481DF5
Oregon-WinGDK-Shipping.exe+1481DF2: 48 8B F7                 - mov rsi,rdi
Oregon-WinGDK-Shipping.exe+1481DF5: 48 8B D6                 - mov rdx,rsi
Oregon-WinGDK-Shipping.exe+1481DF8: 49 8B CE                 - mov rcx,r14
Oregon-WinGDK-Shipping.exe+1481DFB: E8 00 37 E2 01           - call Oregon-WinGDK-Shipping.exe+32A5500
Oregon-WinGDK-Shipping.exe+1481E00: 48 85 C0                 - test rax,rax
Oregon-WinGDK-Shipping.exe+1481E03: 74 1A                    - je Oregon-WinGDK-Shipping.exe+1481E1F
// ---------- INJECTING HERE ----------
Oregon-WinGDK-Shipping.exe+1481E05: F3 0F 10 8B 3C 02 00 00  - movss xmm1,[rbx+0000023C]
// ---------- DONE INJECTING  ----------
Oregon-WinGDK-Shipping.exe+1481E0D: 4C 8D 85 C0 07 00 00     - lea r8,[rbp+000007C0]
Oregon-WinGDK-Shipping.exe+1481E14: 4C 8B CB                 - mov r9,rbx
Oregon-WinGDK-Shipping.exe+1481E17: 48 8B C8                 - mov rcx,rax
Oregon-WinGDK-Shipping.exe+1481E1A: E8 E1 2B 03 00           - call Oregon-WinGDK-Shipping.exe+14B4A00
Oregon-WinGDK-Shipping.exe+1481E1F: 48 8B 03                 - mov rax,[rbx]
Oregon-WinGDK-Shipping.exe+1481E22: 48 8B CB                 - mov rcx,rbx
Oregon-WinGDK-Shipping.exe+1481E25: FF 90 60 01 00 00        - call qword ptr [rax+00000160]
Oregon-WinGDK-Shipping.exe+1481E2B: 4C 8D B0 60 07 00 00     - lea r14,[rax+00000760]
Oregon-WinGDK-Shipping.exe+1481E32: E8 09 B3 0E 00           - call Oregon-WinGDK-Shipping.exe+156D140
Oregon-WinGDK-Shipping.exe+1481E37: 48 8B F0                 - mov rsi,rax
}




aob_fov2+01:
  db F3 0F 11 89 3C 02 00 00

unregistersymbol(aob_fov2)
dealloc(newmem2)

{
// ORIGINAL CODE - INJECTION POINT: Oregon-WinGDK-Shipping.exe+314E230

Oregon-WinGDK-Shipping.exe+314E226: C3                       - ret
Oregon-WinGDK-Shipping.exe+314E227: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E228: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E229: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22A: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22B: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22C: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22D: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22E: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22F: CC                       - int 3
// ---------- INJECTING HERE ----------
Oregon-WinGDK-Shipping.exe+314E230: F3 0F 11 89 3C 02 00 00  - movss [rcx+0000023C],xmm1
// ---------- DONE INJECTING  ----------
Oregon-WinGDK-Shipping.exe+314E238: C3                       - ret
Oregon-WinGDK-Shipping.exe+314E239: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23A: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23B: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23C: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23D: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23E: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23F: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E240: 48 89 5C 24 08           - mov [rsp+08],rbx
Oregon-WinGDK-Shipping.exe+314E245: 48 89 6C 24 10           - mov [rsp+10],rbp
}
</AssemblerScript>
      <CheatEntries>
        <CheatEntry>
          <ID>334346</ID>
          <Description>"fov"</Description>
          <LastState Value="110" RealAddress="1FC69A8024C"/>
          <ShowAsSigned>0</ShowAsSigned>
          <Color>FF80FF</Color>
          <VariableType>Float</VariableType>
          <Address>fov</Address>
          <Offsets>
            <Offset>23C</Offset>
          </Offsets>
          <Hotkeys>
            <Hotkey>
              <Action>Set Value</Action>
              <Keys>
                <Key>17</Key>
                <Key>110</Key>
              </Keys>
              <Value>110</Value>
              <ID>0</ID>
              <ActivateSound>Activate</ActivateSound>
            </Hotkey>
            <Hotkey>
              <Action>Increase Value</Action>
              <Keys>
                <Key>17</Key>
                <Key>107</Key>
              </Keys>
              <Value>2</Value>
              <ID>3</ID>
              <ActivateSound>Activate</ActivateSound>
            </Hotkey>
            <Hotkey>
              <Action>Decrease Value</Action>
              <Keys>
                <Key>17</Key>
                <Key>109</Key>
              </Keys>
              <Value>2</Value>
              <ID>4</ID>
              <ActivateSound>Deactivate</ActivateSound>
            </Hotkey>
          </Hotkeys>
        </CheatEntry>
      </CheatEntries>
    </CheatEntry>
  </CheatEntries>
</CheatTable>


Steam version :

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<CheatTable>
  <CheatEntries>
    <CheatEntry>
      <ID>334398</ID>
      <Description>"Edit FOV (Steam)"</Description>
      <Options moHideChildren="1" moDeactivateChildrenAsWell="1"/>
      <LastState/>
      <Color>FFFF00</Color>
      <VariableType>Auto Assembler Script</VariableType>
      <AssemblerScript>{ Game   : Oregon-Win64-Shipping.exe
  Version: 
  Date   : 2022-12-20
  Author : acecel

  This script does blah blah blah
}

[ENABLE]

aobscanmodule(aob_fov,Oregon-Win64-Shipping.exe,F3 0F 10 B1 3C 02 00 00 33) // should be unique
alloc(newmem,$1000,aob_fov)
alloc(fov,$8)
registersymbol(fov)

label(code)
label(return)

newmem:

code:
  mov [fov],rcx
  movss xmm6,[rcx+0000023C]
  jmp return

aob_fov:
  jmp newmem
  nop 3
return:
registersymbol(aob_fov)




aobscanmodule(aob_fov2,Oregon-Win64-Shipping.exe,CC F3 0F 11 89 3C 02 00 00 C3) // should be unique
alloc(newmem2,$1000,aob_fov2)

label(code2)
label(return2)

newmem2:

code2:
 // movss [rcx+0000023C],xmm1
  jmp return2

aob_fov2+01:
  jmp newmem2
  nop 3
return2:
registersymbol(aob_fov2)



[DISABLE]

aob_fov:
  db F3 0F 10 B1 3C 02 00 00

unregistersymbol(fov)
unregistersymbol(aob_fov)
dealloc(newmem)

{
// ORIGINAL CODE - INJECTION POINT: Oregon-Win64-Shipping.exe+3455981

Oregon-Win64-Shipping.exe+3455958: 48 83 C4 68              - add rsp,68
Oregon-Win64-Shipping.exe+345595C: C3                       - ret 
Oregon-Win64-Shipping.exe+345595D: CC                       - int 3 
Oregon-Win64-Shipping.exe+345595E: CC                       - int 3 
Oregon-Win64-Shipping.exe+345595F: CC                       - int 3 
Oregon-Win64-Shipping.exe+3455960: 48 81 EC E8 08 00 00     - sub rsp,000008E8
Oregon-Win64-Shipping.exe+3455967: 0F 29 B4 24 D0 08 00 00  - movaps [rsp+000008D0],xmm6
Oregon-Win64-Shipping.exe+345596F: 48 8B 05 E2 E7 4A 02     - mov rax,[Oregon-Win64-Shipping.exe+5904158]
Oregon-Win64-Shipping.exe+3455976: 48 33 C4                 - xor rax,rsp
Oregon-Win64-Shipping.exe+3455979: 48 89 84 24 C0 08 00 00  - mov [rsp+000008C0],rax
// ---------- INJECTING HERE ----------
Oregon-Win64-Shipping.exe+3455981: F3 0F 10 B1 3C 02 00 00  - movss xmm6,[rcx+0000023C]
// ---------- DONE INJECTING  ----------
Oregon-Win64-Shipping.exe+3455989: 33 C0                    - xor eax,eax
Oregon-Win64-Shipping.exe+345598B: 0F 57 C9                 - xorps xmm1,xmm1
Oregon-Win64-Shipping.exe+345598E: 89 44 24 20              - mov [rsp+20],eax
Oregon-Win64-Shipping.exe+3455992: 0F 2F F1                 - comiss xmm6,xmm1
Oregon-Win64-Shipping.exe+3455995: 77 2D                    - ja Oregon-Win64-Shipping.exe+34559C4
Oregon-Win64-Shipping.exe+3455997: 48 8B 01                 - mov rax,[rcx]
Oregon-Win64-Shipping.exe+345599A: 48 8D 54 24 30           - lea rdx,[rsp+30]
Oregon-Win64-Shipping.exe+345599F: FF 90 78 06 00 00        - call qword ptr [rax+00000678]
Oregon-Win64-Shipping.exe+34559A5: 48 8B 8C 24 60 08 00 00  - mov rcx,[rsp+00000860]
Oregon-Win64-Shipping.exe+34559AD: F3 0F 10 70 18           - movss xmm6,[rax+18]
}



aob_fov2+01:
  db F3 0F 11 89 3C 02 00 00

unregistersymbol(aob_fov2)
dealloc(newmem2)

{
// ORIGINAL CODE - INJECTION POINT: Oregon-Win64-Shipping.exe+3466200

Oregon-Win64-Shipping.exe+34661F6: C3                       - ret
Oregon-Win64-Shipping.exe+34661F7: CC                       - int 3
Oregon-Win64-Shipping.exe+34661F8: CC                       - int 3
Oregon-Win64-Shipping.exe+34661F9: CC                       - int 3
Oregon-Win64-Shipping.exe+34661FA: CC                       - int 3
Oregon-Win64-Shipping.exe+34661FB: CC                       - int 3
Oregon-Win64-Shipping.exe+34661FC: CC                       - int 3
Oregon-Win64-Shipping.exe+34661FD: CC                       - int 3
Oregon-Win64-Shipping.exe+34661FE: CC                       - int 3
Oregon-Win64-Shipping.exe+34661FF: CC                       - int 3
// ---------- INJECTING HERE ----------
Oregon-Win64-Shipping.exe+3466200: F3 0F 11 89 3C 02 00 00  - movss [rcx+0000023C],xmm1
// ---------- DONE INJECTING  ----------
Oregon-Win64-Shipping.exe+3466208: C3                       - ret
Oregon-Win64-Shipping.exe+3466209: CC                       - int 3
Oregon-Win64-Shipping.exe+346620A: CC                       - int 3
Oregon-Win64-Shipping.exe+346620B: CC                       - int 3
Oregon-Win64-Shipping.exe+346620C: CC                       - int 3
Oregon-Win64-Shipping.exe+346620D: CC                       - int 3
Oregon-Win64-Shipping.exe+346620E: CC                       - int 3
Oregon-Win64-Shipping.exe+346620F: CC                       - int 3
Oregon-Win64-Shipping.exe+3466210: 48 89 5C 24 08           - mov [rsp+08],rbx
Oregon-Win64-Shipping.exe+3466215: 48 89 6C 24 10           - mov [rsp+10],rbp
}
</AssemblerScript>
      <CheatEntries>
        <CheatEntry>
          <ID>334399</ID>
          <Description>"fov"</Description>
          <ShowAsSigned>0</ShowAsSigned>
          <Color>FF80FF</Color>
          <VariableType>Float</VariableType>
          <Address>fov</Address>
          <Offsets>
            <Offset>23C</Offset>
          </Offsets>
        </CheatEntry>
      </CheatEntries>
    </CheatEntry>
  </CheatEntries>
</CheatTable>

Last edited by acecel on Tue Dec 20, 2022 10:57 pm, edited 4 times in total.

khuong
Expert Cheater
Expert Cheater
Posts: 76
Joined: Sat Jan 08, 2022 5:18 pm
Reputation: 41

Re: High On Life

Post by khuong »

acecel wrote:
Tue Dec 20, 2022 5:29 am
A small script that allow to edit the game's FOV and force its value to stay put (when you sprint).

Copy the code below and paste it inside a table. Tell me if you have any issue with it.

@Akira : you can add the script in your table if you want to.

Code: Select all


<?xml version="1.0" encoding="utf-8"?>
<CheatTable>
  <CheatEntries>
    <CheatEntry>
      <ID>334348</ID>
      <Description>"Edit FOV"</Description>
      <Options moHideChildren="1" moDeactivateChildrenAsWell="1"/>
      <LastState/>
      <Color>FFFF00</Color>
      <VariableType>Auto Assembler Script</VariableType>
      <AssemblerScript>{ Game   : Oregon-WinGDK-Shipping.exe
  Version:
  Date   : 2022-12-20
  Author : acecel

  This script does blah blah blah
}

[ENABLE]

aobscanmodule(aob_fov,Oregon-WinGDK-Shipping.exe,F3 0F 10 8B 3C 02 00 00 4C 8D 85) // should be unique
alloc(newmem,$1000,aob_fov)
alloc(fov,$8)
registersymbol(fov)

label(code)
label(return)

newmem:

code:
  mov [fov],rbx
  movss xmm1,[rbx+0000023C]
  jmp return

aob_fov:
  jmp newmem
  nop 3
return:
registersymbol(aob_fov)




aobscanmodule(aob_fov2,Oregon-WinGDK-Shipping.exe,CC F3 0F 11 89 3C 02 00 00 C3 CC CC) // should be unique
alloc(newmem2,$1000,aob_fov2)

label(code2)
label(return2)

newmem2:

code2:
 // movss [rcx+0000023C],xmm1
  jmp return2

aob_fov2+01:
  jmp newmem2
  nop 3
return2:
registersymbol(aob_fov2)


[DISABLE]

aob_fov:
  db F3 0F 10 8B 3C 02 00 00

unregistersymbol(fov)
unregistersymbol(aob_fov)
dealloc(newmem)

{
// ORIGINAL CODE - INJECTION POINT: Oregon-WinGDK-Shipping.exe+1481E05

Oregon-WinGDK-Shipping.exe+1481DE5: 48 8B C8                 - mov rcx,rax
Oregon-WinGDK-Shipping.exe+1481DE8: 48 8B 46 30              - mov rax,[rsi+30]
Oregon-WinGDK-Shipping.exe+1481DEC: 48 39 14 C8              - cmp [rax+rcx*8],rdx
Oregon-WinGDK-Shipping.exe+1481DF0: 74 03                    - je Oregon-WinGDK-Shipping.exe+1481DF5
Oregon-WinGDK-Shipping.exe+1481DF2: 48 8B F7                 - mov rsi,rdi
Oregon-WinGDK-Shipping.exe+1481DF5: 48 8B D6                 - mov rdx,rsi
Oregon-WinGDK-Shipping.exe+1481DF8: 49 8B CE                 - mov rcx,r14
Oregon-WinGDK-Shipping.exe+1481DFB: E8 00 37 E2 01           - call Oregon-WinGDK-Shipping.exe+32A5500
Oregon-WinGDK-Shipping.exe+1481E00: 48 85 C0                 - test rax,rax
Oregon-WinGDK-Shipping.exe+1481E03: 74 1A                    - je Oregon-WinGDK-Shipping.exe+1481E1F
// ---------- INJECTING HERE ----------
Oregon-WinGDK-Shipping.exe+1481E05: F3 0F 10 8B 3C 02 00 00  - movss xmm1,[rbx+0000023C]
// ---------- DONE INJECTING  ----------
Oregon-WinGDK-Shipping.exe+1481E0D: 4C 8D 85 C0 07 00 00     - lea r8,[rbp+000007C0]
Oregon-WinGDK-Shipping.exe+1481E14: 4C 8B CB                 - mov r9,rbx
Oregon-WinGDK-Shipping.exe+1481E17: 48 8B C8                 - mov rcx,rax
Oregon-WinGDK-Shipping.exe+1481E1A: E8 E1 2B 03 00           - call Oregon-WinGDK-Shipping.exe+14B4A00
Oregon-WinGDK-Shipping.exe+1481E1F: 48 8B 03                 - mov rax,[rbx]
Oregon-WinGDK-Shipping.exe+1481E22: 48 8B CB                 - mov rcx,rbx
Oregon-WinGDK-Shipping.exe+1481E25: FF 90 60 01 00 00        - call qword ptr [rax+00000160]
Oregon-WinGDK-Shipping.exe+1481E2B: 4C 8D B0 60 07 00 00     - lea r14,[rax+00000760]
Oregon-WinGDK-Shipping.exe+1481E32: E8 09 B3 0E 00           - call Oregon-WinGDK-Shipping.exe+156D140
Oregon-WinGDK-Shipping.exe+1481E37: 48 8B F0                 - mov rsi,rax
}




aob_fov2+01:
  db F3 0F 11 89 3C 02 00 00

unregistersymbol(aob_fov2)
dealloc(newmem2)

{
// ORIGINAL CODE - INJECTION POINT: Oregon-WinGDK-Shipping.exe+314E230

Oregon-WinGDK-Shipping.exe+314E226: C3                       - ret
Oregon-WinGDK-Shipping.exe+314E227: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E228: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E229: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22A: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22B: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22C: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22D: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22E: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22F: CC                       - int 3
// ---------- INJECTING HERE ----------
Oregon-WinGDK-Shipping.exe+314E230: F3 0F 11 89 3C 02 00 00  - movss [rcx+0000023C],xmm1
// ---------- DONE INJECTING  ----------
Oregon-WinGDK-Shipping.exe+314E238: C3                       - ret
Oregon-WinGDK-Shipping.exe+314E239: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23A: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23B: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23C: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23D: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23E: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23F: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E240: 48 89 5C 24 08           - mov [rsp+08],rbx
Oregon-WinGDK-Shipping.exe+314E245: 48 89 6C 24 10           - mov [rsp+10],rbp
}
</AssemblerScript>
      <Hotkeys>
        <Hotkey>
          <Action>Activate</Action>
          <Keys>
            <Key>17</Key>
            <Key>110</Key>
          </Keys>
          <ID>0</ID>
        </Hotkey>
      </Hotkeys>
      <CheatEntries>
        <CheatEntry>
          <ID>334349</ID>
          <Description>"fov"</Description>
          <LastState Value="106" RealAddress="119DA024C"/>
          <ShowAsSigned>0</ShowAsSigned>
          <Color>FF80FF</Color>
          <VariableType>Float</VariableType>
          <Address>fov</Address>
          <Offsets>
            <Offset>23C</Offset>
          </Offsets>
        </CheatEntry>
      </CheatEntries>
    </CheatEntry>
  </CheatEntries>
</CheatTable>

Just what I was looking for.. without having to enable Console!

acecel
Expert Cheater
Expert Cheater
Posts: 848
Joined: Sun Apr 09, 2017 1:32 am
Reputation: 142

Re: High On Life

Post by acecel »

khuong wrote:
Tue Dec 20, 2022 10:22 pm
acecel wrote:
Tue Dec 20, 2022 5:29 am
A small script that allow to edit the game's FOV and force its value to stay put (when you sprint).

Copy the code below and paste it inside a table. Tell me if you have any issue with it.

@Akira : you can add the script in your table if you want to.

Code: Select all


<?xml version="1.0" encoding="utf-8"?>
<CheatTable>
  <CheatEntries>
    <CheatEntry>
      <ID>334348</ID>
      <Description>"Edit FOV"</Description>
      <Options moHideChildren="1" moDeactivateChildrenAsWell="1"/>
      <LastState/>
      <Color>FFFF00</Color>
      <VariableType>Auto Assembler Script</VariableType>
      <AssemblerScript>{ Game   : Oregon-WinGDK-Shipping.exe
  Version:
  Date   : 2022-12-20
  Author : acecel

  This script does blah blah blah
}

[ENABLE]

aobscanmodule(aob_fov,Oregon-WinGDK-Shipping.exe,F3 0F 10 8B 3C 02 00 00 4C 8D 85) // should be unique
alloc(newmem,$1000,aob_fov)
alloc(fov,$8)
registersymbol(fov)

label(code)
label(return)

newmem:

code:
  mov [fov],rbx
  movss xmm1,[rbx+0000023C]
  jmp return

aob_fov:
  jmp newmem
  nop 3
return:
registersymbol(aob_fov)




aobscanmodule(aob_fov2,Oregon-WinGDK-Shipping.exe,CC F3 0F 11 89 3C 02 00 00 C3 CC CC) // should be unique
alloc(newmem2,$1000,aob_fov2)

label(code2)
label(return2)

newmem2:

code2:
 // movss [rcx+0000023C],xmm1
  jmp return2

aob_fov2+01:
  jmp newmem2
  nop 3
return2:
registersymbol(aob_fov2)


[DISABLE]

aob_fov:
  db F3 0F 10 8B 3C 02 00 00

unregistersymbol(fov)
unregistersymbol(aob_fov)
dealloc(newmem)

{
// ORIGINAL CODE - INJECTION POINT: Oregon-WinGDK-Shipping.exe+1481E05

Oregon-WinGDK-Shipping.exe+1481DE5: 48 8B C8                 - mov rcx,rax
Oregon-WinGDK-Shipping.exe+1481DE8: 48 8B 46 30              - mov rax,[rsi+30]
Oregon-WinGDK-Shipping.exe+1481DEC: 48 39 14 C8              - cmp [rax+rcx*8],rdx
Oregon-WinGDK-Shipping.exe+1481DF0: 74 03                    - je Oregon-WinGDK-Shipping.exe+1481DF5
Oregon-WinGDK-Shipping.exe+1481DF2: 48 8B F7                 - mov rsi,rdi
Oregon-WinGDK-Shipping.exe+1481DF5: 48 8B D6                 - mov rdx,rsi
Oregon-WinGDK-Shipping.exe+1481DF8: 49 8B CE                 - mov rcx,r14
Oregon-WinGDK-Shipping.exe+1481DFB: E8 00 37 E2 01           - call Oregon-WinGDK-Shipping.exe+32A5500
Oregon-WinGDK-Shipping.exe+1481E00: 48 85 C0                 - test rax,rax
Oregon-WinGDK-Shipping.exe+1481E03: 74 1A                    - je Oregon-WinGDK-Shipping.exe+1481E1F
// ---------- INJECTING HERE ----------
Oregon-WinGDK-Shipping.exe+1481E05: F3 0F 10 8B 3C 02 00 00  - movss xmm1,[rbx+0000023C]
// ---------- DONE INJECTING  ----------
Oregon-WinGDK-Shipping.exe+1481E0D: 4C 8D 85 C0 07 00 00     - lea r8,[rbp+000007C0]
Oregon-WinGDK-Shipping.exe+1481E14: 4C 8B CB                 - mov r9,rbx
Oregon-WinGDK-Shipping.exe+1481E17: 48 8B C8                 - mov rcx,rax
Oregon-WinGDK-Shipping.exe+1481E1A: E8 E1 2B 03 00           - call Oregon-WinGDK-Shipping.exe+14B4A00
Oregon-WinGDK-Shipping.exe+1481E1F: 48 8B 03                 - mov rax,[rbx]
Oregon-WinGDK-Shipping.exe+1481E22: 48 8B CB                 - mov rcx,rbx
Oregon-WinGDK-Shipping.exe+1481E25: FF 90 60 01 00 00        - call qword ptr [rax+00000160]
Oregon-WinGDK-Shipping.exe+1481E2B: 4C 8D B0 60 07 00 00     - lea r14,[rax+00000760]
Oregon-WinGDK-Shipping.exe+1481E32: E8 09 B3 0E 00           - call Oregon-WinGDK-Shipping.exe+156D140
Oregon-WinGDK-Shipping.exe+1481E37: 48 8B F0                 - mov rsi,rax
}




aob_fov2+01:
  db F3 0F 11 89 3C 02 00 00

unregistersymbol(aob_fov2)
dealloc(newmem2)

{
// ORIGINAL CODE - INJECTION POINT: Oregon-WinGDK-Shipping.exe+314E230

Oregon-WinGDK-Shipping.exe+314E226: C3                       - ret
Oregon-WinGDK-Shipping.exe+314E227: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E228: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E229: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22A: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22B: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22C: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22D: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22E: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E22F: CC                       - int 3
// ---------- INJECTING HERE ----------
Oregon-WinGDK-Shipping.exe+314E230: F3 0F 11 89 3C 02 00 00  - movss [rcx+0000023C],xmm1
// ---------- DONE INJECTING  ----------
Oregon-WinGDK-Shipping.exe+314E238: C3                       - ret
Oregon-WinGDK-Shipping.exe+314E239: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23A: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23B: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23C: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23D: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23E: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E23F: CC                       - int 3
Oregon-WinGDK-Shipping.exe+314E240: 48 89 5C 24 08           - mov [rsp+08],rbx
Oregon-WinGDK-Shipping.exe+314E245: 48 89 6C 24 10           - mov [rsp+10],rbp
}
</AssemblerScript>
      <Hotkeys>
        <Hotkey>
          <Action>Activate</Action>
          <Keys>
            <Key>17</Key>
            <Key>110</Key>
          </Keys>
          <ID>0</ID>
        </Hotkey>
      </Hotkeys>
      <CheatEntries>
        <CheatEntry>
          <ID>334349</ID>
          <Description>"fov"</Description>
          <LastState Value="106" RealAddress="119DA024C"/>
          <ShowAsSigned>0</ShowAsSigned>
          <Color>FF80FF</Color>
          <VariableType>Float</VariableType>
          <Address>fov</Address>
          <Offsets>
            <Offset>23C</Offset>
          </Offsets>
        </CheatEntry>
      </CheatEntries>
    </CheatEntry>
  </CheatEntries>
</CheatTable>

Just what I was looking for.. without having to enable Console!
I updated my post with the steam version of the script, as the first one i posted was for gamepass version, i hope both works well for everyone.

Edit : To help a little with the stuttering issues you can edit the engine.ini file in the folder :
"C:\Users\USERNAME\AppData\Local\Oregon\Saved\Config\WindowsNoEditor"
By adding to the file :
[/script/engine.renderersettings]
r.CreateShadersOnLoad=1
You can also disable all effects like blur, bloom, noise, chromatic aberration ..

Here is mine :

Code: Select all

(Original File Content)
...

[SystemSettings]
r.Tonemapper.GrainQuantization=0
r.Tonemapper.Quality=0
r.SceneColorFringeQuality=0
r.SceneColorFringe.Max=0
r.MotionBlurQuality=0
r.BlurGBuffer=0
r.MotionBlur.Max=0
r.BloomQuality=0

r.MaxAnisotropy=16

r.DefaultFeature.AntiAliasing=2
r.TemporalAACurrentFrameWeight=0.2
r.TemporalAASamples=32
r.TemporalAASharpness=0.8

r.Tonemapper.Sharpen=0.7

r.FullScreenMode=0

[/script/engine.renderersettings]
r.CreateShadersOnLoad=1


CostaBr33ze
What is cheating?
What is cheating?
Posts: 3
Joined: Thu Aug 22, 2019 8:53 pm
Reputation: 0

Re: High On Life

Post by CostaBr33ze »

Anyone figure out how to get more warp disks? None of the tables I've seen point to warp disks correctly. I'd do it myself but I'd have to restart the game from scratch to spend some disks ... and I don't wanna do that :(

jankec126
What is cheating?
What is cheating?
Posts: 1
Joined: Thu Jan 05, 2023 9:35 am
Reputation: 0

Re: High On Life

Post by jankec126 »

Hello, I've recently lost my High on Life savegame on the Nipulon bounty part. I was wondering if anyone has a savegame on that part that he can send. Thank you

ChocoMilk123
Noobzor
Noobzor
Posts: 5
Joined: Mon Feb 20, 2023 8:30 am
Reputation: 1

Re: High On Life

Post by ChocoMilk123 »

Hey, Akira. :D

I just wanna say that I've been trying to figure out an infinite jump for like 3 days now and still haven't done it. ;-;

I've played with many values and edited so much opcode... Out of desperation I started going down the stack turning everything into NOP's to just force-find it.

Anyway, I just think it's awesome you managed to figure out an infinite jump because it means it's possible.

I was gonna ask if you remember how you did it, if it was basic cheat engine understanding or something more advanced. I don't know what LUA is yet, perhaps you used LUA in some way to do it?

I guess what I'm asking is: Did you make the cheat from basic scanning and finding out which opcode (the normal way) or did you do something advanced which I need to learn in order to do it?

User avatar
Akira
Table Makers
Table Makers
Posts: 1268
Joined: Fri May 24, 2019 2:04 am
Reputation: 1676

Re: High On Life

Post by Akira »

ChocoMilk123 wrote:
Sat Feb 25, 2023 7:00 pm
infinite jump
Unreal Engine it self has a function for jumping which is what I used.

ChocoMilk123
Noobzor
Noobzor
Posts: 5
Joined: Mon Feb 20, 2023 8:30 am
Reputation: 1

Re: High On Life

Post by ChocoMilk123 »

Omg!!! Thank you!!! I've searched it, and now I'm learning it on YouTube! :)


I'm so glad I logged in to ask now, I almost didn't and would've went on feeling defeated and upset. xD

I scanned for:
1.when jump button was held on/off (this found a bunnyhop but useless cheat).
2. when a bool was on/off for detecting if you're in the air or not (found but didn't lead to infinite jump).
3. finding and checking memory region of player coordinates, then found jump-related opcode but didn't lead to an infinite jump.
4. brute-force nop's down the stack (this found air movement velocity and jump height after lots of crashing).
5. changing 0's to 1's and fiddling with other random values in the stack.

Thanks to you I can finish off my table once I've learnt this new feature, and possibly try and find a no-collision cheat for getting chests locked in rooms which require Creature.

Thank you so much!

User avatar
Akira
Table Makers
Table Makers
Posts: 1268
Joined: Fri May 24, 2019 2:04 am
Reputation: 1676

Re: High On Life

Post by Akira »

ChocoMilk123 wrote:
Sun Feb 26, 2023 3:19 am
Thank you so much!
I would recommand to learn a bit more about CE before using other tools such as the GH Dumper.
You could have found it easily by just scanning for your current jump count, 0 when on ground and 1 when jumped 1x (while in air).
You can just freeze or pause the game so your character stays in air for easier scanning.

ChocoMilk123
Noobzor
Noobzor
Posts: 5
Joined: Mon Feb 20, 2023 8:30 am
Reputation: 1

Re: High On Life

Post by ChocoMilk123 »

Akira wrote:
Sun Feb 26, 2023 3:24 am
You could have found it easily by just scanning for your current jump count, 0 when on ground and 1 when jumped 1x (while in air).
You can just freeze or pause the game so your character stays in air for easier scanning.
I had tried this but freezing the values and fiddling with related opcode didn't create an infinite jump. I looked around the stack to find cmp's or odd numbers that might look like checks or height caps or anything, to no avail.

User avatar
Akira
Table Makers
Table Makers
Posts: 1268
Joined: Fri May 24, 2019 2:04 am
Reputation: 1676

Re: High On Life

Post by Akira »

I mean, that's how i found it the first time, so I guess you did something wrong while scanning or you didn't know how to make a proper script.
It's always better to learn how to doi things correctly yourself before using other tools to make your life easier/speed up the process of finding things.

ChocoMilk123
Noobzor
Noobzor
Posts: 5
Joined: Mon Feb 20, 2023 8:30 am
Reputation: 1

Re: High On Life

Post by ChocoMilk123 »

I scanned for 0 and 1 and found it. *facepalm* You just have to change an inc to dec.

What's bad is I missed this in my scanning twice, found it just now. Well, I guess I wouldn't have found air movement speed if I didn't screw up and devolve into craziness putting nop's all down a stack. So, at least I have infinite jump and air movement speed to compliment it.

Thanks for your help, I'm glad you told me about that plugin too and I'll have to check it out sometime but not in-depth until I've finished remembering everything in this beginner tutorial on YouTube. I'm learning from Cheat The Game. ^_^

After learning the beginner tutorial I hope to learn how to use dbg64 for bypassing anti-debuggers.

Post Reply

Who is online

Users browsing this forum: Baidu [Spider], Bing [Bot], Bloodgutter, bthornton, CryptoCF, Eren, Google Adsense [Bot], Gurzo, ins, kalotus, maifa2022, MaLuSR, MichaelNotJohn, remsdeus, saqueeb308, SemrushBot, shadowkick, Somewhat_Awbawlisk, Worky, Zeyus