assigning spreaded values to counters.

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.
  • Hi everyone,

    I know there are tons of examples, videos, instructions about how to spread values but I am stuck with spreading the values correctly and assigning them to counters or other values.

    I really appreciate if someone is kind enough to explain and/or make a quick mfa file for me.

    What I'm trying to do :

    I am building a card game where the user will pick 10 out of 78 cards from a deck ( it can be done automatically). then he/she will check what he/she chose and read the text (in my app -> current frame of Object x = Display paragraph of StringX) Preferably one by one.

    What I do

    I used spread values to assign IDs to duplicate object (which works fine) but I could not assign fixed numbers of each selected card ID to something. like I created 10 counters and wanted to assign ID values to them but all counters show the same value.

    I appreciate your supports

    Best Regards
    Alper

  • Fixed numbers are fixed in the true sense of the word: you can't change them at all. Think of them as read-only ID numbers, like serial numbers on a product. Since counters and strings don't have alterable values or flags, you can't really store any additional 'metadata' information in them the same way you can for an Active Object.

    Manuel's example works well, and manages to 'marry' each counter to its spouse card by putting the card's fixed number in the counter, but this will only work as long as you don't want to: (a) be able to find a matching counter/card in the future, and (b) change what's displayed in the counter at any time.

    A solution is to not try to store any information about the card in the counter, but instead to store information about the counter in the card (using one of the card's alterable values). In the attached example, we've successfully married each card/counter pair, which enables us to move each pair in sync.

  • Fixed numbers are fixed in the true sense of the word: you can't change them at all. Think of them as read-only ID numbers, like serial numbers on a product. Since counters and strings don't have alterable values or flags, you can't really store any additional 'metadata' information in them the same way you can for an Active Object.

    Manuel's example works well, and manages to 'marry' each counter to its spouse card by putting the card's fixed number in the counter, but this will only work as long as you don't want to: (a) be able to find a matching counter/card in the future, and (b) change what's displayed in the counter at any time.

    A solution is to not try to store any information about the card in the counter, but instead to store information about the counter in the card (using one of the card's alterable values). In the attached example, we've successfully married each card/counter pair, which enables us to move each pair in sync.

    I think I get the point. Will work on them to have a better understanding. Thank you for your support.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!