am new here,
how do I make an visual editor to make it similiar to rpg maker GUI
or at least a rpg game on here?

An example using hp, where equipped_list and effects_list are keys on the object that are just lists of other sections that currently affect the character:

[StatSolver]
Equations  = StatEquations
Defaults   = StatDefaults
Update     = change

[StatDefaults]
base_hp      = 10
base_mult_hp = 1
damage_hp    = 0

[StatEquations]
max_hp                = Clamp(0, max_hp_cap, (base_hp * base_mult_hp) + (equipment_mod_hp * equipment_mod_mult_hp))
total_hp              = max_hp + (temporary_mod_hp * temporary_mod_mult_hp) - damage_hp
max_hp_cap            = infinity
equipment_mod_hp      = Sum(equipped_list, equip_modifier_hp, default: 0)
equipment_mod_mult_hp = Sum(equipped_list, equip_modifier_mult_hp, default: 0)
temporary_mod_hp      = Sum(effects_list, temp_modifier_hp, default: 0)
temporary_mod_mult_hp = Sum(effects_list, temp_modifier_mult_hp, default: 0)

This would, given any orx object, generate the attributes base_hp, base_mult_hp, damage_hp, total_hp, max_hp_cap, equipment_mod_hp, equipment_mod_mult_hp, temporary_mod_hp, and temporary_mod_mult_hp on that object.

I've currently got a parser and topological sort working, I've started on setting up a VM for it, but I noticed that the orxConfig API isn't thread safe, which I would need if I wanted to solve for multiple characters in parallel if the equations are referencing lists of config sections, but not if they're just referencing other variables on the object itself, since that can be saved to a hashtable beforehand. The only solutions I can think of so far are either manually doing mutex locks when reading the config (not ideal), duplicating the code from the config module to read values from another section without modifying the config section stack (also not ideal), or just dealing with solving for one object at a time (which limits how much it can be used). Just wondering if there's any tips on this.

[Scene]
TrackList          = enemyMakerTrack

[enemyMakerTrack]
1                     = Object.Create spiderObject
Loop                = True

[spiderObject]
Graphic            = spiderGraphic
Scale                = 0.2
Position            = (800, 275, 0)
AnimationSet    = spiderAnimationSet
Body                 = spiderBody

[spiderGraphic]
Texture         = spider_full.png
TextureOrigin   = (0, 0, 0)  
TextureSize     = (0, 0, 0)
Pivot           = center

[spiderAnimationSet]
Texture         = spider_full.png
FrameSize       = (1024, 1024, 0)
Pivot           = center
spiderWalkRight  = 5
spiderWalkLeft   = 5

StartAnim       = spiderWalkLeft

spiderWalkLeft-> = spiderWalkLeft # .spiderWalkRight
spiderWalkRight-> = spiderWalkRight # .spiderWalkLeft

[spiderWalkLeft]
KeyDuration     = 0.1
TextureOrigin   = (0, 1024, 0)

[spiderWalkRight]
KeyDuration     = 0.1
TextureOrigin   = (0, 0, 0)

[spiderBody]
Dynamic         = true
PartList        = spiderBodyPart
LinearDamping   = 5

[spiderBodyPart]
Type            = box
Solid           = true
SelfFlags       = enemy
CheckMask       = platforms # bullet
BottomRight     = (225, 100, 0)
TopLeft         = (-200, -175, 0)

and here is some of my c++ code:

#include "orx.h"

orxOBJECT* spider;

void spiderMovement()
{
    orxVECTOR spiderLeftSpeed = { -3, 0, 0 };
    orxVECTOR spiderRightSpeed = { 3, 0, 0 };

    if (dead == 0)
    {
        orxObject_ApplyImpulse(spider, &spiderLeftSpeed, orxNULL);
        orxObject_SetTargetAnim(spider, "spiderWalkLeft");
    }
}

orxSTATUS orxFASTCALL Init()
{
     orxObject_CreateFromConfig("Scene");

     spider = orxObject_CreateFromConfig("spiderObject");
}

orxSTATUS orxFASTCALL Run()
{
      spiderMovement();
}

This is not the whole code it is just things that are regarding to the problem.
I can post the whole code if you like.

Most of the projectiles spawned by the ships' spawners are to be completely detached from their respective spawners upon spawning, but one in particular is meant to be parented by its spawner, and move along with it (this behavior might seem a little odd, but I'm wishing to implement it this way so as to leverage the base Ship class' behaviors for all of its descendents). Unfortunately, when parenting the spawned projectile to its spawner, the projectile doesn't move along with it at a 1:1 ratio, but rather follows it incredibly slowly, in effect not being attached to its parent in any meaningful way at all. I've found that the forum threads, Creating a Laser and UseSelfAsParent Makes Spawner Move Twice as Fast seem to address the same problem, and removing the projectile's Body attribute does "resolve" the issue, but the fact remains that this projectile must have a Body in order to collide with its necessary colliders. I attempted to circumvent the issue by following the Passing Items from one Object to Another tutorial, and explicitly setting the parent of spawned objects, but this results in the same behavior.

Is there some trick to parenting objects with Body attributes that I'm unaware of, or do I really need to dispense with my universal spawner behavior and incorporate these projectiles as body parts of their associated ships? Thanks in advance.

• UseParentSpace for Relative Object Positioning and Scaling
• UseParentSpace for Spawners using Relative Position and Scale