Randomize Gear Not Really Random

[tselaty]

Some classes like the Paladin or the DK has fixed chances, and as such, their possibilities by using the first or last character in the poster ID makes the options limited. Paladin's should use the last character of a string, and the DK the second to last. Warlock's should use the last character, etc.

I'll work on fixing that to add some more visual variety.

[entomb]

I've added you as collaborator so you can manage tickets like a boss.

welcome aboard!

[tselaty]

Thank ye` kindly.

Tim Selaty Jr. TLS Web Solutions

On Saturday, April 27, 2013 at 12:22 PM, Jonathan Tavares wrote:

I've added you as collaborator so you can manage tickets like a boss. welcome aboard!

— Reply to this email directly or view it on GitHub (https://github.com/entomb/dragonchan/issues/26#issuecomment-17119784).

[entomb]

Sugestion:

Get 16 of each (if not enough duplicate some of them) weapon and armor MD5($post->id)

take first character from the md5 hash. should be an hex, so 0 1 2 3 4 5 6 7 8 9 A B C D E F, it should randomly match one of the 16 images.

use second character for armor.

[tselaty]

+1

[tselaty]

I've resolved this by just using the second character of a class rather than the first. In some cases we don't have 16 images for the sprites, and others we have 64 available (visually appropriate). The offset works as a better solution for now than the MD5 hashing, as we have more options where viable.

[entomb]

works for me