Problem:
Currently with how scenarios and sp_manifest file(s) are handled, it’s very easy to “break” world scenarios, including animal and pedestrian behaviors.
Many solutions exist that are very rudimentary or can break without any warnings or observable issues.
For example, running two sp_manifest files will break scenarios, there is no obvious documentation about this, and many MLO/map makers will do this to replace scenarios on the map. People who are not experienced with this relatively niche area of map design will run multiple MLOs with separate sp_manifest files, breaking scenarios and world spawns.
This can be solved by combining them in codewalker for example, but if a scenario file included in this package is broken, it breaks world spawns and scenarios as well.
Additionally, we can run replacements for all scenarios, but most of these are out dated/using incorrect scenarios and requires continuously editing and testing the changes.
Testing for this is really difficult, as an sp_manifest must be loaded on server start, making troubleshooting difficult and time consuming.
Suggestions:
- In beta or canary mode, print if multiple fxmanifest files have the file loaded.
- Allow loading of multiple sp_manifest files, which allows more than 1 to be run, but not to conflict
- Give warnings for broken/bugged scenario files.
Additional:
I don’t know how this would be done from a technical perspective, but it’s a widespread/common issue in Fivem that affects many communities, without them knowing it.
Making world scenarios and animal spawns easier to handle would be a big help, since the general game world is dead without them.