Add Pitch Information in the "location" or anywhere more suitable

[coredmp95]

Hello, could we have the "pitch" information in the getPlayer endpoint ?

[
{
"ID": "Char_Player_C_2147452680",
"Name": "derpierre65",
"ClassName": "Char_Player_C",
"location": {
"x": -57604.6796875,
"y": 260436.1875,
"z": -3018.36083984375,
"rotation": 115.5536737696151,
"pitch": 20
},
"Online": true,
"PlayerHP": 100,
"Dead": false,
"Inventory": [
{
"Name": "Beryl Nut",
"ClassName": "Desc_Nut_C",
"Amount": 10,
"MaxAmount": 100
},
{
"Name": "Paleberry",
"ClassName": "Desc_Berry_C",
"Amount": 50,
"MaxAmount": 50
},
{
"Name": "FICSIT Coupon",
"ClassName": "Desc_ResourceSinkCoupon_C",
"Amount": 11,
"MaxAmount": 500
},
{
"Name": "Hard Drive",
"ClassName": "Desc_HardDrive_C",
"Amount": 48,
"MaxAmount": 100
},
{
"Name": "Mercer Sphere",
"ClassName": "Desc_WAT2_C",
"Amount": 1,
"MaxAmount": 50
},
{
"Name": "Wood",
"ClassName": "Desc_Wood_C",
"Amount": 51,
"MaxAmount": 200
},
{
"Name": "Hoverpack",
"ClassName": "BP_EquipmentDescriptorHoverPack_C",
"Amount": 1,
"MaxAmount": 1
}
],
"features": {
"properties": {
"name": "derpierre65",
"type": "Player"
},
"geometry": {
"coordinates": {
"x": -57604.6796875,
"y": 260436.1875,
"z": -3018.36083984375
},
"type": "Point"
}
}
}
]

[porisius]

I will see what I can do tonight, but pardon my curiosity, what is the use case for this?

I don't have an issue with it, but I'm scratching my head wondering what this can be used for.

It is liable, if I remember the code correctly, to add pitch to all actors because the location data is a library function. Just a heads up.

[coredmp95]

Well, I am currently trying to create a "bot" purely for a research project exploring behavioral agents in a rich environment. The goal is to limit the "cheats" the bot needs to use in order to play. For this, it has to be able to know where it is looking so it can place buildings and interact with them.

I have created (using Claude) the changes in the fork I made. I also added some corrections for a race condition in the connection part and a player name problem.

[Bread-Ch4n]

Wouldn't a dedicated mod be better for the bot tho? I mean pitch could be used for the head pointing on a 3d map later on as well.

[Bread-Ch4n]

Missclick 😅

[coredmp95]

The final version of the bot is intended to be fully client-side and will rely on computer vision (likely YOLO) to ensure it only uses the same visual information a normal human player would have access to. Consequently, relying permanently on a dedicated mod to feed data to the bot would bias the research project, as it would grant the agent access to perfect, non-visual information.

However, to start with a simpler case, I'm currently using FicsitRemoteMonitoring to bootstrap the project and get world data. At the moment, the bot runs on Linux, uses a low-level keyboard simulator to send inputs, and is already capable of moving around the map—though its movements are still quite clumsy for now. It basically simulates a user who already knows the map layout.

To actually place buildings or parts, it needs to point to the correct in-game coordinates, which requires knowing the player's current pitch. That's why having pitch in FRM is a huge help for this initial phase.

Down the road, the plan is to drop FRM entirely and switch to pure vision, though I'll probably need to invest in something beefier than my current RTX 3080 Ti (ideally an RTX 5090 if prices ever drop!) to run YOLO inference smoothly alongside the game.