If you run linux and you'd like to try the new libunwind integration, it can produce nicer + more precise stack traces for you during your testing. You just need to have the libunwind library installed, then clone + build the following git repo:
https://github.com/MajBoredom/spring
It is in the "threadtrace" branch, based on 96.0.
libunwind feature branch ready for testing
Moderator: Moderators
Re: libunwind feature branch ready for testing
testing happens in the develop branch... can you merge my pull request please?
https://github.com/MajBoredom/spring/pull/1
fyi: you easily can test many stuff with:
there is really no need to develop on the master branch. its very difficult to merge the changes into the master branch because of merge conflicts, also its very error-prone. for new stuff please always use the develop branch, never the master branch! in current state the changes won't / can't be merged. also i refuse to test it as the difference between develop and master branch is way to big! the output of git diff / gitk / ... for reviewing the code changes is useless atm.
https://github.com/MajBoredom/spring/pull/1
fyi: you easily can test many stuff with:
or/cheat
/give all
/give all 1
i wrote this already in lobby, but for the reference again:/cheat
/crash
there is really no need to develop on the master branch. its very difficult to merge the changes into the master branch because of merge conflicts, also its very error-prone. for new stuff please always use the develop branch, never the master branch! in current state the changes won't / can't be merged. also i refuse to test it as the difference between develop and master branch is way to big! the output of git diff / gitk / ... for reviewing the code changes is useless atm.