[BUG] New HashMapObject functionality broken in ARMA 3 - MISSION EDITING & SCRIPTING Posted September 24, 2023 Noticed you also asked about having access to a parent class. I am working on a project that is based wholly around HashmapObjects and some AI related things. I haven't publicly announced it yet but, I have been working on it since dev announcement of HMOs. I make parent class methods a thing you can do now. I also have preprocessing of the definition arrays where you can even validate code, make methods and properties 'private' through obfuscation and introduce a formal interface class. Interested in your thoughts or if you find cool things that could be added. Basically, arrays are defined in an sqf file, read in at load via config (similar to functions) and preprocessed where they are finally turned into a global var (type definition) that can be used to create objects. And Cached similar to how CBA handled caching Interfaces are declared as only Method/Property declarations that are checked if they exist and return the type expected on a Type Parent methods generated so for example if you have TypeA and a TypeB that inherits from TypeA, you can reference the parent method (for example "Method") by calling the "TypeA.Method" on the TypeB object. There's also attributes you can add as a third element in the [key , pair] that the preprocessor will do extra stuff when compiling the type definition. Feel free to check out the source on github and the brief notes in the wiki. Def check out the wiki first.