#help me if you like playing minigolf while mad drunk
1 messages · Page 1 of 1 (latest)
@grave fern
The issue you are having is not caused by txAdmin.
If you just updated txAdmin, the issue is likely to be caused by a change in the FXServer artifact/build. Since txAdmin comes with FXServer, the recommended way to update txAdmin is by updating the artifact, but this is not strictly required. If you want to downgrade the artifact version, type !manual for instructions on how to keep txAdmin updated even if you downgrade the artifact.
Other possible explanations:
- The OneSync option configured in
txAdmin > Settings > FXServermight be different from the one you were using before. - You selected different
server dataorserver.cfgfrom what you were using previously. - If txAdmin restarted your server, it was either because it crashed or hang - with exception for the "failed to boot in time" error which can be solved by increasing the time limit in the settings page.
!rollback @grave fern