There are so many things I would like to say, but, at the same time, I don't want to. It feels so devastating, heavy, and tough... And yet, we move forward. Forever and Ever.
おはよう, good afternoon, good evening, and good night.
These are some of my theories about what's coming with UE6. Can't be sure about what's actually coming, and what's not. Either way, I'm really excited about the next unreal fest.
🧵 1/4 Before the State of Unreal, I'd like to make a few predictions on how it will work.
1. Verse paths will be the main point of the "metaverse," replacing the island codes. They will be used for both finding games, and adding assets from other developers into your own games.
UNREAL ENGINE 6 NEWS ON JUNE 17 👀
Epic Games will present State of Unreal at Unreal Fest, with their vision for UE6 + important announcements for Fortnite devs
State of Unreal has also revealed big Fortnite/UEFN collabs before, like Squid Game, Avatar, Star Wars, TMNT, etc..
3. The assets, importable with verse codes, will include both actual assets and functions. For example, we would be able to reference /gameexpf.dev/games/RightBehindYou, and use the cosmetics from it, with functions made public by the developer. Or game base. Or anything.
Finally, after almost half a year of working on it, Right Behind You 2.8.0 is out!
Play now: https://t.co/3WKGm9MqdH
Highlights:
✏️Custom Nameplates
🔊New Spatial Voice Chat
⚡Major Performance Optimizations & Loading Fixes
Full patchnotes: https://t.co/DYT0q6g5kh
So what was with the Zero Hour downtime music being really similar to Canny Valley's theme? We already have a Save The World location on the map, but I really hope that it doesn't end there.
I've just thought, if this screenshot is the new metaverse menu, what if the verse box in the upper left corner is actually a search field? Following this idea, the Unreal Verse app will be a browser-like experience, where we will be able to find games using their verse paths.
Amazing announcement! And, as I can see, there is Verse support as well. Not sure for what, but the possibilities are truly intriguing. Can't wait for #UE6!
It's really funny and frustrating when a person who knows nothing about a subject you're an expert in argues that they are correct, and no matter how much you try to explain that they aren't, they insist that you're just not well-versed in it.
The more I think about it, the more I believe that it must be a thing. Some might hate specific emotes, skins, or jam tracks. While Take the L gets blocked, it might not be as hurtful to players as those other cosmetics, the usage of which by enemies could drive them away from FN
I've recently been thinking about this list, and about how it could help people better customize their experiences. My proposal to Epic: make this list editable in the game settings, so that we can choose what cosmetics we don't want to see, including skins, emotes, etc.
I know it's hard to believe, but the device is still broken. Still waiting for @FNCreate to fix it. High hopes for it to be in the next update.
Meanwhile, the To Do stage has been assigned to it about 24 days ago.
I have no words. DBNO device's revive bug is still there, and it has been in the To Do stage for over 16 (!) days. It directly affects gameplay, causing players to lose the ability to interact with devices, until the whole session is restarted.
https://t.co/vhqG2ebYz3
@FNCreate
I just have a quick question here. Why in the world are such changes made to the production servers? Even though not planned, someone still had to change the value on the servers. And if it was not planned to go live, the changes must have been made on the testing servers.
Hey @BeastFNCreative we’re really sorry for the confusion here. This wasn’t a test, it was an error in the Creator Portal and has been reverted.
A compact download size means games remain available to as many players as possible – wherever they play. Later this year, we will add the ability to stream large assets (like textures and meshes) to UEFN, increasing what you can fit within the existing headroom.
Version 40.40 dropped today, but I won't be able to double-check if the DBNO device is fixed. It's probably not, but I'll have a <concrete> answer tomorrow.