Godot @export - EVERYTHING you need to know!
In this video, I'll show you everything you need to know about the @export syntax in Godot!
Whether you're a seasoned Godot developer, or just getting started with GDScript, I'm sure this video will provide an addition to your knowledge base!
Watch until the end to find out ALL the ways you can use @export to optimize, decorate, and automate your Godot workflow!
Please be sure to make use of the timestamps if you're looking for specific info!
Here's a link to the expressions video: • How to use Expressions in Godot!
If you enjoyed the video, leave a like :)
Thanks for watching, and I hope you have a great week!
LINKS:
-------------------------------------
/ discord
/ queble_game_dev
/ queblegames
Book a 1 on 1 Godot tutoring session:
https://www.fiverr.com/s/o8Wq7AG
Official Documentation:
https://docs.godotengine.org/en/stabl...
-------------------------------------
TIMESTAMPS:
-------------------------------------
0:00 Intro (use timestamps if you'd like to skip the basics :)
0:38 What is @export?
1:29 Basic export types
2:09 Intermediate export types
3:25 Getting access to nodes with @export
5:07 Exporting Resource properties
5:57 Array and Dictionary @exports
7:49 Some interesting @export types
9:12 Exported Flags
10:46 Project Settings Layers @export
11:28 @exporting enums (drop down lists)
13:18 @export ranges
14:06 Advanced @export ranges
16:47 @export groups and categories
18:39 NEW! @export tool buttons!
20:59 @export custom
22:30 My favorite custom exports!
24:10 [ ELITE EXPORTS ]
27:15 Important notes!
28:34 Outro, thanks for watching! :)
-------------------------------------
Join this channel to get access to perks:
/ @queblegamedevelopment4143
This video was recorded in Godot v.4.4.dev6, but most of these methods should work in all versions of Godot 4.x (the only 2 that don't work in previous versions, are the export button, and the statically typed dictionaries).
NOTE: If you're using a version of Godot 3, most of the methods shown in this video will work, you'll simply need to remove the 'at' (@) symbol from the annotation.