So i have been playing around with tracking farming patches through config and have stumbled upon a problem.

 

 

Every single farming location is stored on the same config. Yes you read correctly, 

Config 529 stores the patches.

 

The first 3 bytes are the two allotment patches and the flower patch data.

The 4th byte is the herb patch.

 

The old way they stored them prior to now was for example: config 515's 1st byte was Falador herbs, 2nd byte was canafis. (Trees were stored in a different config # and each byte was a different location)

 

Not only did the config id change but also it seems to track the current closest one only..
So if i ectophial to Canifis the config 529 sets to the data of the Canifis patch only.

If i tp to Falador the config 529 changes its values to the patches in Falador.

 

Has anyone found a workaround to this problem or is jagex really keeping this information server sided now?

Edited July 2, 20169 yr by House

So i have been playing around with tracking farming patches through config and have stumbled upon a problem.

 

 

Every single farming location is stored on the same config. Yes you read correctly, 

Config 529 stores the patches.

 

The first 3 bytes are the two allotment patches and the flower patch data.

The 4th byte is the herb patch.

 

The old way they stored them prior to now was for example: config 515's 1st byte was Falador herbs, 2nd byte was canafis. (Trees were stored in a different config # and each byte was a different location)

 

Not only did the config id change but also it seems to track the current closest one only..

So if i ectophial to Canifis the config 529 sets to the data of the Canifis patch only.

If i tp to Falador the config 529 changes its values to the patches in Falador.

 

Has anyone found a workaround to this problem or is jagex really keeping this information server sided now?

 

yeah not possible like before

yeah not possible like before

 

feelsbadman

rip

They changed it bcs its was to easy... Now its only possible to check data if you come close to a certain patch

unless you store the data and have a task that runs to all patches and stores the data and then tell the user to only farm using your script so that the data is still valid and they only need to check all patches the first time they run.

unless you store the data and have a task that runs to all patches and stores the data and then tell the user to only farm using your script so that the data is still valid and they only need to check all patches the first time they run.

 

What are you even saying?

This was handy so that you can see if your herbs were diseased or done growing. Caching data is useless pretty much.

What are you even saying?

This was handy so that you can see if your herbs were diseased or done growing. Caching data is useless pretty much.

 

if you wanted to see if anything was at the patch, but either way it looks like your out of luck.