Memory became unwritable in Stand 116.4

[Polyester-ak-Parci]

• Obvious problem description
  • In Stand 116.4 some memory(with executable code) that was possible to write in previous become unwritable

[Sainan]

This is intentional. Could you provide an example where you would need to write over code?

[Sainan]

Could you be more specific? Why are you trying to overwrite bytecode?

[Polyester-ak-Parci]

Also please explain the reason if possible

[Polyester-ak-Parci]

Could you be more specific? Why are you trying to overwrite bytecode?

I just want to set my hooks where it is necessary for me.

[Sainan]

Hooking into game functions is not a feature of the Lua API.

[Sainan]

Also please explain the reason if possible

This is done for security as there are tons of risks with unmanaged access to bytecode. I have also not seen any use-cases of this, so it seemed like a no-brainer risk mitigation.

[Polyester-ak-Parci]

Also please explain the reason if possible

This is done for security as there are tons of risks with unmanaged access to bytecode. I have also not seen any use-cases of this, so it seemed like a no-brainer risk mitigation.

Can you please return the ability to write to any place in memory? let it be enabled by a separate check mark or available in the lua developer mode

[Polyester-ak-Parci]

Like internet connection

[Sainan]

I have yet to see any valid use case of this, and I highly doubt a user could possibly understand the implications of any such checkbox.

[Polyester-ak-Parci]

I have yet to see any valid use case of this, and I highly doubt a user could possibly understand the implications of any such checkbox.

You can hide this feature somewhere in the settings and not allow it to be switched via the lua api.

[Sainan]

Maybe explain what your reason for needing this is.

[Polyester-ak-Parci]

Maybe explain what your reason for needing this is.

to set hooks in places where I need it. or for example, here is the code to disable collision for vehicles and it does not work either.

local backupcol = 0
local nocollisionveh = menu.my_root():toggle("Disable Collision", {}, "", function(on)
    if on then
        backupcol = memory.read_ubyte(DisableCollision)
        memory.write_ubyte(DisableCollision, 0xEB)
    else
        memory.write_ubyte(DisableCollision, backupcol)
    end
end)```

[Sainan]

Your explanation is nonsensical. This is a bytepatch, not a hook. Also, what exactly is the point of this "disable collision for vehicles" patch? Stand already has a builtin feature for this (vehnocol), it would seem wiser to simply use that.

[Polyester-ak-Parci]

Ваше объяснение бессмысленно. Это байтпатч, а не хук. Кроме того, в чем именно смысл этого патча «отключение столкновений для транспортных средств»? В Stand уже есть встроенная функция для этого ( vehnocol), было бы разумнее просто использовать ее.

Your explanation is nonsensical. This is a bytepatch, not a hook. Also, what exactly is the point of this "disable collision for vehicles" patch? Stand already has a builtin feature for this (vehnocol), it would seem wiser to simply use that.

yes. in the example that I have given here, this is a byte patch. I need the ability to write to any place in memory to implement functions that are not in the stand. and I want to realize them for myself. just please return the ability to write to any place in memory. in any case, it gives more options for the lua api. if you don't want it to hurt other users who don't understand what this feature does, just hide it as I mentioned earlier.

[Sainan]

You still have not given any reason for why this is needed.

[Polyester-ak-Parci]

You still have not given any reason for why this is needed.

What reasons is good for u?

[Sainan]

Tell me a problem you can't solve by any means other than to write to executable bytecode sections.

[Polyester-ak-Parci]

Tell me a problem you can't solve by any means other than to write to executable bytecode sections.

Hook game function

[Sainan]

That's not a problem

[Polyester-ak-Parci]

That's not a problem

That's main problem for me

[Sainan]

As I've already told you, you can simply use the builtin Stand feature to disable vehicle collision. :)

[MihaiStreames]

...but what if they don't want to only disable vehicle collision and run code that is EXTERNAL to stand?

[Sainan]

That would be a security risk. And I don't see a good reason for it.