Chakravanti wrote:jorb wrote:....Example: James has 14 perception...
BAW!! You gave yourself away early and we ALL missed it!!!!!
James has 67 perception, though.

Chakravanti wrote:jorb wrote:....Example: James has 14 perception...
BAW!! You gave yourself away early and we ALL missed it!!!!!
Loopoo wrote:Jorb, please draw the boats and get em in the game ASAP :C
I'm really waiting on them :C
Exactly. Generic perception doesn't even make sense if you leave out the appropriate skill; like Masamune wouldn't know a good sword if he started to lose his sight.Devour wrote:I have to say that I don't like the whole "seeing quality" thing. It's just really annoying. It'd be better if it was based on your level in the related skill, instead of generic perception.
Voideka wrote:Exactly. Generic perception doesn't even make sense if you leave out the appropriate skill; like Masamune wouldn't know a good sword if he started to lose his sight.Devour wrote:I have to say that I don't like the whole "seeing quality" thing. It's just really annoying. It'd be better if it was based on your level in the related skill, instead of generic perception.
A better idea, in my opinion, would either be to combine the skill and perception in some way (with the result no lower than the skill to make it), or to check which is higher, skill or per, and use that. Personally I think the former is the best, as it is most realistic. A good smith will know what it takes to make a certain quality of goods, as he employs those techniques in his work. A good and highly perceptive smith will be able to see what makes an item better than his own best, and this is in part how he learns, by incorporating those things into his future work.
jorb wrote:Chakravanti wrote:jorb wrote:....Example: James has 14 perception...
BAW!! You gave yourself away early and we ALL missed it!!!!!
James has 67 perception, though.
Users browsing this forum: Claude [Bot], PetalBot [Bot] and 1 guest