You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
appears to be specified by noTeamLootOnDeath column in Activities table. if a player is dead at the moment loot is rolled, this should determine if they get loot drops from it (i.e. currently-dead players in BoNS get no loot from Kinga Hurl but likely should get loot from the final chest once it's opened, because the game revives them before that point)
is specified as 0 or 1, but more frequently, null, which should default to false according to client RE
Reproduction Steps
do the dead
Expected Behavior
lootn't
Environment
i have nothing funny to write here this time. you expect that? you even looked FORWARD to it? sucks to be you, bud. im not a fountain of comedy. i dont have the ability to make you laugh on command. i do what i can. if thats not enough for you, im sorry. but im trying. im trying my hardest. sometimes its not good enough. but we all do what we can. im sorry i let you down. anyway, windows 10
The text was updated successfully, but these errors were encountered:
Make sure you've done the following:
I have checked that this issue has not already been reported.
I have validated that this issue is not a syntax error of either MySQL or SQLite.
I have pulled the latest version of the main branch of DarkflameServer and have confirmed that the issue exists there.
DarkflameServer Version
extra emo edition
Issue Description
https://youtu.be/HAaknVJU3Ew?t=1320
https://youtu.be/VKucdAwj4t0?t=434
appears to be specified by noTeamLootOnDeath column in Activities table. if a player is dead at the moment loot is rolled, this should determine if they get loot drops from it (i.e. currently-dead players in BoNS get no loot from Kinga Hurl but likely should get loot from the final chest once it's opened, because the game revives them before that point)
is specified as 0 or 1, but more frequently, null, which should default to false according to client RE
Reproduction Steps
do the dead
Expected Behavior
lootn't
Environment
i have nothing funny to write here this time. you expect that? you even looked FORWARD to it? sucks to be you, bud. im not a fountain of comedy. i dont have the ability to make you laugh on command. i do what i can. if thats not enough for you, im sorry. but im trying. im trying my hardest. sometimes its not good enough. but we all do what we can. im sorry i let you down. anyway, windows 10
The text was updated successfully, but these errors were encountered: