There doesn't seem to be an exclusion function for tags.

Do not circumvent moderation by using the forums.

Posted on Discord but not here yet, so:
Recently I realized fInitialDriveForce should be approximately N*m / kg.

• Horsepower is a rather impractical measure, especially if talking about how a car is moved - and it's a function of torque and RPM.
• GTA doesn't do RPM, but does have a force driving the vehicle, or just the end torque - which is not dependent on wheel radius, so the value represents the torque applied at the tire.
• While horsepower increases proportionally with RPM, torque stays generally flat-ish. GTA's force at the wheels is (completely) flat (until 0.8 RPM where it starts dropping).

So this makes a case for torque. However!

• It can be observed larger vehicles have lower values in order to accelerate slower, while you'd expect higher raw torque.
• Some sporty light vehicles have relatively large numbers, which don't coincide with what their actual output would be compared to bigger vehicles which should output a ton of torque.

Finally, plugging in the (peak) torque/weight number results in acceleration times that are comparable with actual data, and it's consistent for both large vehicles and small vehicles, either powerful or weak. It's not perfect, but remember many variables can influence basic acceleration - tire grip, drag, GTA's tire/suspension physics (curb boosting) and imperfect terrain. It's a good decent starting value though, for consistent realistic handlings.

The default asi loader that comes with ScriptHookV or OpenIV should block access to GTA:O, so you can't accidentally hop onto GTA:O.

It's just CloudFlare rate-limiting. Just come back in a little while and continue browsing.

And probably don't mass-download/open a bunch of mods/tabs.

This is not how you request approval review.

Moved to the correct section.
Removed the offensive Telegram username.

@JohnFromGWN
No reason if the native is known, but unknown natives are still shown as their (hexadecimal) hashes.

The decompiler doesn't know the enum name things so they just show their value as numbers instead of the proper names.

@JohnFromGWN
OP used a decompiler (dnSpy, dotPeek or something) on a .NET script mod. These tools sadly don't seem to contain options to display types as hexadecimal, so when you're going around trying to understand how something works or trying to edit the script, this process has to be repeated for each native hash.

The value (including the negative sign, without the L suffix) can just be thrown into Windows' calculator, which spits out a copyable hexadecimal number.

It can then be correlated to its name, if it has been found, by manually searching natives.h or, what I prefer to do, use a native DB with search function.

See https://forums.gta5-mods.com/topic/14021/mod-approval-thread