The way it is set up right now, .vcd files are required to be compiled in a scenes.image binary blob file before they can be used. This implementation was originally introduced for consoles on retail TF2, as optical media had very poor random read/write speeds.
Current PCs do not have this limitation, and the performance impact of discarding this system would be very negligible. This would allow modders to implement custom taunts and use them in their servers.
The ideal way to do this would be to allow the special taunt attribute to accept a .vcd file path as its value, so weapons can have a custom taunt set up via their item schema entry
The way it is set up right now, .vcd files are required to be compiled in a
scenes.imagebinary blob file before they can be used. This implementation was originally introduced for consoles on retail TF2, as optical media had very poor random read/write speeds.Current PCs do not have this limitation, and the performance impact of discarding this system would be very negligible. This would allow modders to implement custom taunts and use them in their servers.
The ideal way to do this would be to allow the
special tauntattribute to accept a .vcd file path as its value, so weapons can have a custom taunt set up via their item schema entry