I was wondering if there were any examples of an inventory system in the style of JRPGs where basically it can fit an indefinite number of items, scroll through them as necessary, and display quantity. I have already started working on this type of a system but since I'm new an example would be extremely helpful if one exists (i tried searching). Thanks.

I think it would be really useful to develop a text-based format in which you can type out event sheets instead of clicking through a ton of GUI menus. This is just an editor type feature that wouldn't add any functionality (scripting is separate) but would make editing event sheets much quicker for people who become more and more experienced with Construct.

That does work, thanks. I was wondering though, is it on the next tick that I can move the items? If so, is there a way to delay a function by tick amount? I can only find milliseconds, and I know it's unlikely but in the rare case of a hickup (perhaps a user would be runnign multiple apps in teh background) that might cause it to not work since the current tick might last a longer time than the millisecond delay I have.

Thanks. I'm at work now so i can't check, is there a simple Delay X ticks action I can just put in after the Create Objects by name action that would take care of it?

So I'm using Create OBject By name to create an object in the Items family. However, doing a For Each Items, Set XY does not affect these newly created objects. Any ideas on how to get around that?

Well this isn't just a hashtable issue, I think there are other ways that events may appear the same but do different things as well. Furthermore, I have different classes of information stored in the different hash tables. Is an array a better option for that sort of thing?

One of the problems I've been having in debugging, especially with bugs in my logic that show up as a result of interactions with a later-created event sheet, is the lack of information in the event list. For example, checking of a key in one hash table exists in another hash table shows only the hash table that has the key you are checking for, and not the hash table in which you are checking for a match (or do i have that reversed?) So what can happen is that statements that look identical can do different things. As the flow charts grow larger and more time passes since their creation this can lead to confusion.

However, I do appreciate the conciseness of the current view. So an optional view for debugging that includes more information would be great.