Help talk:Style guide/Bugs

Two potential changes

I'll just get right into it:

1. Adjust the "Bugs should be able to happen while playing a regular, non-modified game/server." guideline to exclude game-sided bugs. E.g., a bug with sv_pure 1 is that having a custom taunt sound causes the default sound of the taunt to slow down and play for the duration of the modified file. This is an issue with sv_pure not properly handling the custom files, rather than a bug caused by the custom files itself. An example of a bug with custom files is that things will lose their team colour if you select the RED/BLU buttons on the Loadout menu on custom HUDs, because they change the materials, but if this is kept that way on sv_cheats 1 servers it will keep the modified materials meaning everyone is on the same team.
   The difference here is that this bug was created by custom files, while the custom taunt sound bug is created by an in-game command not working properly but it merely involves custom files.

1. Bugs produced by setting values of certain console commands higher than intended should not be covered. This sounds very broad, but it really isn't. A good example is that the Shortstop's viewmodel shows a bunch of bullets at higher values, but at 70 (which is what the intended limit is as indicated by the game's slider in the options menu) these are not visible. People putting the viewmodel_fov to a higher range than it's meant to is obviously going to produce artifacts like that, so we'd have to put an artificial limit on these kinds of things (e.g. do we count up to values of 90? Or 110? Or the max the command allows?), or just altogether agree it's a bit silly to document a bug like this.

I hope it was all clear.
| s | GrampaSwood (talk) (contribs) 02:07, 6 June 2024 (UTC)