Gatherer v0.9 [Roster 1.7.3 addon]

This version has many changes!

First off the urls are all localized; this includes Zone images, and Zone selections.

Configuration changes for non-English -> array.php

Change only the full name and leave the index name.

For those of you with image location issues or even wrongly named files. Delete your current images and upload the packaged. I strongly recommend everyone do this.

The database has changed. In order to speed queries and move to a Normalized database we have removed columns method, uploads and nodeName.

Uploads might or might-not return to the database structure.

Duplicates check on upload has not been implemented.

SPECIAL THANKS:

Zeryl and Zanix for the quick localization fixes and the late night chit chat.

404 Error

Yeah sorry about that try again, I posted an update too soon...

MAJOR CHANGES!!!

Please delete all files you currently have and drop your database.

This is from scratch, all files changed, language localization, images added and renamed...

ENJOY!

Show Zanix & Zeryl some love, localization changes in a matter of hours :-D FAST PARSE & FAST LOADS!

Need volunteers to translate the language files.

Please check manually for duplicates, might still be an issue.

The way I set up the table and the queries, there should NEVER be a true duplicate.

The real problem with dupes, is that the coords are so presise, that if one user uploads
x=0.2365
y=0.865

And the next user uploads
x=0.2364
y=0.865

They are not counted as dupes

What we need is to work out a range, or "Dupe Zone"
When a value is +- (a certain amount) to what we already have in the db, then skip it
It may also be a good idea to make the xPos and yPos fields in the db float values, instead of varchar(10)

Foxy wrote:Need volunteers to translate the language files.

I think tomorrow i can release a deDe translation here :bigsmurf:

Also, languages/addon.php should not exist
All localization is in it's own file

Zanix, I can verify there is duplicates... As for the "dupe zone" I'm checking with some mod authors that have this in their todo lists...

If there is a range, I'm sure it is a very small one and perhaps a round to the nearest whole number would be fine?

Only problem, is that how precise should it stay. I mean, I don't recall how much .001 is in WoW, but I'm sure there is a reason the precision is there.

What about an external process that can be run occasionally, and will pull all rows, and do some data checking. Not sure how time consuming that would be though.

External like a a cron job?

Ok I went looking through the gatherer lua files to see what I could dig up... And here's a basic explanation shamelessly stolen from gatherer and Astrolabe (a library gatherer uses).
We'll take a mithril node at the top of my database for an example it's located at x=0.19387744, and y=0.60970711 and this is a mine in azshara so when you're reading the new data file and we get to a mine in azshara we would do an sql select query where the map, zone, nodeType, and nodeTypeWord are the same and it would return that node.
So we have a new coordinate uploaded that is located at x=0.19399000 and y=0.60842301 so lets see if they match up with the following formula:

Code: Select all

xDelta = (x2 - x1) * 1002;
yDelta = (y2 - y1) * 668;
dist = sqrt(xDelta*xDelta + yDelta*yDelta);


So using my example numbers above:

Code: Select all

xDelta = (0.19399 - 0.19387744) * 1002
yDelta = (0.60842301 - 0.60970711) * 668
dist = sqrt[(0.11278512 * 0.11278512) + -(0.8577788 * -0.8577788)]
dist = 0.865161807


if dist is greater than or = 1 then you've got a unique node. If it's less than or equal to 1 like in the case above where dist would be 0.865161807 then the node can be considered a duplicate.

Now I might be misinterpretting the way this is done. But that's what it looks like to me. I'd say code it up, backup your gatherer.lua savedvariable file and go find a mine that's already in there, but just before tapping it use the gatherer command to clear all node information to wipe the data clean then mine it. It should then record the gather to the savedvariables with a different location than before since gatherer takes the precise position the player is at as the location of the mine.

update file??

Is there a update.php file so this can be added to the upload.

Vasting wrote:Ok I went looking through the gatherer lua files to see what I could dig up... And here's a basic explanation shamelessly stolen from gatherer and Astrolabe (a library gatherer uses).
We'll take a mithril node at the top of my database for an example it's located at x=0.19387744, and y=0.60970711 and this is a mine in azshara so when you're reading the new data file and we get to a mine in azshara we would do an sql select query where the map, zone, nodeType, and nodeTypeWord are the same and it would return that node.
So we have a new coordinate uploaded that is located at x=0.19399000 and y=0.60842301 so lets see if they match up with the following formula:

Code: Select all

xDelta = (x2 - x1) * 1002;
yDelta = (y2 - y1) * 668;
dist = sqrt(xDelta*xDelta + yDelta*yDelta);


So using my example numbers above:

Code: Select all

xDelta = (0.19399 - 0.19387744) * 1002
yDelta = (0.60842301 - 0.60970711) * 668
dist = sqrt[(0.11278512 * 0.11278512) + -(0.8577788 * -0.8577788)]
dist = 0.865161807


if dist is greater than or = 1 then you've got a unique node. If it's less than or equal to 1 like in the case above where dist would be 0.865161807 then the node can be considered a duplicate.

Now I might be misinterpretting the way this is done. But that's what it looks like to me. I'd say code it up, backup your gatherer.lua savedvariable file and go find a mine that's already in there, but just before tapping it use the gatherer command to clear all node information to wipe the data clean then mine it. It should then record the gather to the savedvariables with a different location than before since gatherer takes the precise position the player is at as the location of the mine.

Wow, nice research. I'll see if I can get something going for a backend process to do this per continent.

Thanks a ton for that info.