Rich

You probably need to add the Albo1125.Common back as well, yes. The RAGENativeUI.dll included with his files is old. Use this one instead: https://github.com/alexguirre/RAGENativeUI/releases/tag/1.7

The .dll and .ini, yes. I'm going to assume if the crash was from Traffic Policer, it was due to the ambient events. You can disable the ambient events in the .ini to stop that crashing (if it was indeed the cause, I don't know without looking at a log).

It works for me and many other people. You never posted the log from your original crash, which you believed to be caused by Traffic Policer, so we never actually saw the cause. Someone just told you to remove it because it's old.

Chill Callouts requires Traffic Policer. You need to either reinstall Traffic Policer or uninstall Chill Callouts.

Also the crash in that log was caused by First Callouts.

Seeing your actual code is more helpful than you telling us what it looks like. The Process function is where you put the "meat" of your callout - it's where everything happens after the callout is accepted.

Spawnpoint is not defined before you call it.

I don't think all the unsafe and explicit pointer stuff is necessary. Could try just the following (Natives screw me up too): NativeFunction.Natives.xA0F8A7517A273C05<bool>(spawnPoint.X, spawnPoint.Y, spawnPoint.Z, brokenVehicle.Heading, out Vector3 outPosition); brokenVehicle.Position = outPosition;

For this you'll probably have to use natives. https://nativedb.dotindustries.dev/natives Natives are called using "Rage.NativeFunction.Natives" For example, "Rage.NativeFunction.Natives.IS_PED_IN_VEHICLE(myPed, someVehicle, false)" or "Rage.NativeFunction.Natives.xA3EE4A07279BB9DB(myPed, someVehicle, false)" Some natives only work using their hash (starting at x followed by the random string of letters and numbers. For getting the shoulder of a road, you might check the "_GET_ROAD_SIDE_POINT_WITH_HEADING" native. Since it begins with an underscore, you should call it with its hash.

Neat, didn't know this. Thanks!

1. If you're asking how to programmatically start your callout in-game, LSPDFR has a StartCallout function you may find useful. 2. If you're asking if you can run your .dll through a debugger, then no, not that I'm aware of. 3. What do you mean by creating world events? Like ambient events? The Initialize function from your EntryPoint class is where you want to start doing stuff. 4. If it's an LSPDFR plugin, it goes in the "plugins/LSPDFR" folder and will be loaded by LSPDFR. If it's a standalone plugin, it goes in the "plugins" folder and will show up in the list of Rage plugins you can load on startup.

You're not assigning GetPursuitPeds to any variable. It returns an array I believe. From that collection, you need to get a single Ped to use in IsPedVisualLost.

This is not how redistribution works.

See the second part of my post.

By default, only stage 3 lighting is recognized as "sirens on" by the game. If you want to change which stage is considered "sirens on," you need to edit each vehicle's ELS XML file. Under the MISC section, find <DfltSirenLtsActivateAtLstg>3</DfltSirenLtsActivateAtLstg> and change the 3 to 2 or 1. Additionally, make sure the vehicle has the correct flags (FLAG_LAW_ENFORCEMENT and FLAG_EMERGENCY_SERVICE) in the vehicles.meta file.

OpenIV. Look up a tutorial about adding replacement and/or addon cars to GTA.

This doesn't make sense?