#🙋 | server creation
1 messages · Page 1 of 1 (latest)
Hi! Please first select which type of question you want to ask:
- "Normal Question" is enough for most questions. If you are unsure, you should choose this mode. It provides quick and accurate answers to your questions and problems.
- "Complex Task" is for very complex questions and multi-step tasks. For example, questions involving complex action script, requirement, or placeholder logic. Normal users will almost never need this. Getting answers takes much longer here.
It is not possible for anybody to send messages in this thread before selecting a mode.
Selected mode: 🧠 Complex Task
I’m checking this with the docs first and then I’ll look for similar bug reports on GitHub 🧐 If it turns out to be an actual FancyMenu issue, I’ll tell you the safest workaround I can find.
I checked the docs and GitHub for similar reports; nothing exact showed up yet, so I’m doing one extra pass for context 🔎 If I find a known workaround, I’ll give you that instead of guessing.
I found a docs page that explains FancyMenu uses screen identifiers for layouts and screen-specific behavior, so the server.ip:port thing may be an internal identifier rather than a true duplicate 🧩 I’m checking one last time whether there’s any documented way to stop that behavior.
Hey 🙂 I checked the docs and I couldn’t find any documented setting that would stop that behavior.
What FancyMenu does document is:
Join last world/serverjust joins the last world or server.- FancyMenu uses screen identifiers for world/server loading screens.
- Those loading screens can be opened as dummy screen instances for customization.
So server.ip:port is very likely an internal per-server identifier, not something you can turn off with a normal option.
If it’s just showing up as the identifier, that’s probably expected.
If it’s actually creating duplicate entries every single time you join, then that does look more like a bug/odd behavior, and I didn’t find a matching GitHub issue for it.
Small workaround: if you don’t specifically need “last server”, use the normal Join Server action with a fixed address instead.
If you want, send me your logs/latest.log from right after it happens and I can take a closer look 👀
The file latest.log is a Minecraft log file.
1.21.11
Fabric 0.19.2
212
41 error(s), 449 warning(s), 46 exception(s)
21
Dynamic FPS, Entity Culling, FerriteCore, Iris Shaders, Krypton, Lithium, ModernFix, Sodium
FancyMenu v3.9.1
SpiffyHUD v3.1.2
Konkrete v1.9.18
Melody v1.0.15
I spotted a latest.log attachment, so I’m checking it now in case it explains the server-instance behavior 📄🔍 If it’s relevant, I’ll give you a more precise answer instead of just the generic workaround.
I found actual FancyMenu log activity around joining a server, but it’s showing a file-copy action error, not anything about the server.ip:port instance itself 😕 I’m checking whether that error is tied to your menu or just a separate config issue.
Thanks for the log 📄🙂
I don’t see anything in it that clearly says FancyMenu is “creating a duplicate instance” as a built-in bug. What I do see is this on server join:
ScreenCustomizationLayer registered: direct_join_server_screenScreenCustomizationLayer registered: connect_screen- a
CopyFileActionrunning from aTickerElement - the path includes the server address:
.../play.pika-network.net/...
So this looks more like a server-specific action/config setup in your menu than the plain Join last world/server action itself. The log also shows the copy action failing (FileNotFoundException / FileAlreadyExistsException), so that part is definitely misconfigured.
Short answer:
- Is it a bug? I can’t confirm that from this log alone.
- Can you prevent it? There’s no documented option I found to disable the
server.ip:portnaming/instance behavior directly. - Best next step: check any ticker/action that runs on
connect_screenordirect_join_server_screen, especially anything using server-IP-based paths orlast_world_server/ server IP placeholders, and disable/test that first.
If you want, send me a screenshot of the action script or the relevant layout and I can help spot the exact thing causing it 👀
<@&1365490168563372113>
@acoustic ingot has requested human assistance.
A human moderator will help as soon as possible.
🙋 | server creation
Editing messages does not change the AI conversation history. Alice will continue to see and use the original message text that was stored before the edit.
Can you show me the action script of the element?
nothing too crazy
I’m checking the screenshot now to make sure I read the action script correctly 🖼️🙂 If it really is just that one action, I can tell you whether it points to the issue or not.
@astral cobalt paused AI answers for this thread.
The current AI turn was stopped.
Editing messages does not change the AI conversation history. Alice will continue to see and use the original message text that was stored before the edit.
it creates for example mc.anarchadia.org:25565 server
in server list
even if it's already added
Maybe because the server is cracked?
Have you tried it with a normal one?
I tried it with like three
but niche
It might be a bug
Because you aren't doing anything extra
I may have an idea why this is happening
it does it for all servers i tried
oh okay
When you click the button
yes
It should normally just join the IP
But it triggers the action 'add and join'
Not just 'join'
so can I fix it? or is it a fancymenu bg
yes but I also tried that with open screen actionscript for a custom gui
Add it in the multiplayer menu and check
Then it might work
But yeah it's probably a bug that needs to be fixed
okay 1 sec
Editing messages does not change the AI conversation history. Alice will continue to see and use the original message text that was stored before the edit.
it happened again
Editing messages does not change the AI conversation history. Alice will continue to see and use the original message text that was stored before the edit.
I think I uninstalled them all for this purpose
Still, show me your modlist just in case
I think there are some mods that are incompatible with fancy meni
if it is then I'll try to bypass it with server leave listener, fm variables and join server action
I thought incompatibilities only affected menus, not functions like that
I'm not sure
since everything else work properly and I disabled every ui
okay
Editing messages does not change the AI conversation history. Alice will continue to see and use the original message text that was stored before the edit.
ohh all right
I think I was wrong about the reason
It makes a new one to join
The name
It uses the ip as the name
And it doesn't find it
So it makes a new one
And joins that
yes i added it without port and it isn't in the name then
It won't make more unless you change the name or delete the new instance it made
I fear that's the only solution for now
it seems like there isn't a bypass
You should report this in Github
server leave listener only can get ip so that's the same issue
okay thanks for checking
It won't make more than one
And I don't think you would care much about the name right?
Better use it like that till it's fixed
I mean that's quite annoying
yes there is no other way anyway
I'm wrtting a github report
thanks for he help
Okay Good luck