Looking for something other to use instead of a DT, any suggestions? For batch referral, e.g. many Levels having the same texture.
What is it about native data tables that doesn’t work for your use case?
Can’t get it to work with the Construction Script.
Data tables are essentially text/.csv files (excel-files, lol). They are pretty compact, albeit somewhat fugly to work with.
You could always make a structure/blueprint with all the right fields to hold what you want but to populate it you need to type stuff in, dropdowns, or use a…data-table…
Honestly speaking, for anything I need, I cannot see why a DT wouldn’t suffice. Plus it’s plaintext.
What doesn’t the current DT do for you?
Runtime DataTable does work at Construction! Though the workflow will be a little different, it is intended to work with dynamic tables at runtime, including at construction.
here is a tutorial where they use DTs as part of UMG construction, does this help, as a practical example?
what is not working in the contruction-script? Can you at least get the name of the DT, print it; at least touch it at all vs loading data?
Is there any benefit of using Actor Components BP instead of ordinary Actor BP?
Components are smaller/modular parts; like a stat-component that is just a collection of variables that track health, stamina, etc.
Other components, like the movement, component do more functional things like help your character navigate, access the movement-queue, etc.
It depends on what you are going for. If it’s a thing that will be shared across multiple actors, then likely a component is the best way since it’s not something in and of itself, like an actor-proper, but something that enhances or adds-functionality to something it’s attached-to.