feat(rdr3/server): server-side entity/ped health natives.

[slashkeyvalue]

Goal of this PR

This PR aims to allow health-related Ped data access on RedM, by adding some new server-side natives: GET_ENTITY_HEALTH, GET_PED_MAX_HEALTH, GET_ENTITY_MAX_HEALTH.

How is this PR achieving the goal

We now parse CPedHealthDataNode in it's entirety, plus a "new" RDR3 datanode that stores ped max health data.

This PR applies to the following area(s)

RedM, Server.

Successfully tested on

Game builds: This research was based on build 1491.50

Platforms: Windows

Checklist

• [x] Code compiles and has been tested successfully.
• [x] Code explains itself well and/or is documented.
• [x] My commit message explains what the changes do and what they are for.
• [x] No extra compilation warnings are added by these changes.

Fixes issues

Collective-RedM

[slashkeyvalue]

I haven't made any updates to the native declarations yet, as I'm unsure what the ideal format should be given these changes. If anyone with more experience in documentation has suggestions or best practices, please share them.

---

ns: CFX apiset: server

GET_ENTITY_HEALTH

int GET_ENTITY_HEALTH(Entity entity);

Parameters

• entity: The entity to check the health of

Supported Entity Types

Entity Type	FiveM	RedM	Returns (FiveM)	Returns (RedM)
Vehicle	✅	❌	0 - 1000	0
Ped	✅	✅	0 - 200	0 - 150
Object	✅	❌	0	0
(Others)	❌	❌	0	0

[RUSIYAAA]

Guys just pull the button on this we are waiting to get it fixed by months now. Please do something!!!!! Why are you guys just abandon such a platform???

[mn9-29]

Hello,

We truly appreciate all the work that has gone into FiveM/RedM over the years. At the same time, it’s difficult for many in the RedM community to see fixes and contributions stall, especially when these are aimed at improving stability and combating cheats.

Could you please let us know if there’s any specific feedback, missing details, or required adjustments from our side to help move these PRs forward? Even a short update or direction from your team would mean a lot and would help keep the community engaged and motivated.

Thank you for your time and for considering the efforts of the RedM players, server owners, and developers who all want to see the platform grow stronger.

[MafiaBorn]

No conflicts on this PR - what is the hold up on it moving forward?

[AvocadoOutlaw]

Following up on this PR submitted by the RedM Collective. With the money, time, and dedication of players, server owners, and developers, fixes have been created to combat cheats and improve RedM for the entire community.

It’s disheartening to see so many pour effort into something they believe in, only for it to feel ignored. Could you please let us know if there’s anything missing, incorrect, or otherwise required on our end to get these fixes pushed through?

The RedM community already often feels like the red-headed stepchild of CFX, and seeing critical contributions stalled only reinforces that frustration. Any clarity or next steps from you would go a long way.

[StarBoyDusk]

Please listen to the community. We are still passionate about it. Don't let it die.

[outsider31000]

@slashkeyvalue when you can squash commits