Nice, always wondered how they managed to place so fast.
To place new house, we are still have to wait. The timer never the same,
The house placement rules have not changed since this worked. I don't IDOC, so I can't confirm that, but considering how easy it is to locate an IDOC since it is announced by the town NPC's on OSI - it is easily confirmed.
The only wait I see is the "wait 60" after event macro 22.
So that wait is waiting for the target cursor to show up. That code should be cleaned up to end the wait cycle as soon as the target cursor shows up.
Something like this idea which you could test on other target cursor things to prove it works.Code: easyuo
while *badtilegone = #false { ; make sure you don't lose the line after the while statement by having this comment in a block } event macro 22 ; wait 60 set %TargetCursorTimeout #systime + 3000 ; equivalent period to wait 60 - both are 3 seconds while %TargetCursorTimeout > #systime { if #targcurs <> 0 break } if #targcurs <> 0 { if #contsizex = 420 && #contsizey = 280 3 set %clickX #contposx + %confirmplace ; 25 = Yes 225 = No set %clickY #contposy + 260 click %clickX %clicky dmc } sound warning ; Filename(wav) same Folder stop
Personally, I think the 'sound warning' statement is a waste of time. I would move that to the end before the stop statement. This would still give you the sound notification, but after it tries to click - especially if you are trying to combat any lag.
You could adapt similar logic to both files for the target attempt.
There is a way to automatically fill in the X and Y values of the target using the find statement results in the Main script and share those via either the registry variables or revise these to use namespace. I do not know which is quicker (namespace vs. registry).
I showed you exactly how to revise it to speed up the delay waiting for the cursor so that as soon as it appears, it will take action. Not sure what else you could need...