Page 1 of 1

Display Client's Modified Files to Client

Posted: Tue May 10, 2022 8:20 am
by Jakob Hubbard
Since there's already a checksum system in place that checks clients tracks vs server's tracks, I'm wondering how difficult it would be to display to the client what files are different from the servers?

Ex.
Client track modified - does not match server's track (track_folder_name)
Client files modified -> statue, tileinfo, decals, etc.

I had a headache trying to figure out why my version of a track I pushed to GitHub and the same version someone downloaded had caused a client track modified error and I feel like it would be useful for players to know which files are incorrect so it makes it easier to debug and fix.

Re: Display Client's Modified Files to Client

Posted: Tue May 10, 2022 5:17 pm
by BcMxKx37
:?

Re: Display Client's Modified Files to Client

Posted: Tue May 10, 2022 10:22 pm
by baker
Jakob Hubbard wrote: Tue May 10, 2022 8:20 am Since there's already a checksum system in place that checks clients tracks vs server's tracks, I'm wondering how difficult it would be to display to the client what files are different from the servers?

Ex.
Client track modified - does not match server's track (track_folder_name)
Client files modified -> statue, tileinfo, decals, etc.

I had a headache trying to figure out why my version of a track I pushed to GitHub and the same version someone downloaded had caused a client track modified error and I feel like it would be useful for players to know which files are incorrect so it makes it easier to debug and fix.
+1 otherwise just a guessing game right now

Re: Display Client's Modified Files to Client

Posted: Wed May 11, 2022 1:55 am
by jlv
All the server knows is the hash from the trackinfo file. What I need is a /listtrackfiles command so you can see where the files opened in the process of loading the track came from.

Re: Display Client's Modified Files to Client

Posted: Wed May 11, 2022 11:42 am
by Jakob Hubbard
jlv wrote: Wed May 11, 2022 1:55 am All the server knows is the hash from the trackinfo file. What I need is a /listtrackfiles command so you can see where the files opened in the process of loading the track came from.
Anything to help would be nice in the future