The Loot

Hoppah and my friend managed to dig out the issues I was running into, so I've got the scripts 100% now. I'm assuming adding even more vehicles would be pretty easy, and that sounds like an interesting script. I'm also going to start adding random checks to other scripts like the Call Ambulance and Call Engine buys to get some variety and eliminate the scripts to call specific vehicles and just have them be dispatched if the map vehicles aren't available. Here's the script; it has two commands, slightly different (the second calls a scout and negotiator in a Bear instead of just SWAT in a Bearcat). LACallSWAT.rar Note: Prototype file names may need to be changed.

Actually, a little pondering (and advice from a friend who actually studied some scripting), and I've got it, and, thanks to Hoppah, I hopefully have another set up like the Light Force where two vehicles can be called if desired.

Ah. that could do it; I'll give that a try later. Edit: Yep, those missing brackets were causing the crash, and then with some help from a friend who has actually studied scripting, and some trial and error, everything works just fine now. Ended up having another weird glitch, though, where all the "else if (!BuyTruckOnly)" lines from each random went off all together, but a quick "&& Random == #" fixed that. While I have your "ear", could you take a look at this script? It gets to finding the vehicle on the map and calling the crew, but they don't enter the vehicle nor does it move to the command position. I wonder if something in the Firestation script has to be tweaked, too. Thanks again, for ALL your modding work. Looking forward to the Army mod!

Double

Still crashing. Should the sections look like this? bool BuyTruckOnly; int Random = Math::rand()%8; if (Random == 0 || Random == 1 || Random == 2) { System::Log("Buy SWAT"); BuyTruckOnly = false; bool BuyTruckOnly; else if (Random == 3 || Random == 4 || Random == 5) { System::Log("Buy SWAT"); BuyTruckOnly = false; bool BuyTruckOnly; else if (Random == 6 || Random == 7 || Random == 8) { System::Log("Buy SWAT"); BuyTruckOnly = false; Everything loads fine without this script, so I don't believe that would be it as that script has never caused problems before this. Here's the script file: http://www.4shared.c...LACallSWAT.html

Making a script to call SWAT units onto the map, with a random function for vehicle choice. That was working fine, but when I used the Light Force command as a guide to make a command with two units, the game and editor crash during load. Nothing seems to be specified in the log. Any thoughts? Logfile Script

Quincy, how would someone put together a randomizer in choosing the Prototype to spawn in the script? I've made separate Call SWAT scripts for the UMPC, UMDC, and the SWAT SUV. They all come from the same place with the same passengers, so a single script that would randomly choose between them would make more sense (as long as we can make the "n.SetSpeed" line dependant on the Prototype selected).

Everything works fine at start (though I have it disabled for every vehicle but the command ones now), and when alarming the station, but using the call command is what the problem is.

For the siren, open up LASiren, add a line like "const char PROTO_VEHICLENAME[] = "mod:prototype path"; Then go down and find a line like "StrCompare(v.GetPrototypeFileName(), PROTO_ATF_CV) == 0 ||" for a vehicle with the same siren you want for the new one, and add the line "StrCompare(v.GetPrototypeFileName(), PROTO_VEHICLENAME) == 0 ||" For the crew, you have to edit the XML file to allow which crew are available to add to the vehicle, and you can either make a default number that will always be selected, or have the vehicle be empty so you can click on which crew you want.

An update, finally. I got the script to finally find the vehicle on the map, and to dispatch the crew from the station, but they don't enter the vehicle, nor does the vehicle move to the spot it's commanded to. Out of the frying pan, and right into the next one. I almost shouted for joy when it said "Vehicle Dispatched" and the crew came out, but that joy didn't last long. If I could finally get it to work correctly, I could do the same for all the other vehicles I want to modify... *sigh*

Oh, that is pretty sweet!

Units in the game ignore traffic lights anyways, so there really wouldn't be a point.

The two ways to do would be to change the path during install, or just move the mod folder to the right directory afterwards. Then you can just zip up the whole folder and ditch the installer.

You made sure to activate the mod from the main menu before playing?

Did you check to see if the path it installed to was actually the right one? Some mods may install either for 911FR, which is under WizardWorks, or EM4, under Sixteen Tons Entertainment.

I think that was the only one I ran into, but I'm not sure; I may have not gone through ALL the units to see if every other one didn't have a bugged command for it.

There are some units with a GoToFireStation command that are not supposed to, and do not work correctly. Might as well load up the editor and remove that command from the vehicle.

Does the logfile show any errors?

Using the Battalion and EMS Captain vehicles would work, also. Having an issue with my Call Commands not showing up when I deploy the post. Scratch that, I found the differences between the Post Commands and the regular commands. Quincy, do you happen to know how the script line "n.SetSpeed" numbers compare to the unit.xml speed? I've changed the values of most units in the xml files, but I'd like to set the script lines to be the same for all of them, too. I have to send all units on map back to HQ at the beginning to get them to reset to their new speeds (I think, I've never actually tested it).

Hmm, that's one way to do it, though I was hoping for the something like the method used by default commands to staff and send vehicles.

Sounds very nice. It's possible to just leave these around on the map, right? Be interesting to eventually use these instead of the normal menu for sending vehicles on the map. Another quick script thought for when you start adding on-map calling to new scripts: a script that is dependent only on the prototype of a vehicle, and it not having "blue lights" enabled (so only idle vehicles would be chosen), instead of vehicles colliding with certain VOs. That would make calling ANY vehicle on the map pretty easy without having to dig too much into all the info needed. I'm not sure how spawning crew would work without specifiying all the VOs, but maybed it can choose the nearest crew spawn VO.

Thanks a bunch for doing this work. Kind of got discouraged when my tweaks weren't panning out, but hopefully using yours as a base should be more successful, I look forward to hopefully being able to finally call the SWR, HRC, Brush, Foam, and HES without needing to manually crew and send them.

Ah, that's an interesting way to go! Nice job!

Well I restored the line (I don't remember why I removed those): if (StrCompare(aCar->GetPrototypeFileName(), OBJ_SWR) == 0 && aCar->GetPlayerMP() == Caller->GetPlayerMP() && !aCar->HasCommand(DUMMY_VCALLED) && (aCar->HasCommand(CMD_STANDBY_OFF) || aCar->IsCollidingWithVirtualObject(VO_SWR))) But still no luck. Hopefully when you release the Chief and Captain I can do a quick change to those scripts for the other vehicles, as long as you get both station's command vehicles done.