When pushing level changes to a running session, the game that starts up keeps saying “Can’t built right now!” when you left click. Can’t shoot or use items like this.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Live Edit
Steps to Reproduce
Just run a map, once the game starts, end it. Start a new round or push a change from the editor or verse. The new game that runs will keep giving you the can’t build message on left click!
Expected Result
Being able to click my mouse and use stuff..
Observed Result
Left click blocked by “Can’t build right now” message
I too face similar issue, after push changes, i’m unable to aim, fire, jump or crouch. Only relaunched the session fixed this. Its happens 2 times in less than a hour.
This happened to me 3 times in 30 minutes. It is better to just right away exit a session and launch new one every time when I want to test something because pushing changes is now just a waste of time because it is not working.
And in my case it is not only shooting with left click that doesn’t work, but also aiming with right click, jumping with spacebar or crouching with a side button on a mouse. I can only run, change weapons with a mouse wheel or build with Q and then left click.
For me it was registering the Fire button as I was trying to build even when I was holding a weapon. Not to mention the constant failing of the UEFN to Fortnite connection. It has made development all but impossible to test. Not sure how this could have been overlooked in QA.
Edit: This has been happening like clockwork every single time I push changes. I have to end the session and return to the lobby in Fortnite. Then relaunch the session for it to work, which is slowing down development considerably. I hope there is a hotfix soon as this is quickly becoming very infuriating.
Worst part is that Input triggers still show up, yesterday I was trying to use one but couldn’t for 3h, tried to fix it in many ways but apparently you can’t even jump, sprint or crouch either. You can press buttons tho.
The worst part is that it is not only “Push Changes” that is broken (= useless) right now, but also “Push Verse Changes”. So what was already taking up a lot of time (pushing changes) now takes up even more (exiting and starting new session each time).
Its not just in game its on the pc as a whole tbh. When uefn crashes and fortnite is open you cannot left click the mouse on any icons ect something is seriously wrong.
I am having similar major issues as reported in this thread: Player can’t (randomly) shoot, jump, sprint, or turn. This happens after pushing changes. It is important to note that character movement remains broken even after the simulation is ended (e.g. Can’t move in the editor either). Pushing changes (Verse only or full) does not resolve the issue. The editor must be shut down and re-launched - usually a full reboot is needed because the Fortnite client hangs (likely connected to anti-cheat).
I can confirm this issue just started happening to me yesterday too. It started for me immediately after I adjusted the guard spawner Health/Shield/Invulnerable values in the outliner. Tried removing the guard spawner device but it’s still happening even after save and reload without the guard spawner. I also created a new blank project and the issue does not occur even after adding a guard spawner and a simple verse device but still persists in the original project with the issue, so I can’t confirm the guard spawner is the issue but at least this might be a place to start?
It’s not, but thanks for the input. The game’s build menu inputs get stuck to the mouse inputs on the second launch. If you stop the match after the first push and close the build phone and just left or right click, it’ll instantly try to place a build floor down. The build menu is permanently open after the first run of an island.
This has been happening for our projects as well. Every single time we Push Verse Changes, the game bugs out and we have to completely close the Fortnite client and relaunch. It makes testing anything extremely time consuming.
We have 2 separate projects this occurs in. When we created a new project to see how widespread the issue was, it doesn’t happen there, so it must be something specific to the project.