Thargorff,
Between you and REEFHAWK, you two did 99% of testing and great feedback. This project would still be a dream without both of you helping. Much appreciated.

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...

Like I stated in the OP...I can basically downlaod and click play...what you posted I'd have better luck reading and understanding what my Dr. writes on my perscription lol (that's impossible too) lol

I do appreciate your reply but that is way way way above my knowledge or scripts (I try messing with it it'll never work again)...was hoping for "yeah, change that 60 to 20 and your good 


I'm gonna send you a pm....

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

1. while *badtilegone = #false
2.  {
3.  ; make sure you don't lose the line after the while statement by having this comment in a block
4.  }
5. event macro 22
6. ; wait 60
7. set %TargetCursorTimeout #systime + 3000 ; equivalent period to wait 60 - both are 3 seconds
8. while %TargetCursorTimeout > #systime
9.  {
10.  if #targcurs <> 0
11.   break
12.  }
13. if #targcurs <> 0
14.  {
15.  if #contsizex = 420 && #contsizey = 280 3
16.     set %clickX #contposx + %confirmplace    ; 25 = Yes 225 = No
17.     set %clickY #contposy + 260
18.     click %clickX %clicky dmc
19.  }
20. sound warning ; Filename(wav) same Folder
21. stop
22.  
23.  

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'm going to take that as a no...LOL

I wish I could do the things you suggested...The auto fill in the x and y would be nice too....
I was honestly hoping for a quick "change 60 to 20" answer   That's about all I'm capable of when it comes to scripting...

Just trying to get a house without that "for sale, only 1.5p" in front of it...
can't compete with the other scripters, there scripts are just too fast...

Thanks for the reply
and again, I appreciate everything everyone does to help myself and others on this site.

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.

Ok, I finally figured out how this thing works...It does appear to work (can't confirm 100%, but it appears to be trying)...

I appreciate everyone here that shares their scripts!!! because god knows I can only download them and click play 

I was wondering if anyone is willing to take a look at this script and tell me does it constantly monitor the bad tile and then try and place?
I see a wait 25 in there for something???
can/is there anything that can be changed to speed up the placement after the tile goes poof?  (for instance that wait 25 changed to wait 5) not sure if that's how this script works but I have changed wait times before on other scripts...

just need to speed this thing up a little bit....or is it my internet/pc that needs more speed?

basically just curious if there's a wait time in here that can be sped up?

Thanks in advance!

If anyone reads this that has the knowledge to take a quick peak and help me out, It would be greatly appreciated...

Enjoy the rest of your day everyone! 

So, Wooden Container Engraving Tool (WCET) has 2 ingredients: boards and ingots. So this is more related to the Nunchaku solution than the tinkered items which make the item in only 1 color.
Bone armor makes items in 1 color and has 2 ingredients (leather of some color and bones) - so were affected by both issues.

I included a bunch of items that should override for the correct color of the item for tinkering. I did not test all of these.

I fixed the logic that any ingredients other than the first one would have plain (0) for it's color. I only tested the WCET and Bone armor (I made spined bone for one item and barbed bone for all the rest, but made a complete set of bods to cover a suit).

If I get more feedback, I will work at stuff next week when I am off, otherwise it will likely be the end of the calendar year to fix anything else that is deep.

New version posted 3.14.15.3