28-01-2026, 01:15 AM
Hello!
Yes, that's still the place to look at. Once the Evolution branch is merged into the master branch, we are probably going to rely on the SVN more directly.
The fact that you don't see updates on either repo comes from the fact that many changes happening behind the scenes to old & new tracks have not been pushed on a public repo yet.
I would suggest having a small document in which you write down issues you notice for now, but waiting around for an official alpha/beta to test if those are still applicable, and then telling us what those issues are, either here on the forum or via a ticket on GitHub.
An exception would be tracks that are already released in 1.5 (or its gift package), where I don't think you need to wait to report relevant issues, as those tracks are not WIPs. Although don't bother with Snow Peak, Fort Magma, Scotland and Minigolf, as those tracks are going to be either removed or completely redone.
(23-01-2026, 07:59 PM)VisitingPlayer Wrote: If I wanted to have the most up-to-date state of development, is the GitHub repository for the assets still the right place to look? Or have the Evolution assets since moved to the SVN repository (or another place for that matter).
Yes, that's still the place to look at. Once the Evolution branch is merged into the master branch, we are probably going to rely on the SVN more directly.
The fact that you don't see updates on either repo comes from the fact that many changes happening behind the scenes to old & new tracks have not been pushed on a public repo yet.
(23-01-2026, 07:59 PM)VisitingPlayer Wrote: Also, suppose I play around in a development build and find an issue with the tracks, like the one mentioned above with Fort Magma's skeleton, where should they be discussed? Or should I maybe just let you work on it for now until some official alpha?
I would suggest having a small document in which you write down issues you notice for now, but waiting around for an official alpha/beta to test if those are still applicable, and then telling us what those issues are, either here on the forum or via a ticket on GitHub.
An exception would be tracks that are already released in 1.5 (or its gift package), where I don't think you need to wait to report relevant issues, as those tracks are not WIPs. Although don't bother with Snow Peak, Fort Magma, Scotland and Minigolf, as those tracks are going to be either removed or completely redone.