We hope you had a good time celebrating the spooky season! We’re back with another Pulse and we’ve got more things to go over, talk about and share. Let’s get into it!
It has been exciting to see the overwhelming response to October’s Community Pulse and the various discussions that have come from it. That said, our team took the time to read the responses, and we’d like to address some points to reduce ambiguity and confusion.
Last month’s FAQ about the PLA and our IP enforcement policy kicked off much discussion in the community, and we wanted to take a moment to clarify what we outlined in that post. While to some it might seem that our responses contained a policy change, FiveM has always encouraged creators to respect IP and not infringe other parties’ rights when developing mods for the platform. We appreciate everyone’s understanding on this as we move forward.
After last month’s focus on FiveM, some of you have expressed concerns about our plans for RedM, as there was very little mention of it in last month’s Pulse. Rest assured, we are not planning on abandoning RedM – quite the contrary! The job listings we’ve mentioned are for both FiveM and RedM. Under the hood, RedM is far more challenging to work on than FiveM but as stated in last month’s Pulse, we plan to leverage the Rockstar Games team’s knowledge to help improve it in the future.
Following the updates to our PLA and our statement in September’s Pulse, there has been some confusion around the use of non-adult/minor pedestrian (ped) character models on our platform. First, we want to clarify that any depiction of an in-game model under age 18 is considered a non-adult ped model. Using these models is prohibited under the PLA in any context or scenario; there is no exception for “character age-appropriate” roleplay. All non-adult ped models must be removed.
In light of Microsoft’s end of support for Windows 7 and Windows 8 operating systems, FiveM will cease to officially support these operating systems by the end of January 2024. To prevent any future interruptions of service and ensure continued access to the latest platform features, we recommend Windows 7 and 8 users upgrade to a supported operating system as soon as possible.
As we continue to make improvements across the board, our team is still focused and committed to the development of our anti-cheat systems. A reminder that you can help us out by submitting reports of cheat software you come across to the support platform with the following information:
- The name of the cheat software
- An archive containing the cheat software executable(s)
- Source of the cheat software, i.e., where did you get it (e.g., Discord server, website, YouTube video, …)
Our team is, as always, hard at work with development! However, most progress is being done internally to optimize workflows and review legacy code, and for good reason, as it will make future development much easier and quicker.
We’ve pushed out a service to detect and notify when your server’s license key has been leaked to the public on GitHub, which should go live by next month. You can find out more on the article in our support portal.
While it was not quite ready to share this month, we have a new and improved version of the txAdmin UI in the works, which will be ready in time for the next Pulse. Stay tuned!
]tweak(gamestate/server): allow blocking phone explosion events
Dillon Skaggs (2):
]fix(native-decls): fix declaration for NETWORK_GET_VOICE_PROXIMITY_OVERRIDE_FOR_PLAYER
]tweak(docs/building): add note for people using Python 3.12+
]tweak(streaming/five): standardize usage of
]feat(rdr3): support for
]tweak(net/five): shared method to get net object from entity
]tweak(net/five): improve player talking hook
]fix(net/rdr3): ignore certain ped model sync blocking tunable
]fix(core/rdr3): train config index crash workaround
]tweak(client): remove IPFS and gRPC
]fix(gta-net-five): Construct CPlayerInfo for g_player31.
]tweak(gta-net-five): fix GTA_FIVE ifdef’s
]fix(scripting/lua): error when awaiting a rejected promise
]tweak(server): scriptless startup notices
]fix(server): fix startup notices linux build
]tweak(scripting/v8): HashString instead of hardcoded hash
]tweak(scripting/lua): cleaner INVOKE_FUNCTION_REFERENCE hash usage
]tweak(scripting/lua): call GetResourceName instead of repeating its code
]tweak(font-renderer): remove useless file, move it to FontRendererImpl.cpp
]tweak(resources): changes for retail builds this is required for upcoming internal changes
]fix(resources): don’t include InternalResourceImpl.h for server
]tweak(client): don’t look for ‘-’ while checking for pure level this will allow users to specify pure mode levels in protocol links again, this is not a proper solution but will work as a temporary one for the time being
]fix(resources): assign m_rootPath if adhesive isn’t loaded hopefully last edge case i haven’t thought about
]Merge branch ‘pr-2235’
]Merge branch ‘mr-127’
]fix(nui/core): allow sdk input callbacks only when in sdk mode
]tweak(ext/cfx-ui): use ASID instead of first available account identifier for matomo
]tweak(ci): refactoring build scripts
]fix(server/gui): ‘FXServer/unknown’ in console title
]tweak(server/gui): add txAdmin suffix to console title
]Merge branch ‘adhesive-rebuild-4’ into ‘master’
]Merge branches ‘mr-129’ and ‘pr-2206’
]Merge branch ‘mr-133’
]Merge branch ‘pr-2229’
]Merge branch ‘pr-2230’
]Merge branch ‘pr-2243’
]Merge branch ‘pr-2255’
]Merge branch ‘mr-136’
]Merge branch ‘mr-138’
]Merge branch ‘mr-139’
]Merge branch ‘pr-2238’
]Merge branch ‘mr-140’
]fix(build): update mojo files for python 3.12
]Merge branch ‘pr-2263’
]Merge branch ‘pr-2262’
]fix(clrclore): ignore captured traces if null
]Merge branch ‘pr-1623’
]Merge branch ‘pr-2114’
]Merge branch ‘pr-2130’
]Merge branch ‘pr-2267’
]Merge branch ‘mr-132’
]Merge branch ‘mr-142’
]Merge branch ‘mr-144’
]Revert “fix(resources): assign m_rootPath if adhesive isn’t loaded”
]Revert “fix(resources): don’t include InternalResourceImpl.h for server”
]Revert “tweak(resources): changes for retail builds”
]fix(server): read object id instead of a single bit on CVehicleHealthDataNode
And that wraps up this Pulse! See you all next month!