I've decided to share the buildables script I made for Rise V2, it's probably the most accurate to BO2's buildables (Tranzit style) you can get from any site atm.
I do expect you have some scripting experience to follow this tutorial, I did not give a example of what to put in the buildables_bench_item() function but it's quite self explanatory.
This tutorial also assumes you're using treminaor's hintstring "fix", if you're not then I'd recommend using this:
http://ugx-mods.com/wiki/index.php?title=Hintstrings_not_updating1. Radiant1.1. Setting up spawn locations for the partsThis is quite easy to do, all you need to do is make a script_origin with a targetname of "buildable_location". Make sure you have atleast the amount of script_origins as you have parts.
Sorry but you are not allowed to view spoiler contents.
1.2. Adding a buildables benchAgain, not hard to do, make your workbench and make a script_origin with a targetname of your choice.
Sorry but you are not allowed to view spoiler contents.
2. Scripting2.1. Calling the scriptsExtract the gsc file from the zip attached to this post into mods/MAPNAME/maps.
Open MAPNAME.gsc and BEFORE _zombiemode::main(); add this:
maps\jr_buildables::PrecacheBuildables();
AFTER _zombiemode::main(); add this:
maps\jr_buildables::main();
Open jr_buildables.gsc and find the PrecacheBuildables() function, there's 2 example lines there, change "XMODEL_NAME_HERE" into whatever the name of the xmodel is you want to use for your part, just copy the line and change the string for every xmodel required. Change "MATERIAL_NAME_OF_PART_SHADER" into whatever the name of the material is you want to use as a shader, just copy the line and change the string for every material required.
2.3. Adding a partFind the buildables_parts_init() function, there's an example line there, change "XMODEL_NAME_HERE" to whatever the name of the xmodel is you want to use for your part. Change "STRING_USED_TO_STORE_PART_NAME_VARIABLE" to a string of your choice, it's used to store the name of the part for the workbench script. Change "MATERIAL_NAME_OF_PART_SHADER" to whatever the name of the material is you want to use for this part.
Find the drop_current_part() function and do the same thing you did in buildables_parts_init(). For every new part, copy the example case and change the strings to those used by the new part.
2.4. Adding a workbenchFind the buildables_benches_init() function and change "TARGETNAME_SET_IN_RADIANT_FOR_WORKBENCH" to the targetname you gave to the script_origin for the workbench in Radiant. Change the "WORKBENCH_VARIABLE" part of the two instances of "level.WORKBENCH_VARIABLE" to whatever you want to use as a variable for your workbench.
Change all 3 instances of "STRING_USED_TO_STORE_PART_NAME_VARIABLE" to the strings you gave to the parts for this specific workbench in the buildables_parts_init() function.
If you have sounds to use for your workbench, uncomment all instances of PlaySound(...); in the buildables_bench() function and change the soundaliases to whatever the ones are you use.
2.5. Make your workbench actually do somethingThis is where you're gonna require some scripting experience, find the buildables_bench_item() function and put your scripts in there. I'm not going to explain how to use it, there's 2 arguments passed to this function you will need to use but they're pretty self explanatory.
2.6. Dropping parts on deathIf you don't have _laststand.gsc in root/mods/mapname/maps yet, then copy it there from root/raw/maps. Open it up and look for the function laststand_bleedout( delay ), add this line:
self thread maps\jr_buildables::drop_current_part();
After:
setClientSysState("lsm", "0", self);
If you decide to use this, don't forget to credit me, I worked hard on this script to make it as easy to use as possible and I think I did a good job with that.
Show Posts
Triton, Lossy, Purity (some nub friends of mine) and me facepalmed (and had a giggle) after finding out what was wrong with it.
