Closed ghost closed 1 year ago
One possible workaround I can see for me is to add a new temporary collection and add all new beatmaps to it, then use the collection filter when exporting.
That works when I am dealing with just a few new beatmaps.
A filter for time added would be pretty straightforward to add.
Do you think it would be more useful to input a specific time, or (as it sounds in your case) being able to specify "how much" time is better? Something like an "added since 2 hours ago" filter is something that I'm thinking would be useful.
true
also sometimes i find it can be hard to type the whole collection name (it can be long and i can forget or make mistakes), or it just simply strangely doesn't work for collections with japanese characters in the name
i hope i can select them from a list using indexes
I have some time where I can write both of these features today, a way to identify collections by an index and the "since" filter.
It looks like there will need to be a small schema update with the next lazer version, so I'll probably release an update with these features at the same time as it's probably soon rather than having 2 updates.
I am using lazer client for grabbing new beatmaps, after that I may want to export the newly added beatmaps to stable.
This tool already does a good job when I want to export all beatmaps from lazer to stable, but when I add some new beatmaps to the lazer database I may want to export only the new ones.
Is this supported currently?