In reply to Scarecr0w12:

 The BastionLoot_Gearpoints-1.2 example plugin that is bundled with BastionLoot is an example of how one would go about providing their own price scheme.

At minimum they would need to  

1. Make a small addon and add BastionLoot as a dependency ## Dependencies: BastionLoot  (in the .toc)
2. Give their pricelist a unique name.
3. Implement a GetPrice function that returns their own values for each item (can be a lookup table like the prices_bc.lua one in the core addon or a dynamic calculation like in the plugin) The core addon doesn't care how the prices are calculated or looked up in your plugin.
4. Use BastionLoot:RegisterPriceSystem("name of price list", YourGetPrice)

You package your pricelist plugin addon and distribute it to your group/guild.

That way you can tweak it and update it separately if you want to make corrections to your prices and not be affected by changes or lose them when the main addon is updated.  

Process does require some small familiarity with addon crafting / Lua.

If you have something in mind on how you want to price your items tell me and I'm happy to walk you through creating a plugin (can even be a copy of the built-in pricelist with changed prices).

In reply to Scarecr0w12:

 The addon is made such that only the guild master and masterlooters need it.

It would work perfectly fine where no one else has it (minus convenience features like bid links / popups or seeing information on the tooltips and the PR list).

That is a design choice and same for not relying on addon comms. The addon only does a handshake for a one time per session version check and shares some very basic guild policy settings when they change.  

Even the pricesystem of choice can be added to the guildinformation pane (with a format of {pricelistname} and will be read from there with no need for an administrator to be online to share it.

Addon comms are a limited resource. The bandwidth is very limited it is not by addon, all addons share the same. You do not want optional information eating into it competing with your bossmods or addons that need it to exchange combat sensitive and real-time information. It also scales extremely poorly with the size of the guild.

TL;DR: A sync of price data is not in the plans I'm sorry to say. I consider the lack of it a feature not a bug :P

First beta for Burning Crusade Classic under All Files or if you have set your updater to pull down beta files.

Unless playing on a Classic Era realm (1.13.x) BastionEPGP should be removed and replaced with BastionLoot*.  

*BastionLoot can still be used to manage (for example wipe) the old BastionEPGP points in preparation for Burning Crusade.

The bid parser should already be smart enough to recognize a + / need / mainspec or ms whisper as valid.
If you mean the bid call out that's defined in https://github.com/Road-block/BastionEPGP/blob/master/Locales/enUS.lua#L105 to 107. You can change the part after = (where it says 'true' currently) to whatever you want the call out to say (but must leave the patterns in ( the %s ) )

Finally I'm afraid I'm not changing the offspec / greed method to /roll as that would require roll parsing for populating the bid window on masterlooter side and that's a whole can of worms I'm not interested in opening.

If you simply want the offspec/greed chatlink and / or the bid popup offspec to do /roll you can do this at 2 spots in the code.
Right below https://github.com/Road-block/BastionEPGP/blob/master/Modules/bids.lua#L250

Add
RandomRoll("1", "100")

Same for https://github.com/Road-block/BastionEPGP/blob/master/core.lua#L914 add a new line with
RandomRoll("1", "100")