Make a new custom script.. type in "dcSetColor(dialogitem, miiijok" and let it scan it and wait for the error window to come up. NOTE: THIS PART WILL TAKE TIME...Next highlight ALL of the script shown, copy, make a new script, paste...your done. NOTE: DEPENDING ON HOW MANY TOTAL TRIGGERS YOU HAVE THE SCRIPT WILL CONTAIN FROM 1-40,000 LINES. 30 TRIGGERS WITH 5 LINES EACH WILL CONTAIN ABOUT 1000 LINES.
//--------------------------------------------------------------------------------------------------
// Trigger: RTS to EX Unit Camera
//--------------------------------------------------------------------------------------------------
bool gt_RTStoEXUnitCamera_Func (bool testConds, bool runActions) {
// Actions
if (!runActions) {
return true;
}
Make a new custom script.. type in "dcSetColor(dialogitem, miiijok" and let it scan it and wait for the error window to come up. NOTE: THIS PART WILL TAKE TIME...Next highlight ALL of the script shown, copy, make a new script, paste...your done. NOTE: DEPENDING ON HOW MANY TOTAL TRIGGERS YOU HAVE THE SCRIPT WILL CONTAIN FROM 1-40,000 LINES. 30 TRIGGERS WITH 5 LINES EACH WILL CONTAIN ABOUT 1000 LINES.
@Xkiller9000
Here is an example...from a basic trigger i turned it into this (this is part of a 30,000 line script)
//--------------------------------------------------------------------------------------------------
void gt_SetFALSEforSkills_Init () {
gt_SetFALSEforSkills = TriggerCreate("gt_SetFALSEforSkills_Func");
TriggerEnable(gt_SetFALSEforSkills, false);
}
________________________________________________________________________________
________________________________________________________________________________
//--------------------------------------------------------------------------------------------------
// Trigger: RTS to EX Unit Camera
//--------------------------------------------------------------------------------------------------
bool gt_RTStoEXUnitCamera_Func (bool testConds, bool runActions) {
// Actions
if (!runActions) {
return true;
}
PlayerGroupLoopBegin(gv_aLLY);
while (!PlayerGroupLoopDone()) {
if ((UnitIsSelected(UnitGroupUnit(UnitGroupFilter(null, PlayerGroupLoopCurrent(), UnitGroupSelected(gv_pLAYER), UnitFilter((1 << c_targetFilterGround) | (1 << c_targetFilterLight), 0, (1 << c_targetFilterStructure), 0), 0), 1), gv_pLAYER) == true)) {
TriggerExecute(gt_TPSEXUIOn, true, true);
TriggerExecute(gt_TPSEXSmallLandUnitCamera, true, true);
CameraUseHeightSmoothing(gv_pLAYER, false);
}
else {
}
@Xkiller9000: Go
...what?
This seems like a very roundabout way to do something we already know how to do.
The auto-generated trigger script sucks -_- There's a lot of code that could be recycled but isn't when it's auto generated.
30-40k lines is just ridiculous.. In pure galaxy I do believe the same effect can be achieved with under 10k lines.
Heh, its MUCH better than Jass back in WC3, where like every Gui function had its own wrapper.
you don't need to create an error O.o
there is a menu button to show the code. ctrl+f11 if I remember correctly
@Kueken531: Go
I always lol'd at those two wc3 functions :D