Finally, after just over a year a new release is ready. This one is focused on completing support for Ordered Datastores but it also has a few other improvements.
Win-Install is an installer containing both Qt5 and Qt6 versions of Open Cloud Tools. Win-Qt6 is the build users of Windows 10 and newer should use. Win-Qt5 is the build users of Windows 7 and 8 should use. Mac supports recent versions of MacOS but I’m not actually sure which. To use the Mac version you must run xattr -cr /Applications/OpenCloudTools.app in the terminal after installing to make it runnable.
Big features:
Added support for creating, incrementing, modifying, and deleting ordered datastore entries.
Added button to automatically fetch universe name based on ID.
Changes:
Fixed failure to list contents of ordered datastores after the API changed.
Fixed being unable to rename API keys.
Added more tooltips to explain functionality.
Improved ‘in progress’ messaging for most API calls.
Working on it now but I’m not sure how long exactly it will take. Right now my attention is split between that and re-working the interface to be less cluttered with the increasing number of APIs that are being added.
Not sure which will be ready first, but I’d guess probably a few weeks until I can release a version with memory store support.
First I should say that this ended up taking longer than I expected so I’ve switched over to working on Memory Store support first, so there will still be a memorystore-compatible version with the older interface. Hopefully will be ready in no more than a week at this point.
Most of it will be staying exactly the same, the big change is that instead of having the universe drop-down on top and then tabs under it, those will both get combined into a single list on the left that lists all of your universes and the different tools available under them. The gui for each individual tab will also be separated into its own subwindow, so you can have more than one up at once.
It is still only half-implemented but here is my mspaint concept.
Edit: Should add the subwindows will also have a title that shows which universe they are for so you don’t accidentally mix them up.
Looking good! I already like the UX, but I think it could be even better with the new tweaks.
By the way, have you seen the new Open Cloud update? You can read more about the devforum post here.
With this update, it’s now possible to create Data Store snapshots. The new CreateUniverseSnapshot endpoint is available on Open Cloud, and you can find the details in the documentation here.
Could this be integrated of somesort inside the tool?
I’ll look at getting that into the next release, looks like it should be pretty easy to add.
My current plan is:
There is a new release right now, more on that below.
Next release should happen within 2 or 3 weeks, it will include the datastore snapshot thing as well as more memory store support. This will still use the old GUI.
At some point following that the new GUI will be ready, more on that eventually.
This release brings partial support for Memory Store Sorted Maps, read-only for now. More will come in the next version.
Changelog:
Big features:
- Added support for reading from a memory store sorted map. More memory store functionality will be coming in the future.
Changes:
- Increased default window size to better support the amount of data available in memory stores.
New release today, but the only new feature is Datastore snapshotting. This one also has an important fix for a mac-only bug that made it impossible to close some dialogs.
Win-Install is an installer containing both Qt5 and Qt6 versions of Open Cloud Tools. Win-Qt6 is the build users of Windows 10 and newer should use. Win-Qt5 is the build users of Windows 7 and 8 should use. Mac supports recent versions of MacOS but I’m not actually sure which. To use the Mac version you must run xattr -cr /Applications/OpenCloudTools.app in the terminal after installing to make it runnable.
Features:
Added support for datastore snapshots.
Bug fixes:
Fixed some dialogs that were impossible to close on MacOS.
Several internal changes to better support the upcoming new GUI.
Next priorities for me are still more memory store stuff and the new gui. Not sure when I’ll have it done, though.
Hey, is the bulk data download supposed to save the file as a .sqlite3? i need this data to transfer over to firebase and i don’t know how to convert it.
I see it looks like you got an answer in that other thread. I would also recommend the python interface if you want to manipulate the format of that data. I don’t know exactly what firebase expects so I can’t help you too much there.
If you’re feeling more adventurous you can also build sqlite yourself and use the C API but python would be much simpler since sqlite support is already built-in.
Yes, you can! You can also delete all entries, as @FlikterIsLinked mentioned he wanted to do. It’s just gonna take very very long if you have 1000+ entries lol.
Hi! Thank you so much for this. I’d also like to ask if there’s a way to bulk download datastores with specific names? For example, I want to download datastores that includes the name “PlayerInventory” only. I don’t want to download everything that I do not need. I would like to know if that’s possible at the moment. Thanks!
As you can see, I am using datastore2 so there would be lots of datastores. I don’t want to download all entries that has the word “PlayerEquippedItems”. The numbers you see are the player’s user ID and I can’t hide it manually because there’s a lot. Please help.
Hey all, wasn’t watching this thread for a month or so, so I fell behind on responding. I’ll reply to the people who still have open questions one-by-one in some follow-up posts so they all individually get a notification rather than doing it all in one post.
Also, I wanted to say that I’m just about ready with the new GUI and should have a beta version out by this weekend. As far as I know everything should work exactly the same as the old version but I’m calling the first one a beta just in case something ends up broken.
Not possible at the moment but I can look into adding that. Right now the whole datastore browsing interface is really built around the idea that you will have a smaller number of datastores with per-player keys in each rather than creating a separate datastore for each player.
This will take some thinking on how I need to make the interface work for that, so I probably won’t have it particularly soon but I’ll add that to my todo list.
