There is no easy way to mark the image as custom except setting it again. But yeah I was just warning that it could happen again since the database might have some games with this bugged image url that should've been set to custom
Did you enable any option in the proxy section of the settings? If so, might be you entered the proxy settings wrong. If not, might be a third party involved in your connection setup blocking access to my api for some reason. Maybe an antivirus blocking connections to new domains with no prior reputation, or same from the internet provider. Or could just be the antivirus blocking the app from accessing the internet at all. Try disabling antivirus, changing DNS settings to use cloudflare's 1.1.1.1 or try on another network.
No real reason not to use the beta if you ask me. I'm busy for another few days with uni then I should be able to make a release. Need to update mentions of how refreshing works since it changed dramatically.
i see, nothing makes it particularly obvious what the issue would be. only thing i can think of is that the memory corruption that causes the sorting issues to begin with just happens to corrupt another piece of memory on your system, which leads the process to a panic as it does not know what to do with the overwritten bad memory.
ive noticed some weird things happening last few days, 2 games i had tracked got the last updated date changed without an update (games that have been completed/abandoned for years), so they showed up at the top of my list. i noticed that the mod had changed the "thread updated" value, but not the "release date" value. i assume that usually the "thread updated" value is changed when the thread is updated with a new game update, not for smaller edits to OP, but apparently some mods change the date anyway. i have changed the cache api to prefer using "release date" instead of "thread updated" from the OP. all games will slowly be parsed with this change over the next week as the cache expires, let me know if this produces unexpected results. it was using "thread updated" because that sounded like it means game updates, while "release date" sounded like when the game originally released, and i dont see a specific guideline about this in f95zone game posting rules/template, but from what i can see usually "release date" refers to when a certain update that is posted to f95zone was originally published by the author, not when the game as a whole was originally released. so i think that this behavior is acceptable, and will prevent "fake updates" from showing up when mods edit the thread updated date without an update.
auto-update for public release is already a thing
I'm considering adopting a system similar to what I use for flipper stuff however. Since with the cache api I now have a server dedicated to this project, I could easily also host a update indexer on it, which will serve a json of the latest versions, and gets built binaries sent to it by GitHub actions. Would make it trivial to have a beta update channel. But that's for after 11.0 release
well nothing i can do about that, the mod published the update and changed the date after. the api cached the new data, but the date was changed after. only place i can reliably get a last updated date is by fetching the whole thread, and this is not possible to do all the time. it monitors latest updates to detect other changes quicker, but that does not give a date or a time, it gives how long ago in human readable form, which i cant use either and it horribly rounded.But as you can see, the Last Updated date was changed on F95 but not in your cache. These were new versions, it picked up the new version number.
tell them to fix it thenThen there is this one that will be on the top of the Last Updated list for quite awhile due to someone fat fingering the date.
yea, thought about ways to do it, but is it worth it for beta?
Agreed, auto update would be best just for stable version. But if you do move forward with auto-update of beta versions can you have it back up the database and add a setting to turn off auto update?yea, thought about ways to do it, but is it worth it for beta?
theres the risk everyone on beta updates to a buggy release that breaks their db then good luck dealing with the fallout
one benefit would be so that everyone who is ok taking the risk will be on the latest so they can be your "beta testers", easier than asking them to manually update
yeah thats true, but i think ive started to have a better development cycle lately. i dont push to main unless ive tested it myself and im confident it wont atleast cause irreparable issues. that work in progress stuff is reserved for separate branches, which i didnt use much in the past but started really using lately on other projects and now here too. its a bit weird making pull requests to my own project but it means that its a more sane development cycle and stops me from merging something stupid as i re-read everything before merging.yea, thought about ways to do it, but is it worth it for beta?
theres the risk everyone on beta updates to a buggy release that breaks their db then good luck dealing with the fallout
one benefit would be so that everyone who is ok taking the risk will be on the latest so they can be your "beta testers", easier than asking them to manually update
