-forceupdate don't work.
Hey ! -forceupdate don't work anymore.
I close, because obviously the problem will never be solved. If it's to release broken versions, we might as well do nothing.
Hello! I understand your frustrations with the slow pace of development. Unfortunately, TShock is an open-source project composed of volunteer work, and no one's free to do address this specific issue at the moment. The issue has already been confirmed(on Discord), if you would like to submit a PR, feel free to
Related to issue #2205
Hello! I understand your frustrations with the slow pace of development. Unfortunately, TShock is an open-source project composed of volunteer work, and no one's free to do address this specific issue at the moment. The issue has already been confirmed(on Discord), if you would like to submit a PR, feel free to
Hello! First of all, thank you for your answer...I must confess that I am quite frustrated about this error. I'm not a coder but I had to create an alternative...I just find it a shame that such an important feature is broken. Sorry if my answer offended some people, it was not my intention, have a nice day everyone.
As said on Discord, even if the update do run, there are still many things that won't update - for example, trees don't grow during the update, but only when player nearby.
You can fix it via several lines of code:
On.Terraria.Netplay.UpdateConnectedClients += (On.Terraria.Netplay.orig_UpdateConnectedClients orig) =>
{
orig();
if (ServerApi.ForceUpdate)
{
Terraria.Netplay.HasClients = true;
}
};
What alternative? On Apr 10, 2023 at 12:22 +0900, C0sm0s-Chill @.***>, wrote:
As said on Discord, even if the update do run, there are still many things that won't update - for example, trees don't grow during the update, but only when player nearby. Thank you for your help, I found an alternative less greedy in cpu / ram, I tried this code it takes me 20% more cpu and more than 150 mo ram, but thank you very much. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>