This BLOWS my mind, Problem with conditions......

Hi there,

I'm building a wardrobe,(dunno if that is spelled correct) where you can buy and the equiped diffrent items.

I have added the mmf file if someone wants to take alook and try to help me. Attachment 10088

Got the whole layout fixed and the logical conditions fixed too, what blows my mind is that the 3 first items i programed,
(Category Armor, Ice armor tier 1, 2, and 3) works as intended but basicaly using the exact same code for Fire armors
one of those conditions (the equiped item condition) wont work at all, as far as i can tell it is exactly structured as the conditions for ice armors
which works just fine. I have old comments in the code roughly explaining what some things does.

I wrote in capital letters where the problem is. (Category Armor, Fire, Tier 1 and Tier 2 (Same code just small diffrences) Neither of those works, only Ice armors works).

Any help is appreciated!

Edit: I believe that it is the check which animation is playing condition that is bugged,
some weird reason it seems NOT to handle animations that is too far down in the animation list.

(<-- how to check this, look at the mmf file i uploaded under, Category Armor, Fire. Change the equip condition to ->Which animation is playing-> any ice armor animation, start application equip the ice armor you picked for the condition, then click the fire armor button of which you changed the code on and the equip string should say that you have the fire armor equiped)

Anyone that have had similer problems ? would be cool if a clickteam developer could shreed some light on this :D

I don't have time to completely debug this for you but do you notice the buttons flashing when you click on the fire armor 2?

If you put a sound on that event you will also see its looping so you might have an INI value or something set wrong.
Something is causing that condition to loop over and over and I think causing the problem.

You really shouldn't be reading/writing to the ini file like that though. You just need to read the ini file at the start, and then write to it at the end. You should just be using temporary values to store data so you aren't constantly accessing the ini file.

Thx jeff for a quick response :D !

Weirdest thing, i too notice that buttons are flashing in the example i uploaded, but in my main "file"(whole game mmf 2 file) they don't and the code is exactly the same as far as i can tell. I implemented a sound event but it didn't at all loop for me when using fire armors tier 1 and 2 (this would be in the example file and my main "file"). Builed 257.12

I try'd changing the fire armor tier 1 animation to walking instead but didn't work either so my first conclussion seems invalid.

Edit: I have been staring at the ini file for an hour and can't see any miss types. If the equip condition would "pass" i set it so i would get ridiculous values all over the ini file.

Konidias, thx for the tip.
But don't realy get whats bad with constantly accessing the ini file when doing a wardrobe frame.

Although i only read from the ini in start of the "gameplay" frames when write to it in the end of those.
I guess in theory it would take longer to access the ini file rather then the temporary values ?

Quote:

---

Originally Posted by Radical

I guess in theory it would take longer to access the ini file rather then the temporary values ?

---

Yes. You store the "temporary values" as global values. Globabl values aren't stored on the hard drive. INI files are. Hard drives take a while to be wrote to/read from. Global values are stored in the RAM. RAM is very quick to write to/read from.

23:46 Finnaly solved it!

Still got no clue what F it up,

Thx for the help and tips :D Good night!