Suggestion - Spice variants and Pyke rule tweaks [Accepted] [In Progress] [Completed]

[Lord Stolas]

What do you want to see?: As the title suggests, I want to see a couple of variants of spice, those being:

Quick/Dirty/low quality spice (Production time: 30 seconds | Worth: 7,500 GC)

Refined/Premium spice (production time: 120 seconds | Worth: 30,000 GC)

As well as this, changing the Spice Refiner quota to be based off the amount the spice is worth rather than the number of pieces of spice

Why should we add it?: Before anyone comments it, no, the addition of quick spice would not make quota easier, just change quota to 300k worth of spice rather than 20 units and quota would remain at the same amount of effort, as each spice types time to produce is directly proportional to their worth. This addition would be a massive quality of life change for spice refiners

 

What are the advantages of having this?: The first advantage isn't about money(none of this really is), it's actually about inventory space and convenience. In having pieces of spice worth more than standard would enable Pykes to carry more worth in their inventory with less slots used. In addition, this would allow pykes more versatility in the way they produce spice, as a pyke without much time or producing in a hostile environment could make quick spice, whereas more confident refiners could make the slower variations, and make bigger hauls. 

 

Who is it mainly for?: Pyke syndicate

 

Links to any content:

[Theta]

While I do like this idea, please bring it to the Pyke Command team!

[HuntR]

On 2/18/2023 at 7:05 PM, Theta said:

While I do like this idea, please bring it to the Pyke Command team!

I like the concept, but what Theta said. If they approve it +Support though!

[Beckett]

ACCEPTED

Thank you for your suggestion! It may take up to a week until fully implemented.

[Beckett]

In Progress

This suggestion is now under review and is in the works of being implemented 

[Beckett]

Completed!

This suggestion has been implemented, you may need to wait for the next scheduled server restart to see the implementation.