I think.
I have a dinky little project in which the standard pill shaped FPS Controller can move around shoot cube primitives. Yesterday, any compiled version of the project would not shoot, even though playing it within the editor still worked just fine. I couldn’t figure it out and knew of no recourse to investigate (I hate troubleshooting with no leads, would rather quit and play someone else’s game).
Just now I figured I’d open the island demo that comes with Unity and make that one shoot. I didn’t use anything from the original project, and I actually copied the script verbatim from the Unity Script Reference. It all worked just fine, both in the editor and in the standalone build.
Switched back to my project. Noticed that the build and data directory from the first time I built this project appeared in the Project pane. It’s actually not the first time I’ve noticed this, but it stuck out because I’ve deleted those files and run the build with new names earlier today in the hope that somehow those files were mucking with my new changes. So, I deleted them from the Project pane and rebuilt. Shit works. I removed those assets from the Project pane before doing one more build test, so I can’t know for absolute certain if that did it. However, if that wasn’t it then the entire period during which it wasn’t working was completely a fluke.
So, the moral of the story is, the output of the build process should not show up in your Project pane.
The remaining question is, how the hell did it get there in the first place? And why did it matter?
