System Item Restrictions

AceHart

Your Friendly Neighborhood Admin
Reaction score
1,494
Every now and then, there might be a need to put some restrictions on your items.
As an example, your map uses different types of "swords",
and you'd like your Heroes to only be able to carry one of those,
not two or more at the same time.


Code:
ThisItemOnlyOnce
    Events
        Unit - A unit Acquires an item
    Conditions
        Or - Any (Conditions) are true
            Conditions
                (Item-type of (Item being manipulated)) Equal to Healing Salve
                (Item-type of (Item being manipulated)) Equal to Rod of Necromancy
    Actions
        For each (Integer A) from 1 to 5, do (Actions)
            Loop - Actions
                If (All Conditions are True) then do (Then Actions) else do (Else Actions)
                    If - Conditions
                        (Item-type of (Item carried by (Hero manipulating item) in slot (Integer A))) Equal to (Item-type of (Item being manipulated))
                    Then - Actions
                        For each (Integer B) from ((Integer A) + 1) to 6, do (Actions)
                            Loop - Actions
                                If (All Conditions are True) then do (Then Actions) else do (Else Actions)
                                    If - Conditions
                                        (Item-type of (Item carried by (Hero manipulating item) in slot (Integer B))) Equal to (Item-type of (Item being manipulated))
                                    Then - Actions
                                        Hero - Drop the item from slot (Integer B) of (Hero manipulating item)
                                        Quest - Display to (Player group((Owner of (Hero manipulating item)))) the Warning message: Sorry, this item only once
                                    Else - Actions
                    Else - Actions

How does it work?

If you get a new item,
we have a look at what item exactly it was.
If it fits the conditions, we then find out in what slot your Hero currently has that item.
That's the first "for integer".
It only needs to run from 1 to 5, because, if we didn't find the item until then,
there's no way to have two of them anyway...
Can't have two items in one slot, now, can you?

Once we found it, we look through all the other slots after that one.
That's the second "for integer".
And, well, if we find that very same item once more,
we simply drop it from the Hero,
and show some message like "Nah, doesn't work".

The "actions" code is very generic.
Meaning, if you have several items this rule should apply to,
you can simply put all of them in the "conditions" part.
The trigger will work as is.

In my example up here, it will limit both "Healing Salve" and "Rod of Necromancy" to one only.
You can have both together, but only ever one of each.


There's also a slightly simpler version of this:
Code:
ItemOnce
    Events
        Unit - A unit Acquires an item
    Conditions
        Or - Any (Conditions) are true
            Conditions
                (Item-type of (Item being manipulated)) Equal to Cheese
                (Item-type of (Item being manipulated)) Equal to Blood Key
                (Item-type of (Item being manipulated)) Equal to Gem Fragment
    Actions
        For each (Integer A) from 1 to 6, do (Actions)
            Loop - Actions
                If (All Conditions are True) then do (Then Actions) else do (Else Actions)
                    If - Conditions
                        (Item-type of (Item carried by (Hero manipulating item) in slot (Integer A))) Equal to (Item-type of (Item being manipulated))
                        (Item carried by (Hero manipulating item) in slot (Integer A)) Not equal to (Item being manipulated)
                    Then - Actions
                        Hero - Drop the item from slot (Integer A) of (Hero manipulating item)
                        Quest - Display to (Player group((Owner of (Hero manipulating item)))) the Warning message: This item only once...
                    Else - Actions

Same idea, when we find the same item as the one we just got, remove it.


However, the first version can easily be adapted to item groups:

For example, several types of "Thoroughly Rusted Swords" or "Dunce Caps" or whatever,
and you'd like to limit your Heroes to one item only per group.

Based on the trigger above, you'll need one trigger per item group:

Code:
ThisItemOnlyOnce
    Events
        Unit - A unit Acquires an item
    Conditions
        Or - Any (Conditions) are true
            Conditions
                (Item-type of (Item being manipulated)) Equal to Healing Salve
                (Item-type of (Item being manipulated)) Equal to Rod of Necromancy
    Actions
        For each (Integer A) from 1 to 5, do (Actions)
            Loop - Actions
                If (All Conditions are True) then do (Then Actions) else do (Else Actions)
                    If - Conditions
                        Or - Any (Conditions) are true
                            Conditions
                                (Item-type of (Item carried by (Hero manipulating item) in slot (Integer A))) Equal to Healing Salve
                                (Item-type of (Item carried by (Hero manipulating item) in slot (Integer A))) Equal to Rod of Necromancy
                    Then - Actions
                        For each (Integer B) from ((Integer A) + 1) to 6, do (Actions)
                            Loop - Actions
                                If (All Conditions are True) then do (Then Actions) else do (Else Actions)
                                    If - Conditions
                                        Or - Any (Conditions) are true
                                            Conditions
                                                (Item-type of (Item carried by (Hero manipulating item) in slot (Integer B))) Equal to Healing Salve
                                                (Item-type of (Item carried by (Hero manipulating item) in slot (Integer B))) Equal to Rod of Necromancy
                                    Then - Actions
                                        Hero - Drop the item from slot (Integer B) of (Hero manipulating item)
                                        Quest - Display to (Player group((Owner of (Hero manipulating item)))) the Warning message: Sorry, this item only once
                                    Else - Actions
                    Else - Actions


In this example, your Hero can have one of Healing Salve or one of Rod of Necromancy,
but not two of the same type,
and not more than one of each.


Happy mapping.


Yours,
AceHart


By popular request, please find attached a demo map with
"Single Item", "Item Groups" and "Class Based" item restriction triggers.
 

Attachments

  • ItemRestrictions_Demo_AceHart.w3x
    15.2 KB · Views: 1,145

skytainted

New Member
Reaction score
3
Thanks! This is required to all RPGs or Campaigns out there to minimize you maximum damage dealt and armor. Like the Final Fantasy map by ILYAS.
 

emjlr3

Change can be a good thing
Reaction score
395
cant say I tried the map, but a neat addition might be to provide a custom function which allows a user to pass an item type of their choice to be used in this "system", and creates a trigger for them to do just this...no?
 

Piranha

New Member
Reaction score
0
Great job!

Really great job! I spent a long time looking around for that excact trigger... I think alot of people would be very happy for a link to this page :)
 
General chit-chat
Help Users
  • No one is chatting at the moment.
  • The Helper The Helper:
    Actually I was just playing with having some kind of mention of the food forum and recipes on the main page to test and see if it would engage some of those people to post something. It is just weird to get so much traffic and no engagement
  • The Helper The Helper:
    So what it really is me trying to implement some kind of better site navigation not change the whole theme of the site
  • Varine Varine:
    How can you tell the difference between real traffic and indexing or AI generation bots?
  • The Helper The Helper:
    The bots will show up as users online in the forum software but they do not show up in my stats tracking. I am sure there are bots in the stats but the way alot of the bots treat the site do not show up on the stats
  • Varine Varine:
    I want to build a filtration system for my 3d printer, and that shit is so much more complicated than I thought it would be
  • Varine Varine:
    Apparently ABS emits styrene particulates which can be like .2 micrometers, which idk if the VOC detectors I have can even catch that
  • Varine Varine:
    Anyway I need to get some of those sensors and two air pressure sensors installed before an after the filters, which I need to figure out how to calculate the necessary pressure for and I have yet to find anything that tells me how to actually do that, just the cfm ratings
  • Varine Varine:
    And then I have to set up an arduino board to read those sensors, which I also don't know very much about but I have a whole bunch of crash course things for that
  • Varine Varine:
    These sensors are also a lot more than I thought they would be. Like 5 to 10 each, idk why but I assumed they would be like 2 dollars
  • Varine Varine:
    Another issue I'm learning is that a lot of the air quality sensors don't work at very high ambient temperatures. I'm planning on heating this enclosure to like 60C or so, and that's the upper limit of their functionality
  • Varine Varine:
    Although I don't know if I need to actually actively heat it or just let the plate and hotend bring the ambient temp to whatever it will, but even then I need to figure out an exfiltration for hot air. I think I kind of know what to do but it's still fucking confusing
  • The Helper The Helper:
    Maybe you could find some of that information from AC tech - like how they detect freon and such
  • Varine Varine:
    That's mostly what I've been looking at
  • Varine Varine:
    I don't think I'm dealing with quite the same pressures though, at the very least its a significantly smaller system. For the time being I'm just going to put together a quick scrubby box though and hope it works good enough to not make my house toxic
  • Varine Varine:
    I mean I don't use this enough to pose any significant danger I don't think, but I would still rather not be throwing styrene all over the air
  • The Helper The Helper:
    New dessert added to recipes Southern Pecan Praline Cake https://www.thehelper.net/threads/recipe-southern-pecan-praline-cake.193555/
  • The Helper The Helper:
    Another bot invasion 493 members online most of them bots that do not show up on stats
  • Varine Varine:
    I'm looking at a solid 378 guests, but 3 members. Of which two are me and VSNES. The third is unlisted, which makes me think its a ghost.
    +1
  • The Helper The Helper:
    Some members choose invisibility mode
    +1
  • The Helper The Helper:
    I bitch about Xenforo sometimes but it really is full featured you just have to really know what you are doing to get the most out of it.
  • The Helper The Helper:
    It is just not easy to fix styles and customize but it definitely can be done
  • The Helper The Helper:
    I do know this - xenforo dropped the ball by not keeping the vbulletin reputation comments as a feature. The loss of the Reputation comments data when we switched to Xenforo really was the death knell for the site when it came to all the users that left. I know I missed it so much and I got way less interested in the site when that feature was gone and I run the site.
  • Blackveiled Blackveiled:
    People love rep, lol
    +1

      The Helper Discord

      Members online

      Affiliates

      Hive Workshop NUON Dome World Editor Tutorials

      Network Sponsors

      Apex Steel Pipe - Buys and sells Steel Pipe.
      Top