[Solved] Triggers gone crazy

[Kanadaj]

Hi guys, I've just imported a trigger from my map to another, then my triggers went crazy... I'M sure variables don't overlap, but I don't know what causes this Any idea? Could it be that because of the import my triggers got corrupted?

 

[Pharaoh_]

What do you mean by "crazy"? What exactly has happened?

 

[Kanadaj]

It's hard to describe... But exactly not what should have happened... The analog-to-binary trigger gave crazy numbers, the trigger which should have emptied the inventory emptied it, but didn't put into it the correct set of new items (let's say a double inventory system) and if I pressed the change back (inventory set) button, it removed 1 item, then clicking again gave back 1 item, then clicking again removed 1 item and so on-but I used a cycle for this Oo

 

[Pharaoh_]

Systems that refer to item-types/unit-types/destructable-types that are not preset usually have nothing in that place when you paste them or they have "Unknown (A000)" (id of an ability for example).
You only have to reset the normal values there. Is this the problem you have just described?

 

[Kanadaj]

No, the normal values are set, the problem is the trigger doesn't work at ALL as it should... I rechecked my code like 50times, but it doesn't work...
For example this one generates the gems it should but it only generates 1 or 2 item of type " " -well I know it's weird to call an item like this but I imported the item from another player's map-so the item "Back to inventory" is in slot 4.

• For each (Integer A) from 1 to SocketedItemTypesNumber, do (Actions)
  • Loop - Actions
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • (Item-type of (Item being manipulated)) Equal to SockedtedItemTypes[(Integer A)]
      • Then - Actions
        • For each (Integer B) from 1 to 6, do (Actions)
          • Loop - Actions
            • Hashtable - Save Handle Of(Item carried by (Triggering unit) in slot (Integer B)) as (Integer B) of (Key (Triggering unit)) in SocketTempitems
            • Item - Move (Item carried by (Triggering unit) in slot (Integer B)) to SocketTempPlace
        • For each (Integer B) from 1 to (Load 1 of (Key (Item being manipulated)) from CurrentSocketsUsed), do (Actions)
          • Loop - Actions
            • For each (Integer X) from 1 to GemTypesNumber, do (Actions)
              • Loop - Actions
                • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
                  • If - Conditions
                    • (Load (Integer B) of (Key (Item being manipulated)) from SocketedGems) Equal to X
                  • Then - Actions
                    • Hero - Create UsedGemTypes[X] and give it to (Triggering unit)
                  • Else - Actions
                • Do nothing
        • For each (Integer B) from 1 to (SocketsMax[(Integer A)] - (Load 1 of (Key (Item being manipulated)) from CurrentSocketsUsed)), do (Actions)
          • Loop - Actions
            • Hero - Create Socket and give it to (Triggering unit)
        • For each (Integer A) from 1 to (5 - SocketsMax[(Integer A)]), do (Actions)
          • Loop - Actions
            • Hero - Create and give it to (Triggering unit)
        • Hero - Create Back to inventory and give it to (Triggering unit)
        • Skip remaining actions
      • Else - Actions

And if I click on the item Back to Inventory this should happen:

• If (All Conditions are True) then do (Then Actions) else do (Else Actions)
  • If - Conditions
    • (Item-type of (Item being manipulated)) Equal to Back to inventory
  • Then - Actions
    • For each (Integer A) from 1 to 6, do (Actions)
      • Loop - Actions
        • Item - Remove (Item carried by (Triggering unit) in slot (Integer A))
        • Hero - Give (Load (Integer A) of (Key (Triggering unit)) in SocketTempitems) to (Triggering unit)
  • Else - Actions

But instead it removes the first item, or replaces it with an item...
These triggers are absolutely separated, none of them should make things like these...

 

[Adiktuz]

I wouldn't be surprised if its caused by the successive Integer A/Bs... I have had experienced some crazy things from them on my former map...

try using Integer Variable blahblah rather than Integer A/B

 

[Kanadaj]

It worked thanks

 

[Magtheridon96]

See why using Integers A/B is bad?
This is actually a pretty good thread to use as a refference to the kinds of problems Integer A/B loops could cause.
I'll use this in the future

 

[Adiktuz]

yeah, on my map I experienced an almost the same scenario, some parts of the trigger just stopped working correctly... And I believe it was just two successive integerBs inside one integer A...

 

[Bannar]

Maggy, please let it be me who punish InfiniteAnswers (=