Set trigger that sets rally point to nearest region.

[DDofSummer]

Thought I'd repost becuase of the lack of answer in the innapropriate place.

This is still unresolved, look here

image

image

The green squares in this next pic are the regions. I want the rally points to automaticly become set to its buildings nearest green square region
as soon as the building's built.

image

 

[spencenator]

Hmm, you could scan all of the regions for distance, then find the closest one. I just made a system like this for laser beam prediction, let me write a version for you.

EDIT: this should do it justice, tell me if you need anymore clarification

• Closest Region Rally Set
  • Events
    • Unit - A unit Finishes construction
  • Conditions
  • Actions
    • Set Temp_Real = 9001.00
    • Set Temp_Loc = (Position of (Constructed structure))
    • -------- from 1 to (number of regions) --------
    • For each (Integer A) from 1 to 2, do (Actions)
      • Loop - Actions
        • -------- Region[#] is a region array, set each region to a different value of the array in another trigger --------
        • Set Temp_Loc2 = (Center of Region[(Integer A)])
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • (Distance between Temp_Loc and Temp_Loc2) Less than Temp_Real
          • Then - Actions
            • Custom script: call RemoveLocation(udg_Closest_Point)
            • Set Temp_Real = (Distance between Temp_Loc and Temp_Loc2)
            • Set Closest_Point = (Center of Region[(Integer A)])
          • Else - Actions
    • Unit - Order (Constructed structure) to Set Rally Point To Closest_Point
    • Custom script: call RemoveLocation(udg_Temp_Loc)
    • Custom script: call RemoveLocation(udg_Temp_Loc2)
    • Custom script: call RemoveLocation(udg_Closest_Point)

don't have time to test it right now, but i have faith it will work. if you see this before i test it, try it anyways

EDIT2: tested, works flawlessly as expected. Here an example of how to set up Region[#] properly, because i feel i was unclear.

• region set
  • Events
    • Map initialization
  • Conditions
  • Actions
    • Set Region[1] = Region 000 <gen>
    • Set Region[2] = Region 001 <gen>

 

[Dr Super Good]

I advise the use of jass for this due to its enhanced efficency. It would be better to store a list of X/Y vectors instead of rects due to the less calculating needed and less handles made.

 

[Bribe]

Not only fewer handles but rects allocate a <lot> of memory; exponentially higher than that of locations.

 

[Dr Super Good]

That makes no sense.... Why would they be exponentially higher than locations?

 

[Bribe]

You would think twice as high as locations, because it requires 2 more parameters, you are actually squaring it to add those parameters.

If you increase each dimension of a 10x10 room (100 area) by 2, you'd get 20x20, which equates to 400 area. Hence, instead of twice the allocation, you get four times the allocation.

 

[Dr Super Good]

You are making no sense.
Why would a rect's size vary with area?

 

[Bribe]

I don't mean area literally, I mean substitute RAM for area.

[][]
[][]     = [][][][]
           [][][][]
           [][][][]
           [][][][]

Unless Blizzard was super-efficient (which I doubt, considering their lack of consideration towards much of their other allocations), you're looking at rects allocating a minimum of four times the allocation as locations.

 

[Dr Super Good]

I doubt your calculations are meaningful.

Anyway, memory allocation goes in pages, so more memory will always be allocated when allocation is run.

 

[spencenator]

I don't know for sure, but I agree that an area would take more memory than a point, so i'll rewrite the earlier trigger.

 

[Dr Super Good]

Its still better to use X/Y instead of locations for this cause all the maths uses X and Y so retrieving them from locations slows it down.

 

[spencenator]

• Closest Region Rally Set
  • Events
    • Unit - A unit Finishes construction
  • Conditions
  • Actions
    • Set Temp_Real = 9001.00
    • Set Temp_Loc = (Position of (Constructed structure))
    • For each (Integer A) from 1 to 2, do (Actions)
      • Loop - Actions
        • Set Temp_Loc2 = Region_Center[(Integer A)]
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • (Distance between Temp_Loc and Temp_Loc2) Less than Temp_Real
          • Then - Actions
            • Custom script: call RemoveLocation(udg_Closest_Point)
            • Set Temp_Real = (Distance between Temp_Loc and Temp_Loc2)
            • Set Closest_Point = Region_Center[(Integer A)]
          • Else - Actions
        • Custom script: call RemoveLocation(udg_Temp_Loc2)
    • Unit - Order (Constructed structure) to Set Rally Point To Closest_Point
    • Custom script: call RemoveLocation(udg_Temp_Loc)
    • Custom script: call RemoveLocation(udg_Closest_Point)

This should be faster. But I did learn something new from DrSuperGood: if you want to make this EVEN faster, you can save the X and Y of the points instead of the whole location. I don't know the function right off the top of my head, but DrSuperGood could probably fill you in. Personally, I think this is plenty fast enough for your purposes. As stated, i have a *similar* system for drawing a laser beam to the closest object in front of it. It can scan 1050 points a second with zero lag; your system won't scan more than the number of regions you have, unless you complete a large number of buildings at once, and even then it won't get anywhere near the critical number to cause lag. Hope this helps