I'm too lazy to search forums, though I think it had been brought up before.
How difficult would it be to extend it so it will include also the buffs, assuming you posses them all.
Pic for reference: https://i.imgur.com/zhHfA8b.png
Nosferatu [280] <Solo Act>
2017-09-20 15:24:34
[7 years, 42 days ago] |
I'm too lazy to search forums, though I think it had been brought up before. How difficult would it be to extend it so it will include also the buffs, assuming you posses them all. Pic for reference: https://i.imgur.com/zhHfA8b.png |
Executed [88] 2017-09-20 15:25:31
[7 years, 42 days ago] |
such a hoarder |
<Apex>
2017-09-20 15:30:04
[7 years, 42 days ago] |
Only two of the normal speed buffs, what a loser. |
Nosferatu [280] <Solo Act>
2017-09-20 16:19:30
[7 years, 42 days ago] |
It ran out. I fixed it and made my bar worse, thanks Obama. |
Administrator 2017-11-19 15:22:22
[6 years, 347 days ago] |
Fixed. It will now expand as needed (though it will retain its ~original size if the space isn't needed). I think it was the size it was because of the old, larger logo. I guess we'll need a more robust solution if/when more buffs are added. Speaking of which, here are today's useless stats... Number of bots per number of buffs (it's the 16th buff that started to straddle the border of the old fixed-size box): mysql> select -> buff_count, -> count(bot_id) count -> from ( -> select -> bot_id, -> count(buff_id) buff_count -> from buffs_bots -> group by 1) foo -> group by 1 -> order by 1 desc; +------------+-------+ | buff_count | count | +------------+-------+ | 18 | 5 | | 17 | 13 | | 16 | 8 | | 15 | 3 | | 14 | 4 | | 13 | 4 | | 12 | 9 | | 11 | 12 | | 10 | 30 | | 9 | 36 | | 8 | 93 | | 7 | 246 | | 6 | 664 | | 5 | 1501 | | 4 | 3078 | | 3 | 6130 | | 2 | 9068 | | 1 | 35980 | +------------+-------+ And the lucky members of the 18 buff club: mysql> select -> bot_id, -> username -> from buffs_bots -> inner join bots on bot_id = bots.id -> group by 1 -> having count(buff_id) = 18 -> order by 1; +--------+------------+ | bot_id | username | +--------+------------+ | 58 | Nosferatu | | 3634 | Serpentine | | 11679 | Drained | | 12265 | Cachexia | | 12266 | Moribund | +--------+------------+ |
Nosferatu [286] <Solo Act>
2024-01-07 14:13:30
[297 days ago] |
|
Administrator 2024-06-19 16:10:06
[133 days ago] |
There's not really a "quick fix" way to do that because the exp bar is actually an embedded graphic (it was made in ~2010 before there were reasonable ways to do this with CSS), so I just centered it for now when the card needs to expand to show more buffs. |
Nosferatu [324] <Solo Act>
2024-06-19 17:18:08
[133 days ago] |
Thanks Ender. It's less glaring in my face now visually. And this is likely a very minor noticeable fix that really only affected a very small amount of people, but I'm guessing wasn't difficult, so I do appreciate it. |
Nosferatu [324] <Solo Act>
2024-06-19 17:22:35
[133 days ago] |
Not a bug, but in the same vein so thought I might place it in this thread as well. On the Topic of Buffs, is there a specific reason the buff purchase order isn't the same as the order in the buff bar |
<Apex>
2024-06-20 04:09:15
[132 days ago] |
|
Administrator 2024-06-20 23:06:32
[132 days ago] |
Exactly. In case anyone is thinking "ugh, THIS is what Ender is spending dev time on??", it took all of a couple minutes to adjust the CSS. :)
I agree that would be more natural and is more typically how buffs get handled in games. I don't know if I decided this explicitly when designing it, but there's currently no way for the game to even know which buff is oldest/newest. There's no timestamp associated with buff changes, nor is there a unique id per bot/buff combo. And given how long we've had the current behavior (sort order = buff id), some might not want it to change. For all those reasons, I won't even say my usual "added to someday list" - but who knows, maybe my thinking will change in the future.
Oh, thanks for doing this. I have some ideas to potentially rework the header card and am planning to (likely) rebuild the progress bars using pure CSS, so I'll hold off on extending it until then. Thank you though! |