Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: support for SteamPipe custom folders in fastdl module #1521

Open
ghost opened this issue Jul 10, 2017 · 0 comments
Open

Suggestion: support for SteamPipe custom folders in fastdl module #1521

ghost opened this issue Jul 10, 2017 · 0 comments
Labels

Comments

@ghost
Copy link

ghost commented Jul 10, 2017

I would like to suggest adding support for SteamPipe custom folders in the fastdl module. Details on this can be found here : https://support.steampowered.com/kb_article.php?ref=7388-QPFN-2491

Why do this? Well for one it's an official feature that probably most source servers are using (at least in tf2). Secondly there's no point in wasting time and resources by copying the stock maps from the default directories. In TF2 for example the fastdl command copies and compresses around 4 gigs from just the stock files alone. And it does this every time the command is executed, which leads me to my second suggestion.

I think it would be beneficial to run checksums on files to determine whether or not they should be copied and compressed. There's no point in re-compressing the same files over and over right?

So for example, rather than doing tf/maps, you would be checking tf/custom//maps

Just some ideas.

@dgibbs64 dgibbs64 added the type: feature request New feature or request label Jul 21, 2018
@dgibbs64 dgibbs64 removed type: feature request New feature or request labels Feb 1, 2019
@dgibbs64 dgibbs64 added the type: feature request New feature or request label Jun 20, 2019
@dgibbs64 dgibbs64 added Epic and removed Epic labels Nov 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant