So I've gotten 1 callout plugin working - CalloutsV - but the other three I have installed don't seem to want to load properly. I've highlighted, in red, the callout plugins that are not working.
Any fixes or suggestions are greatly appreciated, thanks. I've re-installed these multiple times with no luck.

[28/07/2015 19:29:54.594] LSPD First Response: Folder is C:\Program Files (x86)\Steam\steamapps\common\Grand Theft Auto V\plugins\lspdfr
[28/07/2015 19:29:54.679] LSPD First Response: CalloutsV, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
[28/07/2015 19:29:54.716] LSPD First Response: MoreCallouts, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
[28/07/2015 19:29:54.737] LSPD First Response: StraysCallouts, Version=0.1.0.0, Culture=neutral, PublicKeyToken=null
[28/07/2015 19:29:54.741] LSPD First Response: Wilderness Callouts, Version=0.2.1.3437, Culture=neutral, PublicKeyToken=null
[28/07/2015 19:29:54.745] LSPD First Response: Creating plugin: CalloutsV.Main
[28/07/2015 19:29:54.766] LSPD First Response: Creating plugin: APIExample.Main
[28/07/2015 19:29:54.767] LSPD First Response: Creating plugin: StraysCallouts.EntryPoint
[28/07/2015 19:29:54.767] LSPD First Response: Creating plugin: WildernessCallouts.Main
[28/07/2015 19:29:54.769] LSPD First Response: [CalloutsV] Loading plugin CalloutsV version: 0.2.3a
[28/07/2015 19:29:54.769] LSPD First Response: [CalloutsV] Detecting player name from config file as: I forgot to change my name
[28/07/2015 19:29:54.769] LSPD First Response: [CalloutsV] Loaded, callouts will be registered when on duty
[28/07/2015 19:29:54.769] LSPD First Response: Callouts Plugin loaded!
[28/07/2015 19:29:54.770] StraysCallouts initialized
[28/07/2015 19:29:54.770] LSPD First Response: [Wilderness Callouts] Loaded
[28/07/2015 19:29:54.770] LSPD First Response: We have 1 callouts registered
[28/07/2015 19:29:54.771] LSPD First Response: CalloutManager initialized
[28/07/2015 19:48:52.224] LSPD First Response: Registering callout CalloutsV.Callouts.Breakdown
[28/07/2015 19:48:52.225] LSPD First Response: Registering callout CalloutsV.Callouts.TrafficCollision
[28/07/2015 19:48:52.225] LSPD First Response: Registering callout CalloutsV.Callouts.StreetRace
[28/07/2015 19:48:52.225] LSPD First Response: Registering callout CalloutsV.Callouts.Escort
[28/07/2015 19:48:52.225] LSPD First Response: [CalloutsV] All callouts have been registered correctly

From what you've highlighted, everything is fine. what's the problem? 

From what you've highlighted, everything is fine. what's the problem? 

Well I'm not getting any of the callouts from these plugins. I'm only getting them from CalloutsV

At the bottom where its registering the callouts for CalloutsV, it doesn't do that with the others.

Callouts are random, just press X on your keyboard in game and it should force a callout (if you're lucky it will spawn a callout from the other plugins)

I've played for 8+ hours with these installed and I haven't received any callouts from "MoreCallouts" "StraysCallouts" or the "Wilderness Callouts". I know for the wilderness ones you need to actually be outside the city, so I've gone to places (show in videos with the plugins being used) and spammed X on the keyboard to force callouts, and still only get them from "CalloutsV" or the standard pursuits.

I've played for 8+ hours with these installed and I haven't received any callouts from "MoreCallouts" "StraysCallouts" or the "Wilderness Callouts". I know for the wilderness ones you need to actually be outside the city, so I've gone to places (show in videos with the plugins being used) and spammed X on the keyboard to force callouts, and still only get them from "CalloutsV" or the standard pursuits.

Grab the newer version of CalloutsV, the version you are on had a known bug which blocked other callouts plugins from registering their calls. It was a complete oversight on my behalf and I fixed it in 0.2.5 and 0.2.5.1.

Grab the newer version of CalloutsV, the version you are on had a known bug which blocked other callouts plugins from registering their calls. It was a complete oversight on my behalf and I fixed it in 0.2.5 and 0.2.5.1.

Thank you for informing me, everything's working now.