Just open the trigger editor, make a new action and look at the category "Banks". There you got them all. And for every "Store XXX" action there's a respective "Load XXX" action (which is considered a function and thus not shown under actions).
I suggest data tables because you can save everything in them, not only the limited selection of banks.
You can pretty easily create arrays with it as you can specify the name reference as a string.
I actually don't know how to declare a data table, if anyone could please share~ :D
I'm only using banks cause thats the only data table I know how to declare and access.
Okay, I'm going to try my hands at the data table. I'm drafting a system to handle and organize the data into manageable parts (by the system) and easily controllable (by the user).
Edit:
Is there any way I make it so I can make a function return a struct or something so that the user has a handle which links to array data?
I was going to use structs that would hold the name, type, and size of an array so the user can easily call and store structs.
Okay, I'm going to try my hands at the data table. I'm drafting a system to handle and organize the data into manageable parts (by the system) and easily controllable (by the user).
Edit:
Is there any way I make it so I can make a function return a struct or something so that the user has a handle which links to array data?
I was going to use structs that would hold the name, type, and size of an array so the user can easily call and store structs.
I've started working on the API for handling dynamic arrays. Full support for all data table variables will be about 200 functions (45 different variables and 4 different boilerplate functions need to handle specific types so a minimum of 180 functions just to handle all the variables with around 10-20 core functions)
Of course you can delete functions that you won't use and only take a few functions that you need to dramatically reduce size.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
@SouLCarveRR: Go
Just open the trigger editor, make a new action and look at the category "Banks". There you got them all. And for every "Store XXX" action there's a respective "Load XXX" action (which is considered a function and thus not shown under actions).
@s3rius: Go
Yeah what he said.
BankValueSetFromFixed(gv_Session, "RealArray", IntToString(lv_i), 524277.01318359375);
lv_bankReal = BankValueGetAsFixed(gv_Session, "RealArray", IntToString(lv_i));
There are versions for bools, ints, points, strings, text, units, and reals.
@s3rius: Go
Functions... Actions ... Same thing in my book =)
an action is a function but a function is not an action :P
It seems like banks are the logical choice. I figure I can make a bank for each variable type and divide each bank into sections for arrays.
@TheSecretArts: Go
Just remember not to save the bank!
I played an RPG recently that junked up my bank folder with like 30 bank files and didn't even load the next time I tried to play it.
Separate your temp storage banks and DON'T SAVE THEM! :)
@TheSecretArts: Go
I suggest data tables because you can save everything in them, not only the limited selection of banks.
You can pretty easily create arrays with it as you can specify the name reference as a string.
@s3rius: Go
data tables seem to work in a very similar way to banks at first glance. Is there any big differences between them?
@TheSecretArts: Go
I actually don't know how to declare a data table, if anyone could please share~ :D I'm only using banks cause thats the only data table I know how to declare and access.
@TheSecretArts: Go
Data Tables have functions to save any variable type. Banks can only store a few.
@Hokibukisa: Go
You don't need to declare a data table, you can just use it.
@s3rius: Go
How did I miss that... Welp, learn something new everyday I suppose. Thanks! :D
Okay, I'm going to try my hands at the data table. I'm drafting a system to handle and organize the data into manageable parts (by the system) and easily controllable (by the user).
Edit:
Is there any way I make it so I can make a function return a struct or something so that the user has a handle which links to array data?
I was going to use structs that would hold the name, type, and size of an array so the user can easily call and store structs.
You can't return a struct or an array directly.
I've started working on the API for handling dynamic arrays. Full support for all data table variables will be about 200 functions (45 different variables and 4 different boilerplate functions need to handle specific types so a minimum of 180 functions just to handle all the variables with around 10-20 core functions) Of course you can delete functions that you won't use and only take a few functions that you need to dramatically reduce size.