If a player was not on the server when the giveaway ended, or their inventory was full, then the server would push `{ name: undefined }` into the list of players that could win the giveaway. This would send the item into the abyss, as it would error while the server would try to mail the item, preventing it from being recovered.
This fixes a bug with giveaways. Giveaways would previously list all of the participants of a giveaway in the mail, but at some point a breaking change occurred, and instead it lists [object Object] multiple times.
Prior to this change, Piercing Shot (A ranger skill) that gives 500 armor piercing would only grant this pierce if the player had no pierce themselves. If the player had pierce, the pierce from the skill would then be overwritten by the player's pierce. This change fixes it by adding the player's pierce (or miss chance!) to the skills stats.
This PR aims to fix a bug where if a user attempts to shiny an item using the upgrade station and an offering, if it succeeds, the server does not send a response. This appears to occur because the server sets a "announce" flag to be false when the upgrade is a shiny attempt, and this prevents the success response from being sent to the client.
(Original PR: #105)
This PR changes Fire Resistance to not only affect the chance of getting burned, but also having higher Fire Resistance reduces the duration and intensity of the burn debuff. For instance, if the player had N fire resistance, they would have a N% chance to simply not get burned, but also, the duration would be reduced by N%, and the intensity would be reduced by N%.
This makes it clear to the user that they should use equip_batch for 2 items. Previously, if the user used it on 2 items, they would receive the same CC either way. This change removes ambiguity.
This PR fixes a bug that happens when the player has a full inventory, is not in a party, and attempts to loot a chest that contains items, and the chest also has enough gold that it would announce the loot. The result is that the announcement is made, but the chest isn't actually destroyed.
This commit fixes a bug where a mob would get NaN speed, instantly putting them at x: NaN, y: NaN, making them unkillable, but they also would not lose aggro on the player unless the player used something like Scare.
FreezePhoenix