Dalamud plugin for rendering browser overlays in-game.

Enables you to play in fullscreen (and G-SYNC) while having access to e.g. ACT overlays.

This project is a fork off ackwell's BrowserHost plugin (https://github.com/ackwell/BrowserHost). The original scope of the project was to add Endwalker support and nothing more. However since then a few new features and improvements have been added:

• DPI awareness
  • The displayed browser overlays are scaled correctly in regards to your display's dpi. This essentially means you get the same sized output as you get from your browser.
• Zoom support
  • Overlays can be zoomed in and out to make them smaller and bigger, same way your browser's zoom works.
• Opacity support
  • Make your overlays as transparent as you like.
• Framerate configurable
  • The rendering framerate for each individual overlay can now be set.
• Disable support
  • Completly disable an overlay without deleting it.
• Mute support
  • Can mute specific overlays.
• ACT optimizations
  • Optimizes the overlay handling for ACT overlays. Also enables and disables them depending on if ACT itself is running.
• Updated Chromium version
  • 108.0.5359.125
• Project cleanup
  • Everything now uses .net 7
  • Nullable enabled
  • DalamudPackager for easier deployment
  • Some source cleanups
• Minor stability improvements

The initial release focused on making the overlays work again, the focus now rests on rewriting core parts to make the plugin more robust and easier to maintain.

You can also open an issue for new feature requests.

For ACT overlays to work correctly the overlay WSServer has to be enabled. ACT also provides an URL generator that will create the correct URLs to use within Browsingway:

You might also want to enable 'ACT optimizations' inside Browsingway for the specifc overlays, this will also enable and disable them automatically if ACT is running or not running.

Browsingway works in Linux, but is experimental and not supported.

• Newer versions of Dalamud / XIVLauncher.Core include the necessary .NET dependencies, so you should not install your own into the Wine/Proton prefix - they can conflict and cause crashing issues.
• If you encounter performance issues, try using a more recent version of Proton to run FFXIV. Proton-GE 10.27 works well, but others may also.
• You may need to use a custom fork of XIVLauncher in order to change Wine/Proton versions.

• Delete the contents of ~/.xlcore/pluginConfigs/Browsingway. This should cause the plugin to reinstall CEF on next launch. This is most likely to help if you've switched Wine/Proton versions since installing CEF (XIVLauncher may do this on its own as part of its own updates, though this is rare.)
• If your Wine version has changed, you may need to clear your Wine or Proton prefix. This can be done from the Wine tab in XIVLauncher's settings.