Attributes & GS

ingenious.applicationsingenious.applications Member Posts: 102
in Working with GS (Mac)
How many attributes can a GameSalad app handle before slowing/crashing?

Comments

  • KevinCrossKevinCross London, UKMember Posts: 1,894
    I don't see why there would be a limit but I've had about 40-50 before I had a clean up and it was working fine.
  • tatiangtatiang Member, Sous Chef, PRO, Senior Sous-Chef Posts: 11,949
    In the days before tables, we would easily have a few hundred attributes.
  • ingenious.applicationsingenious.applications Member Posts: 102
    In the days before tables, we would easily have a few hundred attributes.
    Excellent to hear. I've been stuck for a very long time with my project as I can't get tables to work for everything that I need...such as being used for rule conditions, etc. So, as tedious as it'll be, attributes are at least less mind-numbingly difficult.
  • tatiangtatiang Member, Sous Chef, PRO, Senior Sous-Chef Posts: 11,949
    edited November 2013
    I know there are some limitations of using tables with regard to rule conditions, but keep in mind that there are sometimes workarounds that are still much easier than adding dozens of individual attributes. Two things come to mind:

    1. If you have a mathematical equation and want to have a tableCellValue on the left side, just move it to the right. For example, instead of tableCellValue > game.Score+100 you would do game.Score < tableCellValue-100.

    2. If you need to check for the value of a constant (e.g. zero, blank text, or any number), create a game attribute for that constant. I use this for When attribute game.ZERO = tableCellValue --> [behaviors].
  • ingenious.applicationsingenious.applications Member Posts: 102
    I know there are some limitations of using tables with regard to rule conditions, but keep in mind that there are sometimes workarounds that are still much easier than adding dozens of individual attributes. Two things come to mind:

    1. If you have a mathematical equation and want to have a tableCellValue on the left side, just move it to the right. For example, instead of tableCellValue > game.Score+100 you would do game.Score < tableCellValue-100.

    2. If you need to check for the value of a constant (e.g. zero, blank text, or any number), create a game attribute for that constant. I use this for When attribute game.ZERO = tableCellValue --> [behaviors].
    I'll give it a shot soon and see how that works out for me. The vast majority of the rules would be working off of a cell being a certain text value.
  • jonmulcahyjonmulcahy Member, Sous Chef Posts: 10,408
    tables for rule conditions should be out in .11.0, it's in the nightlies now and works awesome.
  • tatiangtatiang Member, Sous Chef, PRO, Senior Sous-Chef Posts: 11,949
    tables for rule conditions should be out in .11.0, it's in the nightlies now and works awesome.
    Forgot about that. A great improvement.
Sign In or Register to comment.

© Vanilla Keystone Theme 2025