it's meant to appear on/off screen via tween

so of course nothing moves

🤔

it was working before putting it into a group

i'll try 0

no hold on

stop

FlxTween.tween(menu,  { x:menu.x, y:FlxG.height - menu.height}, 1, {type:ONESHOT, ease: FlxEase.backOut});

FlxTween.tween(menu,  { x:menu.x, y:0}, 1, {type:ONESHOT, ease: FlxEase.cubeOut});

in both of these, you are tweening y to

0

. already. If menu is open, you tween to

0

if menu is closed you tween to

0

thats why nothing moves

its already at 0 both times

FlxG.height - menu.height

is

0

.

because menuBox.height is FlxG.height.

maybe you want the closed menu to be tweened to

FlxG.height

for offscreen below, or

-FlxG.height

for offscreen above

If possible, why not make a new class that extends

FlxSpriteGroup

instead of making a

FlxSpriteGroup

and adding to it later? IIRC,

FlxSpriteGroup

does something special with things that are added in the constructor (

new

) so that they work properly

@hallowed-holiday-15370 nothing special like you're saying is happening to my knowledge. But I could be wrong. Here's the constructor https://github.com/HaxeFlixel/flixel/blob/d03e2d8b77b8c72bdc773fba2b1886dececf0d69/flixel/group/FlxSpriteGroup.hx#L72. theres just hooks that update children when the parent x/y are changed: https://github.com/HaxeFlixel/flixel/blob/d03e2d8b77b8c72bdc773fba2b1886dececf0d69/flixel/group/FlxSpriteGroup.hx#L701

@nutritious-gold-52850 got it working thanks for the help guys

yep this was it. apparently massive oversight on my end lol

thanks

Yep, no worries. That's why you post the code 😛 sometimes you just need fresh eyes

Glad you got it working!

I could be remembering an older version - it has been awhile since I dug deep in the code for it

maybe your thinking of a specific trick I use when adding sprites to a spritegroup in new, I've said it here, before, I'm sure

hx
public function new (x = 50.0, y = 50.0)
{
  super(0, 0);

  add(a = new FlxSprite(0, 0, "assets/a.png"));
  add(b = new FlxSprite(a.x + a.width, a.y, "assets/b.png"));

  this.x = x;
  this.y = y;
}

because with the following, (assuming the groups is placed in it's default position) b.y will end up at 100 (or

a.y * 2

), where above it will be at 50 or

a.y

hx
public function new (x = 50.0, y = 50.0)
{
  super(x, y);

  add(a = new FlxSprite(0, 0, "assets/a.png"));
  add(b = new FlxSprite(a.x + a.width, a.y, "assets/b.png"));
}

I want to give a player an offset of points as a path to move along. A single path will have 4 directions (& inverted) or 8 directions, so it is necessary to rotate 1 array in 8 variations (including reversed) or 16 variations. So

points

copies a path array, then Math cos & sign rotate each point in

points

with degree

degreeVariation

, then

+degreeOffset

retains the path shape (otherwise the rotated shape would be a straight line) and

mag

retains each points length. In my previous rotation attempt with example1 a single point was completely out of shape, then the other attempt with example2 an array of points retain their shape. (1) https://discord.com/channels/162395145352904705/165234904815239168/1075384579482984499 (2) https://discord.com/channels/162395145352904705/165234904815239168/1075536637112619059

i just don't get why you're recreating existing functionality and doing steps that negate each other

hx
package states;

import flixel.FlxSprite;
import flixel.group.FlxGroup;
import flixel.FlxCamera;

class OfffsetRotateTestState extends flixel.FlxState
{
    inline static var ROT_SPEED = 200;
    inline static var ROT_STAGGER = -30;
    
    var sprites = new FlxTypedGroup<FlxSprite>();
    
    override function create():Void
    {
        for (i in 0...4)
        {
            final sprite = new FlxSprite("assets/images/haxe.png");
            sprite.screenCenter();
            sprite.offset.setPolarDegrees(sprite.width * 1.25 * i, ROT_STAGGER * i);
            
            sprites.add(sprite);
        }
        add(sprites);
    }
    
    override function update(elapsed:Float):Void
    {
        for (sprite in sprites)
        {
            sprite.offset.degrees += ROT_SPEED * elapsed;
        }
    }
}

because this seems to do all the things you're trying to do but much more directly

or is that not the case?

I'll look into what my code is doing and get back later.

What happened was I didn't understand or find a rotation formula so I made some bad ones, then I learnt how it works with FlxPoint.rotate() . 1 . My Initial Issue -> made bad rotation formula -> Result : array lost shape cos = cos(rotation) sin = sin (rotation) sprite = ( cos * ax, sin * ay ) 2 . My Solution -> include point magnitude & point angle -> Result : 180 degrees off & inverted point magnitude = Magnitude(ax, ay) point angle = PointToAngle(ax, ay) cos = cos(rotation + point angle) sin = sin (rotation + point angle) sprite = ( cos * point magnitude, sin * point magnitude ) 3 . My Solution after help -> use FlxPoint.rotate() -> Result : worked properly offset = FlxPoint.rotate(rotation) FlxPoint : (cos * x - sin * y, sin * x + cos * y) sprite = ( offset x, offset y )

In example, the icon shows the desired path. Result 1 shows off-shape path, 2 shows inverted path, 3 shows correct path.