Vec3 Sample Pack code#

For our Monster, it is used to populate a vector of tables via the weapons field within our Monster. It is used twice: once within the Monster table and once within the Equipment union.

The Weapon table is a sub-table used within our FlatBuffer.

Vec3 Sample Pack code#

Be careful when using deprecated, however, as it may break legacy code that used this accessor. Since you cannot delete fields from a table (to support backwards compatability), you can set fields as deprecated, which will prevent the generation of accessors for this field in the generated code. Another thing to note is the line friendly:bool = false (deprecated). If unspecified, scalar fields (like int, uint, or float) will be given a default of 0 while strings and tables will be given a default of null. We specify some default values for fields, such as mana:short = 150. This will be used as the template to store our orc monster. The Monster table is the main object in our FlatBuffer. We use a struct here, over a table, because structs are ideal for data structures that will not change, since they use less memory and have faster lookup. If we had created multiple tables that we would want the union to be able to reference, we could add more elements to the union Equipment.Īfter the union comes a struct Vec3, which represents a floating point vector with 3 dimensions. The union in this example is not very useful, as it only contains the one table (named Weapon). Since the behavior of an enum is to increment if unspecified, Green will receive the implicit value of 1.įollowing the enum is a union. We specify Red = 0 and Blue = 2, but we do not specify an explicit value for Green. We have three values in this enum: Red, Green, and Blue. In this example, we have an enum of type byte, named Color. In our example, we have the Sample namespace inside of the MyGame namespace. This determines the corresponding package/namespace for the generated code. The schema starts with a namespace declaration. Let's examine each part of this schema to determine what it does. As you can see, the syntax for the schema Interface Definition Language (IDL) is similar to those of the C family of languages, and other IDL languages.