Skip to content

feat(extra-natives/five): GET_TRAIN_TRACK_INDEX #3351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Ehbw
Copy link
Contributor

@Ehbw Ehbw commented Apr 20, 2025

Goal of this PR

Introduces a way for client scripts to know which track a train is currently on. As with track switching a train can change track index from where it was originally created on. Requested by GlitchDetector

How is this PR achieving the goal

By introducing GET_TRAIN_TRACK_INDEX to allow client scripts to retrieve the trains current track index.

This PR applies to the following area(s)

FiveM, Natives

Successfully tested on

Game builds: 1604, 3258

Platforms: Windows

Checklist

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

Fixes issues

@github-actions github-actions bot added the triage Needs a preliminary assessment to determine the urgency and required action label Apr 20, 2025
@dalekenium-cfx dalekenium-cfx self-assigned this Apr 22, 2025
@dalekenium-cfx dalekenium-cfx added the ready-to-merge This PR is enqueued for merging label Apr 22, 2025
@dalekenium-cfx
Copy link
Contributor

I feel like I'm cursed to always approve train-related PRs. 😋

Simple enough. Looks good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge This PR is enqueued for merging triage Needs a preliminary assessment to determine the urgency and required action
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants