[Solved] AngelScript: A problem with an array

Hello guys, I'm having a bit of a headache with an array. It's more an AngelScript problem than a KAG one, I think.

First, I have defined this small class in one file:

Code:

namespace UndeadInvasion {

  class EntitySpawn {

    string mEntityName;
    u8 mSpawnChance;
 
    EntitySpawn() {
 
      mEntityName = "Zombie";
      mSpawnChance = 100;
   
    }
 
    EntitySpawn(string entityName, u8 spawnChance) {
 
      mEntityName = entityName;
      mSpawnChance = spawnChance;
   
    }
 
  }

}

Second, I have a file with some variables:

Code:

#include "EntitySpawn.as";


namespace UndeadInvasionVariables {

  //Define a minimum number of -1 (disabled) for players on each team for the game to start
  const s8 PLAYER_COUNT_START_MINIMUM = -1;

  //More stuff here...

  //Define an array of Undead entities to spawn
  const UndeadInvasion::EntitySpawn[] UNDEAD_ENTITY_SPAWN_MIX = {
    UndeadInvasion::EntitySpawn("Zombie", 60),          //Zombie 60% chance
    UndeadInvasion::EntitySpawn("Skeleton", 35),        //Skeleton 35% chance
    UndeadInvasion::EntitySpawn("Devilish Zombie", 5)   //Devilish Zombie 5% chance
  };

  //print("Length:"+ UNDEAD_ENTITY_SPAWN_MIX.length); //<-- Causes error: "Expected Identifier"

}

And lastly, I have this in my RulesCore:

Code:

#include "UndeadInvasionVariables.as";
#include "EntitySpawn.as";

#include "RulesCore.as";

shared class UndeadInvasionRulesCore : RulesCore {

//More stuff here

void spawnUndead(Vec2f position) {

    //Check if there are any undead available for spawning
    if(mUndeadAvailable > 0) {
 
      //Get a random value between 0 and 100
      u8 randomChance = XORRandom(100);

      //print("Length:"+ UndeadInvasionVariables::UNDEAD_ENTITY_SPAWN_MIX.length); //<-- Causes error: Likely missing ';'

    }

}

}

I'm stumped. All my other const variables work just fine. I also tried declaring the array using the Array<UndeadInvasion::EntitySpawn> approach. No dice. Anyone got a clue about what's going on?

Solution: The rules core and respawn system was declared using the shared keyword, and could thus not access the array. Removing that keyword fixed the problem.

 

Isn't length() a method?

 

For the Template type Array, it is, but for these native-style arrays it's not. At least it's used like this many places in vanilla code, and I've used it too in other situations without problems. But anyway, I still get an error.

 

This happens because you can't call a function out like this. You have to call it from a function.

About the likely missing ";", I don't really understand how could it be problematic. Have you tried using the size() method instead of length?

 

The print line directly in the variables namespace, was just for testing. I did the same call in my rules core function.

I'm actually pretty sure the array types are not compatible, because I think I tried several times to replace .length with .length() other places, and I got errors when I did that.
But really, whatever I type, I get this error. Even doing this:

Code:

if( UndeadInvasionVariables::UNDEAD_ENTITY_SPAWN_MIX is null) {
        print("SPAWN MIX IS NULL");
      }

If I comment out any reference to UndeadInvasionVariables::UNDEAD_ENTITY_SPAWN_MIX, there's no error, and the game runs fine.

 

Yeah, I realized that might be a cause, but if you had looked closer, I have attempted the same call elsewhere.

 

Thank you! Removing the shared keyword on the rules core and re-spawn system solved it. I guess I should've thought about that. Not sure why the base classes are declared as shared in the first place, I just assumed it was a good idea to keep the keyword. Tagging topic as solved. Peace.

P.S. length() also worked. How odd! Thanks for the tip about Objects.txt. I didn't know about that one!

 

RulesCore might be a mess (you've probably been working much more with it than I), but it works for me. It was a little confusing at first though. I think I've found a set-up I'm fairly happy with considering what limitations there are, and things are starting to take shape. RulesCore and SpawnSystem hides some of the (more or less) gritty details, so I don't have to worry about it anymore, now that I have an idea how it is designed. I think the bigger issue is that it follows a pattern that isn't used elsewhere. There are too many patterns around, and now I'm introducing even more (but in my view better ones) :o)