I'm stupid.

[NicoM1]

why do we need that? isnt flxgroup typed in dev? eg. FlxGroup

[NicoM1]

sorry html got cut out FlxGroup<Entity>

[NicoM1]

thats unnecessary, you dont have to import if they are contained in the same .hx file

[sruloart]

Just good practice, I think. FD isn't the most stable software in the entire world, I've encountered weird problems with the way FD imports classes before. Let's just keep it in mind if something really weird happens.

[NicoM1]

ok will do:)

[nathanbl]

Why this project is dead? It's so cool! Wake up, please... @NicoM1 & @sruloart 👍

When I try to remove "import flixel.group.FlxGroup;" and "import flixel.group.FlxGroup.FlxTypedGroup;" in Player script for fun 😄

package ;
import flixel.FlxG;
// import flixel.group.FlxGroup;
// import flixel.group.FlxGroup.FlxTypedGroup;
import flixel.util.FlxColor; // <------------------------ Oh no!!!
import ice.entity.Entity;
import ice.entity.EntityManager;
import Math;
import flixel.FlxObject;

class Player
{
    //#
    var owner:Entity;
    //#

Oh no, "flixel.util.FlxColor" is not found :face_with_head_bandage:

haxelib run lime test neko -Ddebug

ScriptHandler.hx:110: path: flixel.FlxSprite
ScriptHandler.hx:110: path: ice.entity.Entity
ScriptHandler.hx:110: path: ice.entity.EntityManager
ScriptHandler.hx:110: path: flixel.math.FlxRandom
ScriptHandler.hx:110: path: flixel.FlxG
ScriptHandler.hx:110: path: ice.group.EntityGroup
ScriptHandler.hx:110: path: Std
ScriptHandler.hx:110: path: flixel.util.FlxColor
expose attempt failed: flixel.util.FlxColor
Type.resolveClass("flixel.util.FlxColor");

Libs version

flixel-demos: [2.3.0]
flixel-templates: [2.1.0]
flixel-tools: [1.2.1]
flixel-ui: [2.2.0]
flixel: [4.2.0]
hscript: [2.0.7]
hxcpp: [3.3.49]
iceentity: git [dev:/devel/haxelib/iceentity/git]
lime-samples: [3.4.0]
lime: [2.9.1] 3.4.1 3.5.1 3.5.0
openfl: 4.4.1 4.5.1 [3.6.1] 4.5.0

[NicoM1]

@nathanbl thank you for the kind words, but honestly this is a very out of date project, and one that was clunky to work with at best. I do not recommend you attempt to build anything in it, and if you really wish for a similar workflow, it would not be too large an amount of work to reimplement most of this in cleaner ways.

Thanks for peaking around though, and I'll answer any questions I can :)

Nico