A script that is executed when exporting the project. [EditorExportPlugin]s are automatically invoked whenever the user exports the project. Their most common use is to determine what files are being included in the exported project. For each plugin, [method _export_begin] is called at the beginning of the export process and then [method _export_file] is called for each exported file. To use [EditorExportPlugin], register it using the [method EditorPlugin.add_export_plugin] method first. Return true if this plugin will customize resources based on the platform and features used. Return true if this plugin will customize scenes based on the platform and features used. Customize a resource. If changes are made to it, return the same or a new resource. Otherwise, return [code]null[/code]. The [i]path[/i] argument is only used when customizing an actual file, otherwise this means that this resource is part of another one and it will be empty. Customize a scene. If changes are made to it, return the same or a new scene. Otherwise, return [code]null[/code]. If a new scene is returned, it is up to you to dispose of the old one. This is called when the customization process for resources ends. This is called when the customization process for scenes ends. Virtual method to be overridden by the user. It is called when the export starts and provides all information about the export. [param features] is the list of features for the export, [param is_debug] is [code]true[/code] for debug builds, [param path] is the target path for the exported project. [param flags] is only used when running a runnable profile, e.g. when using native run on Android. Virtual method to be overridden by the user. Called when the export is finished. Virtual method to be overridden by the user. Called for each exported file, providing arguments that can be used to identify the file. [param path] is the path of the file, [param type] is the [Resource] represented by the file (e.g. [PackedScene]) and [param features] is the list of features for the export. Calling [method skip] inside this callback will make the file not included in the export. Return a hash based on the configuration passed (for both scenes and resources). This helps keep separate caches for separate export configurations. Return the name identifier of this plugin (for future identification by the exporter). Adds a custom file to be exported. [param path] is the virtual path that can be used to load the file, [param file] is the binary data of the file. If [param remap] is [code]true[/code], file will not be exported, but instead remapped to the given [param path]. Adds an iOS bundle file from the given [param path] to the exported project. Adds a C++ code to the iOS export. The final code is created from the code appended by each active export plugin. Adds a dynamic library (*.dylib, *.framework) to Linking Phase in iOS's Xcode project and embeds it into resulting binary. [b]Note:[/b] For static libraries (*.a) works in same way as [code]add_ios_framework[/code]. This method should not be used for System libraries as they are already present on the device. Adds a static library (*.a) or dynamic library (*.dylib, *.framework) to Linking Phase in iOS's Xcode project. Adds linker flags for the iOS export. Adds content for iOS Property List files. Adds a static lib from the given [param path] to the iOS project. Adds file or directory matching [param path] to [code]PlugIns[/code] directory of macOS app bundle. [b]Note:[/b] This is useful only for macOS exports. Adds a shared object or a directory containing only shared objects with the given [param tags] and destination [param path]. [b]Note:[/b] In case of macOS exports, those shared objects will be added to [code]Frameworks[/code] directory of app bundle. In case of a directory code-sign will error if you place non code object in directory. To be called inside [method _export_file]. Skips the current file, so it's not included in the export.