Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
what dis?
sorry me stupid but i installed this mod earlier today and it worked and made my days longer and now i get this error code
Another solution would be to edit your world's rights.config file to include the "owner" and "tutorial" permissions.
If you need help with either of those two solutions, do let me know!
I'll keep on trying to find a simpler, easier way to go about this. Perhaps an in-game command?
Your file will likely look something akin to this:
{
"byUid": {
"steam_USER_ID_GOES_HERE": {
"rights": [
"tutorial",
"owner"
],
"username": "USERNAMES_GOES_HERE"
}
}
}
Reason for this is because sundial works on a per world basis, in case you want to have different settings for each world.
For the first issue, I recommend running the Staxel Content Builder. The steps for doing so are in the troubleshooting section of the description.
As for the second, it's likely that the Staxel client froze and missed its window of opportunity to respond to the mod check request. Details on how the process works, as well as instructions on how to fix this issue, are listed in the pinned thread, Modifying the Mod Detection Process .
If you encounter any more issues, or would like help fixing the above, do let me know.
If this is ever fixed, it's going to change the game for multiplayer games.
If, however, mod support were to be added, whether officially or via a community project, then there's a chance I'd port Sundial over to it. Here's to hoping it'll be possible, someday!
Check out the pinned post for more details.
Well, that was a biiit quicker than expected, so I'm hoping it's not too buggy. Do give it a try and tell me if it's any good.
How quickly would you like an update? I'm currently debating whether to push out a simple update to Moonbow that would allow for custom timeout length for the mod detection process (0.4.1), or keep it for a larger update that should hopefully allow for custom UI elements (0.5). No ETA on the latter, though; I'm still trying to figure out how I'd like to structure everything to be easy to understand and mod.
For now, though, one workaround should be to disable Sundial by deleting the config file (located in your world's save folder), and re-enable Sundial once in-game by using the SetDayLength command. Do give it a try and tell me if it works!
Again, thank you so much for the detailed bug report. It really does help a lot.
I'm assuming you were the host for the multiplayer world? Typically, I've only ever seen the issue occur for the host; guests seem to have no problem.
Though I'm not entirely sure what is causing the TranslationException, I do have one theory on why this disconnection issue is happening. Sometimes, the client and/or server freezes for a few seconds while the world is loading, and messes with mod detection. This, in turn, causes Sundial to not detect you have the mod installed, despite you very clearly having it.
You can't tell if the server has frozen (unless you have the server console open and are actively monitoring it), and the only indication that the client has frozen is a stutter or freeze in its loading screen animation, making this a frustrating issue to even notice.
After installing, the mod worked fine for the first session in a multiplayer world. I set the day cycle to 45 minutes.
The next day when I tried loading the world, I got the message "Staxel.Translation.Translateexception: Mods.sundial.hooks.Sundialhook.disconnect." and the world would not open. I ran the content builder in the mod manager, and restarted the game. Nothing.
I uninstalled and deleted the mod entirely, restarted the game. The world works fine without the mod.
Reinstalled the mod fresh and restarted the game, but the world gave the same error message again and refused to load.
I am playing the game in English.
The only other mods I have on are some player species mods, color mods, and moonbow.
Honestly the days feel way shorter than that tbh. I'd maybe just increase it 50% to 33 minutes, perhaps double the original to 44 if that's still feeling short.
Staxel's default day length is 22 minutes , and as Sundial does not modify this value unless instructed to, you can verify this with the CheckDayLength command.
Joining a world with Sundial enabled, whether singleplayer or multiplayer, will indeed synchronize the client's visual day length, but will fail to revert to the default value upon leaving. If you then join a world that does not have Sundial, the client will keep the previous world's day length, causing a mismatch between server and client. Restarting the game fixes the visual issue, but it will occur again upon joining a modded Sundial world.
Honestly, that wasn't your fault, either: if translations had been working, they would've informed you that you needed to provide a number of minutes, haha. Just one issue leading to another.
Could you try running the Content Builder and see if that fixes the issue? From the Steam launch options menu, choose Mod Manager Tool , wait for it to load all the mods, then choose Run Content Builder from the Tools menu at the top.
When using the SetDayLength command, what are you typing? Is it solely "/SetDayLength" without any number? If so, provide a number afterwards, such as "/SetDayLength 10" (without the quotes, case-insensitive).
And when I type "/checkdaylength" I get "response" as a reponse.
Any idea what I'm doing wrong?
1. Open Staxel's installation folder. You can do this by selecting "Browse local files" or similar from the additional options menu on the game page in your Steam library.
2. Open the LocalContent folder. This is where world saves are kept.
3. Open your world's save folder. It will have the same name you gave the world when first creating it.
4. Open the Mods folder, then open the Sundial folder. This is where Sundial keeps the custom day length.
5. Delete or rename the config.json file. This will force Sundial to be disabled for that world.
With that, you should be able to join your world again. Using the SetDayLength command will re-enable Sundial.
If the error happens again after using the command, could you try joining the Staxel Discord server [discord.gg] to be able to share the game logs?
1. Staxel is failing to translate the message.
2. Sundial isn't being detected, despite being installed.
Are you playing on a singleplayer world? Is your game's language set to one other than English? I'm confused as to what's causing these two issues. Sundial should be detected, and Staxel should serve the correct translation.
If it helps, translations are used when using the help , SetDayLength , and CheckDayLength commands. They are also used when synchronizing day length, which occurs when joining a world with Sundial enabled or after the SetDayLength command is used.
Once those two things are known, there's a good chance of tracking the issue down and getting it fixed.
1. Figure out a way to get the command to work without enabling cheats.
2. Create a separate mod to add a command to disable cheats so achievements are re-enabled.
I'll start working on the second one for you. Sorry for the inconvenience.