All events are run every tick if the conditions are meant then the actions are done. For each is a condition and it has no other qualifiers so it will always run. If you add another condition to that then once Both of the conditions are meant it will .

Its hard to say with no cap but it you just have a for each with no other condition it will run every tick. you need to put a trigger once in there.

hash tables are ok but even then you nee to use an editor to edit the values. With an .ini file you can simply type it up in the correct format which IMO is much easier than using a special hash table editor Especially when using it for things like story I would rather use note pad and have to format it correctly than program my own editor.

uber lou because when doing large stories its easier to use an out side file and edit that than a bunch of internal text files.

http://files.getdropbox.com/u/646697/Lucid.zip

I whipped this a few days ago.

besides in the may update

[quote:18rmp2zh]The road to 1.0

The next major build release of Construct will be 1.0. We have now implemented all the features we want for 1.0, and until then, we will focus solely on bug fixes. There are around 150 open items on the tracker, and through the 0.99 minor releases (.2, .3, .4...) we will aim to get these as close to 0 as possible. Once we're satisfied with the bug fixes, we'll release version 1.0!

This is easy enough to do with events.

just use canvas start of layout set height/width to layout height/width.

Is it possible to put a hash table in a family as a container? So each instance of an object in that family have a hash table with them?

What would happen if you added an E into red but no counter part in the red family?

Im guessing that the event would just not run for E

I was looking into making a family with a hash table contained in it that way eveything could have its own hash table but you cant do the family containers....

I really like beyond oasis

If you use the diffrent layout methods it is a system action called Go to layout. If you make a level editor/saver/loader, the you would have to program in what to load when.

I don't understand what you mean about the name of the key but not the value. The values are shown when you click on the keys. To me it would be impractical to show both at the same time.

i didnt see an input box for value granted I looked at this pretty late at night so I was pretty sleepy and I could not see the value of the key when I clicked on it.

As for loading it would be something like

->on load

-->for each key

+Text.text=text.text&Hashtable.Currentkey&Newline

The .exe gives me an error when I try to run it. I looked at the cap though and it seems interesting enough. One thing though and I used to do it too. You dont need to divide event sheets up so much Most of that stuff can probably go in the main event sheet and you can cut down on the even sheets. there is not point in having event sheets with 2 or 3 events in them just use a group. just a suggestion.