PROCUREMENT : The Ultimate Path Of Exile Companion Tool!

thanks for the update too, but shouldnt it be a 1.2.1 version?

add: request: can we have an option to switch between accounts (recall of login page instead of exiting)?

gj, all working fine )

"

Natakata wrote:

I have saved it, and restarted. It is not picking up any gems other than the ones that are default. here is an example using tabs of gems

Stupid question, but you did update to 1.2.0 right?

"

Mr_Cee wrote:

thanks for the update too, but shouldnt it be a 1.2.1 version?

add: request: can we have an option to switch between accounts (recall of login page instead of exiting)?

Nope, the version is 1.2.0. If we did a version with a few bugfixes it would be 1.2.1, otherwise if we do a new release with new features it will be 1.3.0.

"

AISBERG wrote:

gj, all working fine )

Thanks.

In which file does it save the buyouts? Every time I update to the new version and copy the new files into the folder overwriting all files my buyouts are gone. I'd like to prevent this from happening in future.

Btw the "-> CLICK HERE TO DOWNLOAD FROM GITHUB! <-" link still points to sourceforge.

"

Holocaustus wrote:

In which file does it save the buyouts? Every time I update to the new version and copy the new files into the folder overwriting all files my buyouts are gone. I'd like to prevent this from happening in future.

Btw the "-> CLICK HERE TO DOWNLOAD FROM GITHUB! <-" link still points to sourceforge.

Buyouts are stored in settings.xml, so you can just copy over your settings.xml file. For versions where the settings file changes, just copy over the buyout section of the settings file.

Thanks for pointing out the download link, I've updated it so it points to github correctly now.

I have 231 gems in my gems tabs. But the code procurement produces when selecting those tabs, only generate code for 129 gems. In otherwords, it doesn't seem to recognize a lot of gems.

I was really disappointed with Procurement when I tried it out.
I was expecting that it would detect socketed gems as well as items in a character's inventory as well as possibly even equipped items (if desired in an option or something). The fact that I can't search for such things nor auto-display such things for a shop makes it extremely less useful for me, if not nearly useless.

"

Zeusolympus wrote:

I have 231 gems in my gems tabs. But the code procurement produces when selecting those tabs, only generate code for 129 gems. In otherwords, it doesn't seem to recognize a lot of gems.

Maybe you have the problem that some gems are socketed?

Great program, thanks a lot! Can't live without it.

"

Stickymaddness wrote:

"

Mr_Cee wrote:

shouldnt it be a 1.2.1 version?

Nope, the version is 1.2.0. If we did a version with a few bugfixes it would be 1.2.1, otherwise if we do a new release with new features it will be 1.3.0.

Makes it a bit hard to track such minor (but very relevant) updates - if one already has that version (like I did with 1.2.0 for some days) there's nothing to expect changes (and its nearly(?) impossible to find the lastest "release" date in the doku...

"

Mr_Cee wrote:

"

Stickymaddness wrote:

"

Mr_Cee wrote:

shouldnt it be a 1.2.1 version?

Nope, the version is 1.2.0. If we did a version with a few bugfixes it would be 1.2.1, otherwise if we do a new release with new features it will be 1.3.0.

Makes it a bit hard to track such minor (but very relevant) updates - if one already has that version (like I did with 1.2.0 for some days) there's nothing to expect changes (and its nearly(?) impossible to find the lastest "release" date in the doku...

It's not really that hard to follow.

0.x.x (app in alpha/beta stage)
1.0.0 (first final release)
1.0.x (minor bugfix or small changes to initial release)
1.1.0 (some major changes)
1.1.x (minor changes to latest major update)
1.2.0 (new major update)

and so on

2.0.0 (This would be some serious changes like rewriting most off the code or yearly releases like MS does with office almost every year for instance)


Some bigger softaware that are updated more frequently may also include build number in the end which makes sense if you are expecting dozens of minor updates before next major update.

GGG has chosen to use 1.0.x for updates and ABCDE for hotfixes. Probably keeping 1.1.0 for first expansion/miniexpansion. ;)

In the end its developers choice how he uses numbers but both ways are pretty much the same.


On unrelated note, I took a quick peek into source code and it looks pretty solid. Haven't coded CS much lately so not really expert with that language myself though.