Delete Guides/Custom_hitsound_library

[Walavouchey]

contains mostly dead links
save for random s-ul links in random guides, i can't find any similar resource that is maintained that we could potentially yoink for this
is there interested in resurrecting this, potentially by gathering some commonly used sample packs and uploading to assets.ppy.sh? EDIT: yes and hivie is working on it so this pr is drafted for now

• slightly unsure how the outdating workflow with squash merging is going to work for Guides/Using_custom_hitsounds

[TicClick]

1. no way
2. unfortunately yes, as random links aren't well-maintained.

is there interested in resurrecting this, potentially by gathering some commonly used sample packs and uploading to assets.ppy.sh?

would be interested in knowing the answer as well -- there certainly is (a weak?) demand for a library

slightly unsure how the outdating workflow with squash merging is going to work for Guides/Using_custom_hitsounds

why the confusion? if a translation is edited in any way (or specified in the PR's body), it's not going to be outdated. if it is left as-is, then it's going to be outdated if no outdated_translation tag is already present.

[UnknownOsu]

Suggested change

	Para poder usar hitsounds personalizados en tu beatmap, ¡primero necesitarás algunos! La biblioteca personalizada de hitsounds es un gran recurso para obtener muestras de sonido, incluyendo platillos, tambores, campanas, silbatos y mucho más. Alternativamente, si no encuentras lo que buscas, ¡puedes hacer tus propias muestras!
	Para poder usar hitsounds personalizados en tus beatmaps, primero necesitarás algunos. Busca muestras de sonido en internet, y si no encuentras lo que buscas, ¡puedes hacer tus propias muestras!

[Walavouchey]

is there interested in resurrecting this, potentially by gathering some commonly used sample packs and uploading to assets.ppy.sh?

would be interested in knowing the answer as well -- there certainly is (a weak?) demand for a library

@Hiviexd seems to be poking around gathering commonly used hitsound packs (so i'm drafting this for now)

why the confusion? if a translation is edited in any way (or specified in the PR's body), it's not going to be outdated. if it is left as-is, then it's going to be outdated if no outdated_translation tag is already present.

i'd normally want the translations of those to be outdated, because i'm not able to update all the wording in the translations, but i needed to remove the broken links as a result of the deletion. in this case, i'd manually outdate the translations (while still editing them in this pr), but since all the commits in this pr will be squashed, i'm not sure if the commit reference would be valid

would i just add outdated_translation but not outdated_since?

[TicClick]

would i just add outdated_translation but not outdated_since?

I think as long as there is an edit, it won't do anything to the files.

however, you can cheat a little and outdate them manually using the hash of a commit in master that your pull request will land after

[Walavouchey]

i think we'll need a pr description tag for the outdater to outdate the translations anyway <.<

[peppy]

Can we merge this and get it over with? Or still stuck on some tooling?

[Walavouchey]

no, this is drafted because another solution is in the works

is there interested in resurrecting this, potentially by gathering some commonly used sample packs and uploading to assets.ppy.sh?

would be interested in knowing the answer as well -- there certainly is (a weak?) demand for a library

@Hiviexd seems to be poking around gathering commonly used hitsound packs (so i'm drafting this for now)