why is so many trains here
Merth1 opened this issue ยท 18 comments
Is this a new world? Are you updating from an existing world? Have you tried changing the train type at the siding? Also duplicate of #401.
The best solution I can think of is to update to 3.1.2, change the train type in all the sidings then refresh and clear
Also worth mentioning is that architectury is for forge, not fabric, so I suggest to remove it
Thanks kettle-7. Let me check your suggestions and get back. I forgot to mention that I'm using TLauncher. Architectury might be the culprit.
I guess the curved portions of the tracks should be large enough to accommodate the size of the trains, too (unlike mine!).
Cheers.
Thanks kettle-7. Let me check your suggestions and get back. I forgot to mention that I'm using TLauncher. Architectury might be the culprit. I guess the curved portions of the tracks should be large enough to accommodate the size of the trains, too (unlike mine!). Cheers.
Cracked Launchers of Minecraft Are not Supported.
This seems to be an issue of TLauncher. Since we know very little about the differences between minecraft started with TLauncher vs other launchers, it's really hard to tackle this issue.
Hello guys, what's the language of your Windows and minecraft? @Merth1 @kaan-guven
Hello guys, what's the language of your Windows and minecraft? @Merth1 @kaan-guven
My windows language turkish and minecraft tlauncher Minecraft language:English
Very strange, but everybody who has this bug seems to have their windows locale set to Turkish
Found the issue! https://stackoverflow.com/questions/11063102/using-locales-with-javas-tolowercase-and-touppercase
I'm suspecting it's my default .toLowerCase()
string calls which are affecting train ID values like TRAIN_24_2
-> train_24_2
.
Very strange, but everybody who has this bug seems to have their windows locale set to Turkish
Yeah, I think it's definitely about Turkish, I have the same problem. (Windows lang=TR Minecraft lang=EN) Also, I noticed that this problem doesn't occur in v.3.0
@Merth1 @kaan-guven @bekase Please try the latest version, 3.1.5, and see if it fixes this issue!