Thank you all for the feedback and support! It really made my day.
I like that idea, but at the moment I can’t because my account is not verified.
Thanks for the detailed feedback. It was very helpful and I will try to incorporate it into future releases (although the x-aligned fields will be a little difficult since all elements are rendered in isolation for virtual scrolling).
oh my god, thanks so much. I was trying to figure this out for the past 5 hours yesterday. it kept listing 50 keys over and over when i know i had way more. thanks again.
The scroll bar on the right (same picture as above) is a bit hard to make out; would be great to add some spacing between the rightmost edge and it, along with a background on the scroll bar whenever its visible.
Some elements are incredibly clicky and immediately responsive, whilst some UI animations are very slow. The setting color fade-out, and switching between accent colors could perhaps be a bit faster – though this is of course purely preferential & subjective
The key info tables (or just any read-only values) may be useful to turn into uneditable TextBoxes, so that the plugin user can still select & copy-paste text. TextLabels by themselves do not allow for this unfortunately
It feels slightly disorienting hovering over rows that do not immediately respond – if not having it a default, then adding a setting for an immediate-mode highlight would be amazing!
this is a big undertaking in itself, but sorted data stores would be an amazing help for debugging leaderboards and the like.
Thanks you for all the feedback! I really appreciate getting replies like this If you don’t mind, could you elaborate more on the sorted datastores? There is already support for ordered datastores.
Thanks for the report! That is a very weird bug, but I think I found the solution:
If you go into the settings and turn on AllScopes
and then you connect to the your DataStore
you’ll see the problem
I think this is because when you access the NumberValue from ServerStorage, the C++ side of stuff converts it into a string differently. The solution I found is to make sure to manually convert to string: