Gatherer::Development

Italian nodes name via cache

elegos — Mon, 10 Sep 2012 12:52:58 +0000

Hello! I don't have all the nodes in the cache, but here are the ones I've exported from it.

["Ardispina"] = 191303,
["Trifoglio d'Oro"] = 189973,
["Deposito di Cobalto"] = 189978,
["Deposito Ricco di Cobalto"] = 189979,
["Fogliargenta"] = 1617,
["Bulboterro"] = 1619,
["Vena di Rame"] = 1731,
["Sbocciapace"] = 1618,
["Cassa del Tesoro Rinforzata in Argento"] = 207472,
["Algatorta"] = 2045,
["Scrigno di Rovinato"] = 179486,
["Grandespina"] = 1621,
["Sanguesacro"] = 1624,
["Bulbovivo"] = 2041,
["Erbalivida"] = 1622,
["Magareale"] = 1620,
["Vena di Stagno"] = 1732,
["Muschio di Tomba"] = 1628,
["Vena d'Argento"] = 1733,
["Deposito di Mithril"] = 2040,
["Orospino"] = 2046,
["Ciuffo di Khadgar"] = 2043,
["Deposito di Ferro"] = 1735,
["Erbacieca"] = 142143,
["Vena d'Oro"] = 1734,
["Foglia Eterea"] = 2042,
["Erbasole"] = 142142,
["Fiordiferro Selvatico"] = 1623,
["Foglia Onirica"] = 176584,
["Sansam Dorato"] = 176583,
["Sangue di Grom"] = 142145,
["Loto Purpureo"] = 142140,
["Deposito di Verargento"] = 2047,
["Vena Piccola di Torio"] = 324,
["Ramargento Montano"] = 176586,
["Vena Ricca di Torio"] = 175404,
["Corolla Invernale"] = 176588,
["Gloria d'Oro"] = 181271,
["Erbavile"] = 181270,
["Deposito di Vilferro"] = 181555,
["Terocone"] = 181277,
["Deposito di Adamantite"] = 181556,
["Vena di Korio"] = 181557,
["Cardomana"] = 181281,
["Vite dell'Incubo"] = 181280,
["Giglio Tigrato"] = 190169,
["Deposito di Saronite"] = 189980,
["Lingua di Vipera"] = 191019,
["Deposito Ricco di Saronite"] = 189981,
["Gelaspina"] = 190172,
["Fiore del Lich"] = 190171,
["Cassa d'Acero del Tesoro"] = 207529,
["Frammento Semprefreddo"] = 193997,
["Vena di Titanio"] = 191133,

bug report

Piney84 — Fri, 14 Sep 2012 23:02:33 +0000

Date: 2012-09-15 08:28:56
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\Gatherer_HUD\GatherHUD.lua line 400:
attempt to call global 'GetNumPartyMembers' (a nil value)
Debug:
Gatherer_HUD\GatherHUD.lua:400: Render()
Gatherer_HUD\GatherHUD.lua:634: RunUpdate()
[string "*:OnUpdate"]:2:
[string "*:OnUpdate"]:1
Locals:
hide = false
d = nil
d_squared = nil
dx = nil
dy = nil
node = nil
pct = nil
angle = nil
facing = 2.0678391456604
newangle = nil
newsize = nil
newalpha = nil
pc = 11
pz = 0
px = 0.61809504032135
py = 0.40259611606598
point = nil
scale = nil
_ = 1
_ = true
xScale = 5745.8333282471
yScale = 3831.2498779297
gridres = 250
gridressquare = 62500
maxunits = 62751
now = 1347663536
grid = { 1 = 0 2 = 0 3 = 0 4 = 0 5 = 0 6 = 0 7 = 0 8 = 0 9 = 0 10 = 0 11 = 0 12 = 0 13 = 0 14 = 0 15 = 0 16 = 0 17 = 0 18 = 0 19 = 0 20 = 0 21 = 0 22 = 0 23 = 0 24 = 0 25 = 0 26 = 0 27 = 0 28 = 0 29 = 0 30 = 0 31 = 0 32 = 0 33 = 0 34 = 0 35 = 0 36 = 0 37 = 0 38 = 0 39 = 0 40 = 0 41 = 0 42 = 0 43 = 0 44 = 0 45 = 0 46 = 0 47 = 0 48 = 0 49 = 0 50 = 0 51 = 0 52 = 0 53 = 0 54 = 0 55 = 0 56 = 0 57 = 0 58 = 0 59 = 0 60 = 0 61 = 0 62 = 0 63 = 0 64 = 0 65 = 0 66 = 0 67 = 0 68 = 0 69 = 0 70 = 0 71 = 0 72 = 0 73 = 0 74 = 0 75 = 0 76 = 0 77 = 0 78 = 0 79 = 0 80 = 0 81 = 0 82 = 0 83 = 0 84 = 0 85 = 0 86 = 0 87 = 0 88 = 0 89 = 0 90 = 0 91 = 0 92 = 0 93 = 0 94 = 0 95 = 0 96 = 0 97 = 0 98 = 0 99 = 0 100 = 0 101 = 0 102 = 0 103 = 0 104 = 0 105 = 0 106 = 0 107 = 0 108 = 0 109 = 0 110 = 0 111 = 0 112 = 0 113 = 0 114 = 0 115 = 0 116 = 0 117 = 0 118 = 0 119 = 0 120 = 0 121 = 0 122 = 0 123 = 0 124 = 0 125 = 0 126 = 0 127 = 0 128 = 0 129 = 0 130 = 0 131 = 0 132 = 0 133 = 0 134 = 0 135 = 0 136 = 0 137 = 0 138 = 0 139 = 0 140 = 0 141 = 0 142 = 0 143 = 0 144 = 0 145 = 0 146 = 0 147 = 0 148 = 0 149 = 0 150 = 0 151 = 0 152 = 0 153 = 0 154 = 0 155 = 0 156 = 0 157 = 0 158 = 0 159 = 0 160 = 0 161 = 0 162 = 0 163 = 0 164 = 0 165 = 0 166 = 0 167 = 0 168 = 0 169 = 0 170 = 0 171 = 0 172 = 0 173 = 0 174 = 0 175 = 0 176 = 0 177 = 0 178 = 0 179 = 0 180 = 0 181 = 0 182 = 0 183 = 0 184 = 0 185 = 0 186 = 0 187 = 0 188 = 0 189 = 0 190 = 0 191 = 0 192 = 0 193 = 0 194 = 0 195 = 0 196 = 0 197 = 0 198 = 0 199 = 0 200 = 0 201 = 0 202 = 0 203 = 0 204 = 0 205 = 0 206 = 0 207 = 0 208 = 0 209 = 0 210 = 0 211 = 0 212 = 0 213 = 0 214 = 0 215 = 0 216 = 0 217 = 0 218 = 0 219 = 0 220 = 0 221 = 0 222 = 0 223 = 0 224 = 0 225 = 0 226 = 0 227 = 0 228 = 0 229 = 0 230 = 0 231 = 0 232 = 0 233 = 0 234 = 0 235 = 0 236 = 0 237 = 0 238 = 0 239 = 0 240 = 0 241 = 0 242 = 0 243 = 0 244 = 0 245 = 0 246 = 0 247 = 0 248 = 0 249 = 0 250 = 0 251 = 0 252 = 0 253 = 0 254 = 0 255 = 0 256 = 0 257 = 0 258 = 0 259 = 0 260 = 0 261 = 0 262 = 0 263 = 0 264 = 0 265 = 0 266 = 0 267 = 0 268 = 0 269 = 0 270 = 0 271 = 0 272 = 0 273 = 0 274 = 0 275 = 0 276 = 0 277 = 0 278 = 0 279 = 0 280 = 0 281 = 0 282 = 0 283 = 0 284 = 0 285 = 0 286 = 0 287 = 0 288 = 0 289 = 0 290 = 0 291 = 0 292 = 0 293 = 0 294 = 0 295 = 0 296 = 0 297 = 0 298 = 0 299 = 0 300 = 0 301 = 0 302 = 0 303 = 0 304 = 0 305 = 0 306 = 0 307 = 0 308 = 0 309 = 0 310 = 0 311 = 0 312 = 0 313 = 0 314 = 0 315 = 0 316 = 0 317 = 0 318 = 0 319 = 0 320 = 0 321 = 0 322 = 0 323 = 0 324 = 0 325 = 0 326 = 0 327 = 0 328 = 0 329 = 0 330 = 0 331 = 0 332 = 0 333 = 0 334 = 0 335 = 0 336 = 0 337 = 0 338 = 0 339 = 0 340 = 0 341 = 0 342 = 0 343 = 0 344 = 0 345 = 0 346 = 0 347 = 0 348 = 0 349 = 0 350 = 0 351 = 0 352 = 0 353 = 0 354 = 0 355 = 0 356 = 0 357 = 0 358 = 0 359 = 0 360 = 0 361 = 0 362 = 0 363 = 0 364 = 0 365 = 0 366 = 0 367 = 0 368 = 0 369 = 0 370 = 0 371 = 0 372 = 0 373 = 0 374 = 0 375 = 0 376 = 0 377 = 0 378 = 0 379 = 0 380 = 0 381 = 0 382 = 0 383 = 0 384 = 0 385 = 0 386 = 0 387 = 0 388 = 0 389 = 0 390 = 0 391 = 0 392 = 0 393 = 0 394 = 0 395 = 0 396 = 0 397 = 0 398 = 0 399 = 0 400 = 0 401 = 0 402 = 0 403 = 0 404 = 0 405 = 0 406 = 0 407 = 0 408 = 0 409 = 0 410 = 0 411 = 0 412 = 0 413 = 0 414 = 0 415 = 0 416 = 0 417 = 0 418 = 0 419 = 0 420 = 0 421 = 0 422 = 0 423 = 0 424AddOns: Swatter, v4.0.3 (<%codename%>) AucAdvanced, v5.14.5335 (KowariOnCrutches) AucFilterBasic, v5.14.5335 (KowariOnCrutches) AucFilterOutlier, v5.14.5335.5335(5.14/embedded) AucMatchUndercut, v5.14.5335.5225(5.14/embedded) AucScanData, v5.14.5335 (KowariOnCrutches) AucStatHistogram, v5.14.5335 (KowariOnCrutches) AucStatiLevel, v5.14.5335 (KowariOnCrutches) AucStatPurchased, v5.14.5335 (KowariOnCrutches) AucStatSales, v5.14.5335.5335(5.14/embedded) AucStatSimple, v5.14.5335 (KowariOnCrutches) AucStatStdDev, v5.14.5335 (KowariOnCrutches) AucStatWOWEcon, v5.14.5335.5335(5.14/embedded) AucUtilAHWindowControl, v5.14.5335.5133(5.14/embedded) AucUtilAppraiser, v5.14.5335.5335(5.14/embedded) AucUtilAskPrice, v5.14.5335.5160(5.14/embedded) AucUtilAutoMagic, v5.14.5335.5335(5.14/embedded) AucUtilCompactUI, v5.14.5335.5335(5.14/embedded) AucUtilEasyBuyout, v5.14.5335.5238(5.14/embedded) AucUtilFixAH, v5.14.5335 (KowariOnCrutches) AucUtilItemSuggest, v5.14.5335.5335(5.14/embedded) AucUtilPriceLevel, v5.14.5335.5237(5.14/embedded) AucUtilScanButton, v5.14.5335.5335(5.14/embedded) AucUtilScanFinish, v5.14.5335.5153(5.14/embedded) AucUtilScanProgress, v5.14.5335.4979(5.14/embedded) AucUtilScanStart, v5.14.5335.5153(5.14/embedded) AucUtilSearchUI, v5.14.5335.5335(5.14/embedded) AucUtilSimpleAuction, v5.14.5335.5208(5.14/embedded) AucUtilVendMarkup, v5.14.5335.4828(5.14/embedded) Babylonian, v5.1.DEV.332(/embedded) BagBrother, v Bagnon, v5.0.4 BagnonConfig, v Bartender4, v4.5.3 BeanCounter, v5.14.5335 (KowariOnCrutches) Configator, v5.1.DEV.335(/embedded) Cooldowns, v DBMCore, v DebugLib, v5.1.DEV.312(/embedded) Enchantrix, v5.14.5335 (KowariOnCrutches) EnchantrixBarker, v5.14.5335 (KowariOnCrutches) Gatherer, v4.0.3 GathererHUD, v4.0.3 HealBot, v5.0.4.5 Informant, v5.14.5335 (KowariOnCrutches) LibExtraTip, v5.12.DEV.324(/embedded) MoveAnything, v13.1.2 Postal, v3.5.0 Recount, v SellJunk, v3.0.7 SlideBar, v4.0.3 (<%codename%>) Stubby, v5.14.5335 (KowariOnCrutches) TipHelper, v5.12.DEV.315(/embedded) Titan, v5.1.4.50001 TitanBag, v5.1.4.50001 TitanClock, v5.1.4.50001 TitanGold, v5.1.4.50001 TitanLocation, v5.1.4.50001 TitanLootType, v5.1.4.50001 TitanPerformance, v5.1.4.50001 TitanRepair, v5.1.4.50001 TitanVolume, v5.1.4.50001 TitanXP, v5.1.4.50001 BlizRuntimeLib_enUS v5.0.5.50001 (ck=980)

Suggestion for automatic nodes detection

elegos — Mon, 10 Sep 2012 13:34:19 +0000

I know NPCScan reads the WoW cache in order to get the rares - can't you do the same thing, searching for IDs and adding them in the savedvariables?

Made changes

PapaDoom — Tue, 31 Jan 2012 16:22:20 +0000

Hey all, I've been updating Gatherer on my own for a while now due to no offical updates. I would love to help out and get some changes in there.

So far I have Skills updated correctly and a few other minor ones. But i have next to know idea how to send in the code etc.

Archaeology Tracking

Kjasi — Thu, 30 Dec 2010 07:43:00 +0000

Hi there. Been a fan for ages, but first time posting.

Been writing addons for a while now, and I've always wanted to track Archaeology with Gatherer. Tried to do it with a Gatherer addon, but couldn't get it to work, so I directly modified Gatherer.

Attached is my modified Gatherer, complete with Archaeology Icons. I've tested this, and it works almost perfectly. The one thing I couldn't fix was that the Archaeology tracking options are inverted for some reason. (Setting the tracking option to OFF will make them appear in the Minimap, while ON will make them disappear.)

Only the enUS data has been filled for the localizations, so that will have to be done at some point.

I hope this becomes a standard feature in the next release.

Feature request: Sound notification on new node

stierlitz — Sat, 06 Aug 2011 19:15:01 +0000

Hello all,

first of all please let me thank you Gatherer developers for your awesome addon! Maybe I am posting about something which was discussed already (as this seems to me obvious and logical) but I wasn't able to google anything outside nor find anything inside this forum site related.

So I am using Gatherer daily for gathering herbs and I was thinking that it would be very useful if we would have sound signal when a new node pops-up on the minimap. What do you think?

Altered Icons for Gatherer

FrogFactory — Fri, 24 Jun 2011 05:34:27 +0000

I have played World of Warcraft (intermittently) since January 2005, and was an early adopter of Gatherer. As the addon became more detailed and impressive, I found that there was a bit of 'information overload' happening with the map tracking. It occurred to me that the problem is that the icons used to represent the various plants and ores were overly complex. Many complex icons on screen can reduce the effectiveness of what you are aiming to present.
Having identified what I perceived as the problem, I endeavoured to find a simple solution. Now originally I thought - well, use letters like chemical formulae for the nodes. But how to differentiate plants and ores? Use different fonts.
This worked up to a point, but with TBC came all these herbs starting with F and N, and again complexity was beginning to creep in. Not long after TBC I took a hiatus for 3 years - I skipped all of Wrath and the first year of Cataclysm. But I've resubbed, and Gatherer is still working, and I have new icons to boot.

I went with a simple idea - dots for ores, squares for herbs. The colour of the dot is (mostly) representative of the item being collected. I have also added in the Un'Goro crystals and soil, Sithilyst and differentiate rich and regular nodes where possible.
There's not a large number of ores to mine, so I didn't see the need for further splitting them between Azeroth, Northrend, Outland and Cataclysm. With herbs there are a lot so I took to the following scheme: a vertical divide indicates a vanilla WoW herb. A diagonal divide is an outland herb. A checker (grid) is Northrend, and a horizontal divide is Cataclysm.

Below are some screen shots of the icons in the game.

http://www.bluestar.com.au/wow/borean.jpg
http://www.bluestar.com.au/wow/silithus.jpg
http://www.bluestar.com.au/wow/thousand.jpg
http://www.bluestar.com.au/wow/ungoro.jpg
http://www.bluestar.com.au/wow/westfall.jpg

I have also put up a PDF that I made for Inscription which also uses the herbal icons.

http://www.bluestar.com.au/wow/inscription.pdf

So, if you like the look of those icons, then you can grab the zipfile here :
http://www.bluestar.com.au/wow/GatherIcons.zip
Just extract them into your Gatherer folder. They're the icons plus two lua files that I had to edit to show the Cataclysm nodes and un'goro stuff.

Cheers,

Stuffy.

[Gatherer_HUD] [Patch] Minimap Lens + Attitude Indicator.

Sinus — Wed, 02 Feb 2011 23:58:55 +0000

Greetings.

I've created two new features for the Gatherer HUD plugin, which I believe might prove useful.

The lesser of these is the Attitude Indicator, that helps you maintain a perfectly level flight.

Nothing fancy, just a bare-bones aviation instrument - a colored line extending up or down. We want our gathering rounds done as efficiently as possible, so it's best to avoid constant falling and rising, which reduces the distance covered in time. You should fly horizontally whenever possible. Available only in flight, naturally. Perhaps this deserves to be a separate little addon by itself, as it's also useful on longer trips that have nothing to do with Gatherer.

The bigger of the two features is the Minimap Lens. It combines HUD's long-range display with Minimap's tracking dots, so that you don't have to keep glancing alternatingly at the HUD and at the Minimap.

Its base is the minimap, copied and put inside the HUD area, with terrain blanked so that only tracking icons are visible (and blinking, using a cyclic texture switch). The result is that HUD icons become blinking golden dots when there are herbs or ores to harvest. No attempt to detect node activity is done, fear not, this is all purely visual.
One might observe that the minimap hardly matches the HUD's range, often set to 1000yd or more. That's why I called the Minimap placement a "Lens" - icon distances on the HUD are adjusted so that icons inside the central minimap tracking area are displayed on a smaller scale, while those outside it keep using the long-range scale. This results in a fish-eye effect, with the Minimap serving as a zooming "lens" placed on the HUD.
The HUD's "player Field of View" circle is adjusted to match the tracking area on the minimap, and is thus made larger than usual - even way larger, up to the size of your minimap, if you zoom in. This gives the "field of view" display the function of a "flashlight" - node icons that get in the FOV circle may prove to be active gatherable nodes.

Drawbacks:
- Requires player to use minimap rotation. With rotation off, Minimap Lens will be disabled.
- Requires the HUD's Viewing Angle setting to be set to 90'. No oblique angle is possible, and thus perspective is out of the question, too. Minimap Lens works properly only when the HUD is viewed "from the top", as it can't match the HUD's distortion.
- Displays all kinds of built-in Minimap icons on the HUD; questing arrows, corpse pointers, POI indicators, etc. Hunters would be advised to turn their creature tracking off.
- Keeps in sync with the Minimap zoom level, there's no escaping that.
- Will probably clash horribly against any Minimap-modifying addons, like Sexymap or Carbonite.

The patch and the two additional images are here: http://sinpi.net/wow/minimap_lens_patch-files.zip
A ready patched Gatherer_HUD, for quick setup, is here: http://sinpi.net/wow/gatherer_hud_lens.zip

Have fun with it.
Does it feel useful? Are there any glaring bugs in my code?
All kinds of comments are very much welcome.

Enhancment Idea (Gather Farming)

thematrimix — Tue, 18 Jan 2011 16:42:45 +0000

Hello,

Not sure if this is already a part of Gather as I have been away from WoW for a year.

Basic Idea: Use Gather to farm the things(herbs, ore) it tracks easily.

More Details:
The idea here is to use the knowledge gather has (locations of herbs for example) to create shortest path for farming. Now this will involve graph theory (I have not uses in a good while so do not remember that much about it) to use the locations of the items and determine shortest path to gather them all(assuming they are all there).

Note this is just an idea and not flushed out, but here is a think tree.

Gather Farming
*Search by area/zone
*Search by specific herb(s)/ore(s)
*treat like quest so to have pointer to next item in search graph
*draw overall path on map
*make an option say "Farming"
*Effiency
*limit to option (graph search can be a resource hog)
*calculate one and assume user will follow unless change event
*change events
*found new item along the way
*picked up item out of order of search graph
*enter/leave area/zone

Description of Farming Options:
Imagine a window for the Farming options. It will be pretty simple in that all that is really needed is a check box to enable the Farming option and a check boxs list (separated by type) of all the items you want to include in the search graph.

Well that is my idea. I do not know if something like this already exist or not, but it seems like it could be a very useful farming tool

Thanks
thematrimix

Manually adding nodes, eggs etc

Talia — Sat, 15 Jan 2011 13:44:10 +0000

I'm not sure if this is the correct forum, please accept my apologies if it isn't.
Are there any plans to enable the player to manually add nodes or items that they've been given the co-ords for, e.g Netherwing eggs.... there are loads of posts around listing co-ords for them, and I just thought, rather than having to dl "yet another addon :/" it would be nice to simply be able to slot the information into gatherer.

esES missing locales

maqjav — Sun, 19 Dec 2010 18:29:21 +0000

Rich Obsidium Deposit esES 202739, --> Depósito de obsidium rico
Rich Pyrite Deposit esES 202740, --> Depósito de pirita rico

Astrolabe Library

Esamynn — Wed, 22 Nov 2006 19:56:08 +0000

Astrolabe in the new library I have been developing for placing icons on the Minimap, and World Maps. I will be incorporating a pre-release version of the Library into Gatherer's 3.0 branch shortly, and I am going to use this post to detail the various API functions that may be of interest.

General Notes:
[ulist]
[*]Currently a coordinate data point consists of 4 numbers, continent, zone and xPos and yPos (with TOPLEFT being the 0,0 point and BOTTOMRIGHT being the 1,1 point)
[*]continent 0 is the world of Azeroth, 1 is Kalimdor, 2 is Eastern Continent, 3 is Outland
[*]a zone of 0 or nil indicates that you want the continent itself (this value is generally, but not guaranteed to be, ignored when continent == 0)
[/ulist]

dist, xDelta, yDelta = Astrolabe:ComputeDistance( c1, z1, x1, y1, c2, z2, x2, y2 )
[ulist]
[*]takes two sets of coordinates and computes the distances between them in game yards
[*]specifically, the calculation is point 2 - point 1 do adding the xDelta and yDelta information to the first point would get you to the second point
[/ulist]

xPos, yPos = Astrolabe:TranslateWorldMapPosition( C, Z, xPos, yPos, nC, nZ )
[ulist]
[*]calculates world map coordinates for another zone
[*]C, Z, xPos, yPos - the point to be translated
[*]nC, nZ - the new zone whose map scale the point will be translated into
[/ulist]

continent, zone, xPos, yPos = Astrolabe:GetCurrentPlayerPosition()
[ulist]
[*]returns the player's current position
[*]NOTHING AT ALL is returned if no valid player position is found
[*]this function only changes the current world map if there is no valid player position available on the current Map Zoom
[/ulist]

Astrolabe:PlaceIconOnMinimap( icon, continent, zone, xPos, yPos )
[ulist]
[*]icon - frame or texture widget to be placed on the Minimap
[*]continent, zone, xPos, yPos - world map position of the icon
[*]once an icon has been placed on the Minimap with this function, Astrolabe will actively update it's positioning until it is removed
[*]this function calls icon:Show()
[*]if icon is already being managed then its positioning information is simply updated
[/ulist]

Astrolabe:RemoveIconFromMinimap( icon )
[ulist]
[*]removes the specified icon from position management
[*]this function calls icon:Hide()
[/ulist]

Astrolabe:RemoveAllMinimapIcons()
[ulist]
[*]removes all currently managed Minimap icons from the Minimap management system
[*]this function is called whenever PLAYER_LEAVING_WORLD is fired
[*]this function calls icon:Hide() for all managed icons
[/ulist]

Astrolabe:PlaceIconOnWorldMap( worldMapFrame, icon, continent, zone, xPos, yPos )
[ulist]
[*]worldMapFrame - the world map frame the icon will be anchored to (WorldMapDetailFrame for our purposes)
[*]icon - frame or texture widget to be placed on the World Map
[*]continent, zone, xPos, yPos - world map position of the icon
[*]this function does not call icon:Show()
[/ulist]

Please use this thread for any suggestions and/or comments. Please note that the API and specific guarantees of the API are still under development and thus may change somewhat.

frFR localization item

Nechckn — Fri, 13 Mar 2009 19:03:14 +0000

Esamynn,

Not sure if it is already modified in the upcoming version - just passing along the info.

so with the new version of wow
{Verpérenne"] = 191019, -- Adder's Tongue
change her name to
["Langue de serpent"] = 191019, -- Adder's Tongue

Happy localization,

Nikk :shades:

minimum skill?

Malific — Sat, 31 Jan 2009 16:02:02 +0000

Just a thought, I personally feel this would be very useful to those of us working on getting our skill up.

Could you look into including an option to show the minimum skill required to gather something on the mouse over tooltip. Also a maximum teachable skill would be nice.

They could show up as a single line Skill Req: 250 Max: 300
And be toggled separately by check boxes in the options menu.

Just a suggestion.

What node density data should be shown in gatherer?

Kandoko — Thu, 13 Mar 2008 20:01:04 +0000

Looking for input on what shape the node density report should take? This is a remake of the old display what % of nodes are in each zone.
To display where is the best place for Rich Thorium
75% rich thoruim in Burning steeps
60% Ashazara
XX% in foo

So what types and how would you like data such as this displayed?

Node average content

Islorgris — Mon, 19 Feb 2007 08:30:27 +0000

Esa,

how hard would it be to have average node secondary drops stored and/or displayed (more this later option though) on a zone basis ?

for mining alone, I see huge differences between average node content in various zone.

for example:
Fel iron nodes in Hellfire have a larger chance to provide fire motes compared to other fel iron nodes in the other zones
Mining nodes in Blade Edge have a larger chance to give gems (and more blue quality ones too on average).
Average gem types obtained in a zone changes too.

this is empirical data but based on gathering 400-500 ores in a row from single zones.

Localizer contents

Islorgris — Wed, 14 Feb 2007 12:21:44 +0000

I've proceeded to lock most french items in the Localizer for Gatherer (except those few non-critical ones I'm still not happy with their translation) since somebody though it fun to change the skill names by something not existing ingame thus affecting recording for Herbs (the change made it in 480)

Un'Goro Power Crystals

Esamynn — Mon, 29 Jan 2007 14:09:34 +0000

It's time we figured out how we are going to handle these. The various questions we need to answer include:

[ulist]
[*]Do we want to treat the four colours as one type of node instead of 4? (If No, then we are done, don't go any further.)
[*]Do we want to record each colour of node seperately and then display them as a single node, or just record them in the database under a single category node id?
[/ulist]

Any other comments?

underdev: TBC Beta version

Islorgris — Tue, 21 Nov 2006 12:01:42 +0000

apart from making the live version functionnal for BC, I'm also testing some new things, among others:

- universal zone indexes (poor man's version, not using the mapnames but the zonematch transition matrixes to convert the indexes on the fly to the universal one) (my guild leader is playing with me on the beta and he's using the english client).
- node sharing using the addon message mechanism (had to adapt a few things DB-wise such as storing the icon name instead of the node name to allow it to work for cross language clients but otherwise it's pretty straighforward, if you don't forget to convert the numbers passed in the message string back to numbers that is ;) )

also had to extend menus a bit to handle the extra herbs (we cross over the 32 items limits in menu with the addition of new TBC herb types), had to make a workaround to go over the 32 limit (basically, dynamically creating the extra dropdown menu buttons when initializing the menu and changing the global variable giving the max number of entries before adding the button and setting it back to the normal value just after) but, since there are some side effects, the dropdown menu code will probably have to be rewritten to split too long lists.

will probably make a branch in SVN for this for reference.

[Gatherer] Undergoing a heap of restructuring

Norganna — Wed, 25 Oct 2006 02:07:48 +0000

Well, Esammyn has just about finished his database cleanup code and so now it's time for me to step up and do my refactoring which has been waiting for a lull in development since it will be so disruptive.

It's all a part of the process in converting Gatherer to being a more environmentally friendly, more localizable, more developable addon. I'm carrying out the restructuring work in the branches/3.0 directory.

I've moved a heap of the code that was in the monolithic Gatherer.lua into seperate role based files. All the functions now exist in the single Gatherer namespace, with subcategories underneath, and finally the function name, so at a single glance, you can tell the file that the given function will appear in. EG: Gatherer_MiniMapPos is now Gatherer.Mapping.MinimapPosition and in the GatherMapping.lua file, along with all the other Gatherer.Mapping functions.

Now that this has been done, I'll fix up any stray references to the old function names and start working on Babylizing the localized strings so we can get this whole localizer thing up and running. Then we can get some of our translators working on doing Gatherer translations as well.

Have a look at the new structure if you get the chance. I'd love to get some feedback.

[Gatherer] Database Design

Imported — Thu, 15 Jun 2006 16:07:10 +0000

Imported post by: Esamynn Technical details about the database upgrade (as they currently stand).

Last update: June 23, 2006

The current plan is for the database to be read in by a seperate file that maintains a library of code for accessing the database. No code outside of thie file will ever access the database table directly and in fact the table will be stored in a local variable until PLAYER_LOGOUT fires, as which point it will be given a global pointer to allow the database to be written out as a SavedVariable. The purpose of the library is to allow us to limit the scope of any further upgrades to the database. For example, if we upgrade the database to use zone name Tokens instead of locale dependent numbers, the rest of the gatherer code could remain unchanged, while the library code handles the details of converting between the locale numbering system and the internal format.

Library Functions (NOT FINAL)
internalDataTable = GetRawDataTable() - removed
index = AddNode(gatherName, gatherType, continent, zone, gatherX, gatherY, gatherEventType)
ClearDatabase( noCollection )
zoneDataExists = HasDataOnZone( continent, zone )
nodeNameInZone = IsGatherInZone( continent, zone, gatherName )
nodeTotal, countTotal = GetNodeCounts( continent, zone )
nodeCount = GetGatherCountsForZone( continent, zone, gatherName )
treasure, herb, ore, unknown = GetNodeCountsByGatherType( continent, zone )
xPos, yPox, gtype, icon, count = GetNodeInfo( continent, zone, gatherName, index )
buggedState = SetNodeBuggedState( continent, zone, gatherName, index, bugged )
buggedState = IsNodeBugged( continent, zone, gatherName, index )

Library Iterators (NOT FINAL)
GetAreaIndices( continent ) - continent is optional,

if not specified, the iterator returns each continent the DB has data for,
otherwise the zones on the specifed continent for which there is data are returned

ZoneGatherNames( continent, zone ) - iterates over the nodes names in a zone returning: nodeName, gType, nodeCount, icon
ZoneGatherNodes( continent, zone, gatherName ) - iterates over the nodes of a specific name in the zone returning: index, xPos, yPos, count

Database Merging/Upgrading

The conversion process uses a definition table for each previous version that tells the process how to go about converting from a database of that version to the most current version. The database version is designed to only be incremented when the format changes in a fashion that is incompatible with older versions as the library code will always assume that it is dealing with an up to date format for efficiency reasons.

Here is an example of a conversion infromation entry, I have used the version number 0 to represent unversioned databases.

CODE

ConversionInformation = {
    [0] = { --MergeNode argument mapping table for unversioned DB to MergeNode function arguments
        nodeLevel = 4,
        mappingData = {
            [1] = { type="key", level=3, }, --gatherName
            [2] = { type="value", level=4, key="gtype" }, --gatherType
            [3] = { type="key", level=1, }, --continent
            [4] = { type="key", level=2, }, --zone
            [5] = { type="value", level=4, key="x", }, --x
            [6] = { type="value", level=4, key="y", }, --y
            [7] = { type="value", level=4, key="count", }, --count
            [8] = { type="value", level=4, key="icon", }, --icon
        },
        --conversion table for any needed type conversions to the arguments of MergeNode
        --this is also type checking data
        --if there is no data for an arugment, then it is nil'd out
        --values with invalid types are nil'd out
        --conversion specifications can either be a table or a function that maps old values to new ones
        typeConverstionData = {
            [1] = "string",
            [2] = {
                caseSensitive = false,
                number = {
                    [0] = "Treasure",
                    [1] = "Herb",
                    [2] = "Ore",
                    --all others map to nil
                },
                string = {
                    ore = "Ore",
                    herb = "Herb",
                    treasure = "Treasure",
                    --all others map to nil
                },
            },
            [3] = "number",
            [4] = "number",
            [5] = "number",
            [6] = "number",
            [7] = "number",
            [8] = {
                caseSensitive = false,
                number = function(data, nodeData) return Gatherer_GetDB_IconIndex(data, nodeData[2]) end,
                string = function(data) return data end;
            },
        },
    },
};

Note: MergeNode is a function that is passed to the conversion process when it is started. It's job is to take a set of node data and integrate it into the new/existing database table that is the final result of the conversion process.

Entry Details

nodeLevel - defines what level of the table nodes are found at
mappingData - defines where each argument to the MergeNode function is defined in the old data format
type - indicates whether the data for this argument is found in the entry's key or in its value
level - indicates what level of the table (in the path below the node entry) the data is on
key - if type="value" then the key under which the data is stored at that level needs to be specified
typeConverstionData - this table is for defining type checking and conversion information for each argument that will be passed to MergeNode4
if the value is a string then that string defines a Lua type, if the argument's type matches the defined type, then the data is valid, otherwise it is nil'd out
if the value is a table, then you can define multiple possible Lua types, each key in the table defines the lua type that it's value handles, the conversion information is store in the values and can be of the following Lua types:
table - a table is used as a direct mapping of old values to new values, any old values that are not defined in this mapping table are nil'd out
function - the function is called with 2 arguments and should return the new value, the first arument is the data that is being converted, the second is the table of arguments that will be passed to MergeNode (as it currently stands in it's partially filled in state, note that this argument table is not flushed before each new node is processed so only entries prior to the current one should be used by the function)
string - a string is assumed to be a pointer to a globally defined function so it is passed to getglobal and then the return value of getglobal is called with the same fashion as the function type
caseSensitive - this entry determines if string.lower should be called on the data entry before it is passed through the conversion process, a value of true indicates that it should NOT be altered (thus the default is to use string.lower). This only applies if the old data type is a string

Internal Database Format

CODE

GatherItems = {
    [continent] = {
        [zone] = {
            [nodeName] = {
                ["icon"] = <iconString>,
                ["gtype"] = <gatherTypeString>,
                [1] = {
                    [1] = <x-coordinates>,
                    [2] = <y-coordinates>,
                    [3] = <countValue>,
                },
            },
            [nodeName] = {
                ["icon"] = ,
                ["gtype"] = "Ore",
                [1] = {
                    [1] = 57.69, --x value
                    [2] = 74.78, --y value
                    [3] = 0, --count
                },
            },
        }
    }
    ["dbVersion"] = 1,
}

Internal Field Details

continent - number - the continent number as returned by the game client
zone - number - the zone number as returned by the game client
nodeName - string - the localised name of the node that was gathered from
- string - locale independent string that represents the icon used by this node name
- string - locale independent representation of the node type (one of "Ore", "Herb", "Treasure")
- number - the x-coordinates of the node (accurate to 2 decimal places)
- number - the y-coordinates of the node (accurate to 2 decimal places)
- number - the number of times the node has been gathered from (whole numbers only)

Supporting Gatherer Code Changes

This is a list of general changes to the code structure of Gatherer that I will be making to support the database upgrade. Some of them are somewhat wide spread, but once they are finished, the code base will be more consistant overall. Because these changes are somewhat sweeping, I won't detail them here, but I will simply list the overall outcome of the changes.

unknown icon and gtypes will now simply be nil values
gtype will now always be a string
icons will be indexed by a locale independent string token (numbers limit readabilty of the SavedVariable file)

P.S. - Yes I did delete this post's original contents, but it still exists in the quote in MentalPower's reply. /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />

in development (2.2.3.2)

Islorgris — Mon, 11 Sep 2006 11:55:30 +0000

for post live release bug fixes, mainly.

- among other things, I received an update for the chinese localisation from the guy that made the original translation.
- few items in the trac tickets to take care of

PS: btw, I'm on vacation at the end of the week for 2 weeks away from any modern communication device, I'll try to commit what I have in the trunk before that :)

[Gatherer]Issues with WoWI upload

MentalPower — Fri, 01 Sep 2006 16:46:43 +0000

Hey Islorgris, after a conversation with Cairenn (over at the #WoWI-Lounge IRC channel at chat.freenode.net) about the upload over at WoWI, it has come to our attention that neither her (Cairenn) nor Dolby (Admin of WoWI) have received any PMs about a transfer of ownership of the Gatherer AddOn to your account. In short if you want it transferred all you need to do is PM Cairenn and she'll take care of it. Hope to get this matter resolved without causing more drama/headaches for Cairenn and our other WoWI friends.

EDIT:
Further conversation has resulted in the Gatherer AddOn being transferred to your ownership. However a thorough search of PM's sent to Cairenn and Dolby have not turned up any message from you.

[Gatherer]Lua 5.1

MentalPower — Wed, 30 Aug 2006 20:47:42 +0000

Well the pirate has come thru again, this time with an often requested change. In the expansion WoW will be changed to use Lua 5.1 (http://forums.worldofwarcraft.com/thread.html?topicId=14682657)

The only real problem here is the for loops
for key, value in someTable do ... end
Will NOTwork anymore. Instead, the following construct should be used
for key, value in {i}pairs(someTable) do ... end

I have not looked thru the Gatherer code to see if the former construct is used, but if it is, you should start changing them now.

[Gatherer]Preferences not saved

MentalPower — Sun, 27 Aug 2006 11:00:21 +0000

If I'm reading the changes correctly, the GatherConfig table is no longer being saved at all. It was completely removed from the .toc file.

[Gatherer] in development (2.2.3.1)

Imported — Wed, 26 Jul 2006 14:00:38 +0000

Imported post by: Islorgris # Bug Fix:
- forced overlay frame identifier to integer values when computing these dynamically for world map buttons
- forced UI options that were meant to be saved as numbers to number in default and changed values.

# Changes:
- Configuration is now saved per character instead of globally (which means that current UI configuration will be only kept for the 1st character to logon after that is installed, the settings have to be redone on other char, they'll be set to the default values).
- removed world map buttons, these are now generated dynamically.
- moved the Gatherer_AddGatherToBase function as a local function inside the Gather_AddGatherHere function (this will break GathererShare), undocummented change.

everything commited to the trunk (except the matching readme).

all changes put in the 259 revision of Gatherer.lua have been reverted.

BTW, Esa don't commit to the trunk without telling me, it's a real headache to merge/unmerge files directly from the trunk and that's where the fixes are commited.

if you want I can lock the trunk so that, there's no mistake while commiting.

[Gatherer] Documentation

Norganna — Mon, 21 Aug 2006 08:57:58 +0000

I'm in the process of converting the Gatherer forum documentation into the wiki at the moment. I'm gonna have a stab at doing the Frenchdocs while I'm at it, but i'll need someone to check over what I do to make sure it's all ok(no stupid mistakes etc)

[Gatherer] in development (2.2.3)

Imported — Wed, 26 Apr 2006 00:00:47 +0000

Imported post by: Islorgris Some minor bug fixes.

Fixed some checkboxes positions in the Globals tabs
Fixed default icon for worldmap notes to prevent spam in FrameXML.log
French localisation: fixed Sauge-argent and added name transition to list of fixed names.
Fixed Event processing not to occur while zoning.
Addon init, use a string forced to lower case to get addons name (which match the folder/toc name, while windows is not case sensitive, the WoW client is) to have initialisation occur even if the folder is misnamed on hard drive.

The bulk of the modifications will be some code optimisation and database format change (will be incompatible with GatherBook).

Have to see if I can slip in zone promixity for mininote display so that nodes in adjacent zones show up again on minimap.

Convert translations to use the same tool as Auctioneer

Imported — Tue, 11 Apr 2006 00:55:12 +0000

Imported post by: Norganna I would like to get the translation team to start using Localizer.

It has proved to be a real benefit to Auctioneer, and I think it will be good for Gatherer also (although I know Gatherer is a bit more complicated)

What do you think Islorgris?

(it's at http://norganna.org/localizer in case you've never seen it)

[Gatherer] Mass confusion and mayhem

Imported — Tue, 18 Apr 2006 01:00:38 +0000

Imported post by: Norganna I've been thinking this over, and I want to bring Gatherer into the fold as far as the subversion repository and automated builds etc are concerned as well as doing the localization stuff.

I know you are hesitant on all of this stuff because you're comfortable with the sourceforge repository, but we've built some really cool technology with Auctioneer and I think once the pain of the move is done with, you will really love the systems we have in place.

Just to make you more comfortable, I will implement the new systems in parallel to the sourceforge ones for the time being so you can test them out and see how neat they are.