DataTableFillTools

Description

This plugin was born to quickly fill out data forms. It can add a tool called DataTableTools in the details panel of the blueprint. Just select the variable that this blueprint owns to save in the “Select Structure Value Name” dropdown box, then click the “Select Destination Data Table Name” dropdown box to select the data table you want to add it to, and click “Save Data To “Table” is saved to the data table;

If you are using it for the first time, you need to select the variable name to be saved in the “Select StructValue Name” drop-down box, click the “+” button to fill in the data table name, create a new data table, and then click “Save Data to DataTable” to save to data sheet. By default, the new table location is in the /Game/ConfigDataTable/ directory. If the C++ structure contained in it is not inherited from FTableRowBase, a “structure name_TableStruct” composed of your C++ structure name will be automatically created in the /Game/ConfigDataTable/AutoCreateStruct directory to fill the data table;

Of course, this plug-in also provides the function of quickly reading data from the data table, just select the variable owned by the blueprint in the “Select target data table name” drop-down box, and select the data to be selected in “Select”. You can read the “Target” table from the “DataTable Name” drop-down box, and then click the “Load Data From DataTable” button to read the data according to the ID field in your current structure and overwrite the current variable data blueprint;

This plugin can automatically convert C++ types that do not inherit FTableRowBase into blueprint structures (stored in the /Game/ConfigDataTable/AutoCreateStruct directory);

The type of Blueprint to open can be configured through the game settings (in DataTableFillTools/Target Type Settings). C++ type only needs to fill in the name of this type, and blueprint type needs to add _C after the blueprint name

Sorry, my native language is not English. This document was translated by Google. There may be ambiguities. If you have any questions, please file an issue on Github