[DiscordArchive] Arent you going the "We are going to support more than 3.3.5"-route?
[DiscordArchive] Arent you going the "We are going to support more than 3.3.5"-route?
Archived author: Saty • Posted: 2025-09-21T22:45:42.725000+00:00
Original source
Arent you going the "We are going to support more than 3.3.5"-route?
Archived author: Saty • Posted: 2025-09-21T22:46:04.922000+00:00
Original source
Like what I am saying is purpose built for one specific, never changing version.
Archived author: Titi • Posted: 2025-09-21T22:47:14.047000+00:00
Original source
in the future if possible, but adding core features to 3.3.5 is first priority. And I'd argue you're doing the same mistake you're calling with versioning, "my tool does all" but also is only usable for one version
Archived author: Titi • Posted: 2025-09-21T22:47:22.846000+00:00
Original source
it can't be standard if it's only one version
Archived author: Titi • Posted: 2025-09-21T22:47:49.792000+00:00
Original source
also getting compatibility with classic clients so the community can eventually move on to classic clients is important imo
Archived author: Saty • Posted: 2025-09-21T22:48:08.621000+00:00
Original source
There is no point in supporting more than 3.3.5. It only adds headache.
If there is another version worth porting too, it will be a completely different program
Archived author: Titi • Posted: 2025-09-21T22:48:51.423000+00:00
Original source
that just fragments the community between more tools
Archived author: Saty • Posted: 2025-09-21T22:49:13.469000+00:00
Original source
The modding community I would say is like 90% or higher on 3.3.5
Archived author: Titi • Posted: 2025-09-21T22:49:37.252000+00:00
Original source
well if there are support for it, 90% would move to 3.4...
Archived author: stoneharry • Posted: 2025-09-21T22:50:20.192000+00:00
Original source
If you're just editing the DBC tables you might as well import it to SQL and all the benefits that brings.