Since it won't let me quote. I am allowed to make macros as long as they do not automate any process by which you can make money, so auto farming macros or auto-clickers for exp. I am also not allowed to sell macros for ecodollars as they can be considered not "ECC related".

The macro I am suggesting I could make does not aid the process of making money but rather the process of destroying spawners, which does not result in direct economic gain. If anything it raises exp prices meaning that if you farm exp it is more valuable.

I am also not charging for this macro and am willing to distribute it freely (though donations would be nice :p) therefore not profiting of something not ECC related.

So I believe that I am allowed to make this macro. dork1877 you can sum this up in 3 words for me later.

 

as long as it doesn't spam /near, it's fine to use a macro like that.

 

By spam, I think he means using it multiple times a second. If you wait a few seconds between uses, no problem.

 

So will anyone upload screenshots and instructions of how to use /near to find spawners so I can start working on a macro?

 

Tanstaafl explained it earlier

No screenshots though, but this should suffice.

 

When you type "/near", there shows a list of people within 500 of you.

rockboy(40m), dork1877(125m), andrewkm(308m)

If no one is near you, then it just says: none

I'll post 2 screenshots in a few moments.

OK here are 3 quick shots so you get the idea.

 

Here is my rough plan. I make it echo /near and then store all values in an array. I then wait a few seconds and then do /near again. The values are compared and any distances that stay the same are assumed stationary and at a spawner. I then make the player move 1 block in each direction, each time doing /near and recording the results in an array and through some maths I can figure out the co-ordinates of the player.

It is fairly straight forward, I just need to clarify one thing. When it says "m" after the numbers, I assume though it means meters it is actually referring to number of blocks?

 

add to dork's short one:

if can't get any closer, turn 90 degrees and repeat.

 

Yes, number of blocks.

 

yes, it refers to number of blocks. supposedly, blocks are 1 meter cubed.

Don't forget that we are working in three dimensions and you have to account for the y-axis too.

I would have your script move 10 blocks in each direction instead of 1. moving just 1 is too small when the person is up to 500 meters away.

 

How is it we can work out where a player is in relation to yourself if it includes the y axis. Is it measured diagonally from you or across then down or up?

EDIT: Just going through the source code to figure out how to get the location of the player. Let's try and see if this will work. :p

 

%POSX% %POSY% AND %POSZ%

 

I understand, now, that it takes into account your y position as well as your x and z. However I don't understand how /near calculates the distance from the player to another player.

 

Squared distance.

http://en.wikipedia.org/wiki/Euclidean_distance#Three_dimensions

 

It's straight line distance rounded to nearest whole (m). This is why moving 1 block at a greater distance means almost nothing.

 

The macro will be able to calculate the players that are standing still and the direction in which to walk in but then there is a small problem. The way pythag works, for those who don't know, is it requires two sides of a so called right angled triange to find the third. As kuke explain /near is calculated using pythag. This presents us with the task of having the find a second side of the triangle in order to calculate the exact position of the player. I have made a diagram showing you what must be done after the macro has calculated the direction in which the player is.



As you can see the time wasted going the same distance away from where the player is exp farming is quite significant therefore reducing the effectiveness of making a macro to do the job.

Here is my idea. I make a macro that simply calculated the direction in which the player must travel to get to the nearest idle player.

Making one that calculates the exact location is couter productive and so I see no reason in making one unless someone can give me a reason.

I understand that what I have written may be confusing, as it is past midnight and I am not able to phrase my points in the easiest to understand way due to being tired. If you don't really care about my reasoning here is my point.

Making a macro to pin point a users exact location would be counter productive so I suggest that a macro to lead you in the direction on the nearest idle player is the best option.

 

Whoa... That's confusing for me xD