(using the tutorial here as a jumping off point - https://docs.godotengine.org/en/3.1/tutorials/3d/fps_tutorial/ … . I might turn this into a progress thread as I go through the day)
-
-
Show this thread
-
-
-
step 3: Ok, I can hop about now. Now it's basically down to game design + graphics + audio (with some final scripting when the environment is done). [a big help for learning a game engine is finding a simple/interesting project to make that plays to its strengths...]pic.twitter.com/tcIw7FgJzQ
Show this thread -
step 4: ok was maybe *slightly* too optimistic on the coding front. If I had a godot-literate coding buddy this would be a lot faster, but I should can figure it out...online documentation is pretty ok! (I'm especially grateful for people asking stupid beginner questions online)pic.twitter.com/sWNCsryX0G
Show this thread -
New conversation -
-
-
What was your reasoning behind engine choice?
-
Godot seems pretty decent and I wanted to give it a proper try now that it has all the features I want (decent scripting, nice editor, html export). Though, using an engine one day for a jam is a pretty minor commitment; it barely needs any justification/reason at all.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.