Search results

It's optional, so just don't click on the buttons.

Resize the plugin window slightly.

If you have an account-wide webhook set up, then I believe so. I could have a way to disable them for a specific mod, but you could also put in a bogus URL for the unlisted mod as a workaround in the meantime.

You are entitled to call your empty mod "passive", but the fact remains that it is completely empty. It has no effect. We are not interested in hosting non-functional mods. I did not think this would need to be stated in the rules, but I'll add a policy item about it tomorrow. You could...

Hi there. Your initial mod upload had an AI-generated cover image, which violated the mod rules. This was actioned by hiding your mod until you removed all AI-generated content. You instead deleted the mod and uploaded it again without an AI image, which does not let the moderators verify that...

I like the idea! It does seem pretty niche, but I can see the utility in it. The technical aspect of it should be pretty easy. The UI/UX I'll need to ruminate on.

Having the game and a browser open creates an environment that surfaces the hardware (or possibly driver) fault. It sounds like a RAM issue to me because you list scenarios of high RAM usage as when things go wrong. Either way, Heliosphere is not the root cause of your BSODs or crashes; we would...

No idea, but this is definitely a hardware issue. I wish you luck. Edit: my first place to look would be your RAM. memtest86+ would help there

As of Chrome version 142 (and other browsers based on Chromium), requests to localhost require a new permission. Heliosphere does not yet ask for that permission by default. I will be updating the site soon to fix that, but if you are having issues getting Chrome to connect to the plugin, there...

Check here and report back.

I have a hunch that setting the prefix to report Windows 7 in XL might bypass the access denied error, but it's just a hunch.

Firstly, never run 14/XL as admin. Secondly, this is a timeout error. There is nothing I can do to fix this. Somewhere along your network path has an issue. See this post.

Yup, you'll have to diagnose that yourself. That is the problem, though. Wine/the system/something is denying access to the http server starting.

My only advice is to make sure 4.5.0 is installed before you start the game with debug logging enabled. There's nothing else I can do at this point, since it does log all errors now.

4.5.0 should show the errors now, hopefully. Make sure you've set the log level to Debug first.

This is now available in 4.5.0. You first have to click the version number at the bottom of the Settings tab seven times to get the "Unsupported options" section to show up.

Move your "FFXIV mods" folder to a location that is not in OneDrive. Afterwards, open Penumbra's settings and change the root folder to where you moved it. Heliosphere automatically uses Penumbra's root folder, so you don't need to do anything special for Heliosphere.

Please read the error message. Heliosphere is refusing to install a mod in your OneDrive. Do not use OneDrive for mods; it is notorious for causing issues that are hard to debug.

The error changing doesn't matter as long as that button is there. That button only appears if the server failed to start and isn't currently started.

Hi! This is not a WCIF (where can I find) forum. I don't know where people do that, but it's not here. I think there are Discord servers for that purpose.