Weaponsmith Archive
Thread: Selling sliced weapons-- how do you keep track of what's what?
Page 1 of 1
d0qtrX
Tue Aug 10, 2004 10:32 am
#1
Obvioulsy sliced weapons carry different values dependant on what % the slice was. So any of you WS who sell them, how do you keep track of what was sliced as what?
As necessity is the mother of invention, I wrote a quick-and-dirtyPHP script that takes your base min/max and speed and generates a table of what would happen under every slice condition from 10%-35%. Using this, i can look at a weapon's final stats compared to the base (which i put in the name) and am able to pinpoint the slice percentage easily.
I ran into a problem when writing the script, and I was wondering if you had any opinions. It has to do with decimals. When you slice, there are decimals that are either rounded or dropped. I get the most accurate comparison with real-world slices when I simply drop the decimals. However, sometimes it will be slightly off. Perhaps this is attributed to the invisible decimals in the weapon's own stats before the slice ever takes place?
At any rate, I was wondering what you all were doing as far as that goes.
Brilyn
Tue Aug 10, 2004 10:38 am
#2
I don't pinpoint the slice % at all. I find people just don't care about the % slice, but do care about the type.
CsciGuy
Tue Aug 10, 2004 11:12 am
#3
Hi,
When it comes to fiquring out which weapon I just sold from the vendor email , I make the price of the weapon unique for that weapon's name, damage and speed. But yeah , like Briyln said , the customer doesn't seem to care about the %, just the actual stats
When it comes to fiquring out which weapon I just sold from the vendor email , I make the price of the weapon unique for that weapon's name, damage and speed. But yeah , like Briyln said , the customer doesn't seem to care about the %, just the actual stats
FreeEnterprise
Tue Aug 10, 2004 11:26 am
#4
All my damage sliced are $x (higher than an unsliced), and all my speed sliced are $x (lower than an unsliced).
First one there gets the pick of the litter.......this also gives customers incentive to check back often.
smork
Tue Aug 10, 2004 1:08 pm
#5
d0qtrX wrote:
As necessity is the mother of invention, I wrote a quick-and-dirtyPHP script that takes your base min/max and speed and generates a table of what would happen under every slice condition from 10%-35%. Using this, i can look at a weapon's final stats compared to the base (which i put in the name) and am able to pinpoint the slice percentage easily.
I ran into a problem when writing the script, and I was wondering if you had any opinions. It has to do with decimals. When you slice, there are decimals that are either rounded or dropped. I get the most accurate comparison with real-world slices when I simply drop the decimals. However, sometimes it will be slightly off. Perhaps this is attributed to the invisible decimals in the weapon's own stats before the slice ever takes place?
I did the same thing, a simple spreadsheet that calculates all slices 20-35%. I also added in a pricing formula for each %.
CorenLanra
Tue Aug 10, 2004 2:24 pm
#6
I have my own slice calc that does 15 25 35 (that is my main tiers) and have a custom field which I almost put 30% in, normally I round down or if say a 25%slice comes out as 278 damage I will make my price point cutoff at 275 or so. I know that doesn't help you with your rounding, but usually if the slice comes out to 2.489 speed or something the weapon will be 2.5 if that helps 
www.sitepoint.com has some nice PHP tutorials if you are looking at updating your code to account for rounding.. I jusually just eyeball it.
www.sitepoint.com has some nice PHP tutorials if you are looking at updating your code to account for rounding.. I jusually just eyeball it.
Dynastar
Tue Aug 10, 2004 3:19 pm
#7
I group it into 35-30/29-25/24-20% slice groups. Anything lower is base price. Although, guild members get the first pick of high-end slices.
omif
Tue Aug 10, 2004 7:31 pm
#8
speed sliced is one price and damage sliced is another no matter what the % slice was
Page 1 of 1