Duplicate registered item id: 2091

[Na Amigo]

i got this error and here is the search notepad++ i am trying to make the items with action id

[16:54:52.467] [Warning - Actions::registerEvent] Duplicate registered item id: 2091

here is my search

Search "2091" (4 hits in 4 files)
  C:\Users\amr\Downloads\Files\OTMadness\data\actions\actions.xml (1 hit)
    Line 420: <action itemid="2091" script="item seller.lua" />
  C:\Users\amr\Downloads\Files\OTMadness\data\items\items.xml (1 hit)
    Line 1780:     <item id="2091" article="a" name="golden key">
  C:\Users\amr\Downloads\Files\OTMadness\data\talkactions\scripts\tools.lua (1 hit)
    Line 19:     doAddContainerItem(container, 2091, 1)

 

[Infernum]

you have to look manually for something that's registering 2091 through a range of ids
aka something like itemid="2081-2095", which would register every id between 2081 and 2095

 

[Na Amigo]

you have to look manually for something that's registering 2091 through a range of ids
aka something like itemid="2081-2095", which would register every id between 2081 and 2095

i not found :/

some one could help with teamviewer? the error not solved i tried to search i found nothing guys

[Warning - Actions::registerEvent] Duplicate registered item id: 2091

 

[Shadowsong]

some one could help with teamviewer? the error not solved i tried to search i found nothing guys

[Warning - Actions::registerEvent] Duplicate registered item id: 2091

Well what Static_ said is most likely true.
If you can't find this ID directly in actions.xml, then it is concealed behind a defined range of ids ("fromid" - "toid") and it's somewhere in between.
With this being the most likely case, you'll have to search for it manually until you find it, however here's a tip that might be useful:

If it's a duplicate registration, then it must mean that this ID is registered to do some other action as well.
Delete what you added temporarily, and then use this item to figure out what kind of action script it is performing.
Once you know which script it's performing, you'll can find where this ID is hiding in actions.xml by searching for the line where that script is defined instead.

Also if what you wrote up there is true

 C:\Users\amr\Downloads\Files\OTMadness\data\talkactions\scripts\tools.lua (1 hit)

Then this is possibly the script that this key is tied to.

Find the line where tools.lua is in actions.xml, and it should be there probably.

 

[Na Amigo]

Well what Static_ said is most likely true.
If you can't find this ID directly in actions.xml, then it is concealed behind a defined range of ids ("fromid" - "toid") and it's somewhere in between.
With this being the most likely case, you'll have to search for it manually until you find it, however here's a tip that might be useful:

If it's a duplicate registration, then it must mean that this ID is registered to do some other action as well.
Delete what you added temporarily, and then use this item to figure out what kind of action script it is performing.
Once you know which script it's performing, you'll can find where this ID is hiding in actions.xml by searching for the line where that script is defined instead.

Also if what you wrote up there is true

 C:\Users\amr\Downloads\Files\OTMadness\data\talkactions\scripts\tools.lua (1 hit)

Then this is possibly the script that this key is tied to.

Find the line where tools.lua is in actions.xml, and it should be there probably.

well the problem from my action i removed but i want create with action can you enter team?

 

[Shadowsong]

well the problem from my action i removed but i want create with action can you enter team?

Team as in teamviewer? I won't do that in cases where stuff is super simple like this.

Find the line in actions.xml where the ID of the key is involved with -> Exclude the ID from being involved with this script -> add your own line that ties this ID to another script.

Just to give you an example. In my server, ID 2091 is within this:

<action fromid="2086" toid="2092" script="other/doors.lua" />

(As you can see, this action script activates for all IDs from id 2086, to id 2092 (2086,2087,2088,2089,2090,2091,2092).

I'd split this so that it leaves 2091 out:

<action fromid="2086" toid="2090" script="other/doors.lua" />
<action id="2092" script="other/doors.lua" />

And now I'd be able to use

<action id="2091" script="myscript.lua" />

without conflict.