Families don't have subfolders?

0 favourites
From the Asset Store
A collection of various zombie characters sprites for creating a 2D platformer or sidescroller game
  • Starting to make use of more families now, noticed that there aren't subfolders for families whereas they exist for every other category. Is this an oversight or a bug?

  • In what way are you trying to further categorize families?

  • Yeah that would be nice to have.

  • In what way are you trying to further categorize families?

    Hopefully this picture makes it crystal clear:

  • I mean why do you feel you need to categorize families?

  • "why you feel you need to"?! Please don't try to dismiss this topic as my mental problem. You're not a member of product team, it doesn't impact your work. There's nothing for you to gain by trying to shut down an honest question for the developers.

  • Nobody said anything about mental problems, I'm asking why you want to have sub folders for family objects. If for example I have some families "Enemies" "Characters" "Weapons", I can't think of a sub folder I would need to create to categorize it further.

  • I would like subfolders for families too.

  • There's an existing feature suggestion for this.

  • Do you just want a folder where you can store your families with no impact to how they behave?

    or are you asking for being able to nest families and having them behave like inheritance?

    like sub families?

  • Nobody said anything about mental problems, I'm asking why you want to have sub folders for family objects. If for example I have some families "Enemies" "Characters" "Weapons", I can't think of a sub folder I would need to create to categorize it further.

    Example:

    Folder:Tools
    Family: Guns
    -Lasers
    -- ********
    -- ********
    -Shotguns
    -- ********
    -- ********
    -Rifles
    -- ********
    -- ********
    
    Family: Melee Weapons
    -Swords
    -- ********
    -- ********
    -Daggers
    -- ********
    -- ********
    
  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • but in your example in your top level weapon folder did you want to give them basic weapon properties (instance variable/behavior)

    then as you drill down be more specific for each weapon family?

    Weapon --> (firerate, bulletSprite, range)

    Shotgun (numberOfBulletsPerShot)

    Rilfe (fireMode (burst or auto) )

    In this case Shot Gun and Rifle still have firerate, bulletSprite, and range

    This impact how family behave as opposed to just grouping them in a folder? the above is more like inheritance, even though it can also be accomplished using family composition?

    But they both behave differently

  • Sometimes you just want folders for things like

    George

    folder for families George is handling

    Sue

    folder for families sue is handling.

    Or even

    needs work by friday folder

    for families that need work by friday.

    You get a lot of families pretty quickly as you code.

  • > Nobody said anything about mental problems, I'm asking why you want to have sub folders for family objects. If for example I have some families "Enemies" "Characters" "Weapons", I can't think of a sub folder I would need to create to categorize it further.

    Example:

    > 
    Folder:Tools
    Family: Guns
    -Lasers
    -- ********
    -- ********
    -Shotguns
    -- ********
    -- ********
    -Rifles
    -- ********
    -- ********
    
    Family: Melee Weapons
    -Swords
    -- ********
    -- ********
    -Daggers
    -- ********
    -- ********
    

    In my game I would just have a family called Guns only. If I want to define different types of Guns I use family instance variables. However, if someone really felt the need to have a family called Guns as well as families called Lasers, Shotguns and Rifles, I'm still not getting why they need to go in sub folders. Seems redundant.

  • I think the need for sub folder is clearly defined in the feature request that was mentioned. if you have alot of different family, it's a quality of life improvement, to not have all the family fill up your plugin selection screen, it should help in finding the families as well if you have like 20+ families. and i agree with just having folder to help organize all your families, having nested families/ family inheritance on the other hand, i don't really see a point in that, because you can use family composition to achieve the same thing in a clearer way.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)