#✅ | Browser element info saving

1 messages · Page 1 of 1 (latest)

ionic coral
#

Where does the browser element save the info ?
Let's say that i add a browser element with a website url. When i login on that website where is the info saved so that i dont include that when exporting the modpack ?

sudden fiberBOT
#

Hi! 👋 Please first click the button below to start this support ticket.

⚠️ It is not possible for anybody to send messages in this ticket before it has been started, so you need to click the button for others to be able to help/answer you.

sudden fiberBOT
# ionic coral Where does the browser element save the info ? Let's say that i add a browser e...

The FancyMenu documentation does not specify where login data from the Browser element is stored. The website may save it as browser cookies, local storage, or another MCEF/Chromium profile, but its exact location is not documented.

For exporting a FancyMenu setup:

  • Layout files are stored in <game-directory>/config/fancymenu/customization/.
  • Local assets are stored in <game-directory>/config/fancymenu/assets/.
  • The recommended export is to copy only the required <game-directory>/config/fancymenu/ files and referenced assets, not the entire Minecraft instance.

To avoid accidentally sharing a logged-in session:

  1. Do not include the entire game/instance directory.
  2. Export only the FancyMenu configuration and assets needed by the layout.
  3. Before sharing, test the exported setup in a clean instance and verify whether the Browser element is still logged in.
  4. For extra safety, log out of the website or clear its cookies/site data before creating the export.

I can’t confirm a specific MCEF browser-profile path from the available documentation, so if the session persists after exporting only the FancyMenu folder, please ask for human help regarding MCEF’s storage location. 🧭