Bug Fix: Unused Column

[Wifus]

The rrcount column in the user_weapon table is not being used! Added a query in the fetchNewWeapon function to update this column in order to give it use. Right now all the entries in that column are 0 in the database!

Also, since I changed fetchNewWeapon to be async I also made sure to add await before each invocation of fetchNewWeapon.

This information would be nice to have when I add some weapon utils to snail!

[CLAassistant]

All committers have signed the CLA.

[atifnimran]

Please me

[ChristopherBThai]

Question, should rrcount be:

• Whenever user rerolls, regardless of if they accept the changes or not
• Only when user accepts the changes

IMO if users want to show off a "pristine" weapon the ladder would be better. Rerolling without accepting the changes shouldn't put dirt on the weapon. Thoughts?

[Wifus]

From what I've seen and what weapon utility bots offer, players like to know "how much effort" was put into rerolling a weapon. Since it is much more worthwhile to look for weapons with high stat qualities and low passive qualities and reroll the passive, most people tend to reroll these weapons only once to get them to fabled or legendary tier, so the latter would not give much information in these cases. I personally don't see a case for the latter especially since it will only ever be updated to one once someone is satisfied with a rerolled passive, or two if they are feeling daring and get lucky with a good stat roll. The former would be more representative of how many shards went into the weapon which I think is more useful to know.