UEFN Instances where notification would be helpful:
- When you attempt to launch a session but your Fortnite is already in a separate session. UEFN will say session is loading, meanwhile Fortnite is in the background with a prompt to join the new session. There’s no indication that this is the case and is implied to be working by UEFN saying session loading. This can also lead to the server not launching if you don’t realize it’s in this state for long enough.
- When you click build verse code from Visual Studio, it sometimes pulls up a save dialog in UEFN. Sometimes this leads to the developer waiting for the build successful message not realizing they need to tab back into UEFN and click save on the dialog.
- When you build a private code, it tends to put the generated code window behind other UEFN windows.
- These problems are especially prevalent on a dual monitor setup. If I’m tabbed into another program, or I have a separate UEFN window open on the other monitor, it will sometimes put important dialogs behind the Window up on the other monitor.
These are just a few of the times I can think of when a notification would be useful in UEFN. It would be a huge positive for user experience, time management, and workflow by adding a notification of some sort when important actions are needed to proceed. It would also be helpful to have notifications for instances where the server failed to launch.