These 2 plugins work fine when running together until I actually put a restriction on a skill - it doesn't actually matter what skill as long as the actor using the summon ability has it learned, as soon as I use the tag, I will get this error. Here is how to replicate the bug: After restricting a skill (what I was using
<Restrict>
State: 998
</Restrict>
)
Go into combat and summon an actor using the plugin. On the next turn, when you go to your skill menu the game will crash and you will get the error "Object too deep."

After looking around for hours I found that this may be caused by the two plugins using the same variable perhaps? I'm not sure at all, since I am really bad at programming. If anyone could help me out on this, it would be greatly appreciated. Both of these plugins are core to my game, and without them a looooot of things won't work in the game.

The above steps made it much easier to reproduce the bug, so it only took me about one hour to reproduce the bug following Sharm's instructions. I then explained in detail, for others helping to look for the bug how to reproduce the bug:

So I am asking you to follow these steps & yes it will probably take you one to two hours (maybe longer) to do this:

Isolate the problem down to "using the menu's demo file" with just plugins.

Post images of this in SPOILER tags like Sharm did.

Post clear step by step instructions like I did.

This will make it much easier for others, so they might be able to stomp your bug in one to two hours (maybe longer).

Without clear instructions from you, it could easily take them even more hours to stomp your bug. Thus solving bugs is a cooperative process between the bug reporter & the people trying to stomp the bug.
​

(I've removed almost all the sound and images from the folder to reduce the size of the download)

After loading the plugins, the first step is to make an actor that will be summoned into the battle. For the Demo I named this: "Summoned Thing"

Next is to create a skill that will summon him. This is done by creating a spell, and placing the following in the note tag:
<Summon>
Actor ID: 5
<End Summon>
The actor ID being the actor who will be summoned into the battle.

So far this has all been for the summon plugin, which works fine. You can go into the demo and fight, and you can summon the enemy and cast spells without hitch after this. Next we will move on to the Restrictions plugin. For this we will add the following notetag to the skill "Fire"
<Restrict>
LevelMin: 1
</restrict>
This will tell the plugin to only allow the actor to be able to use the ability if he is Level 1. This bug can be replicated with any restriction tag, I'm just using this one as an example.

Make sure to give your actor both the Fire spell and the Summon spell so you will be able to use them in game.

Now to replicate the bug.
Play test the game and enter battle by talking to the npc. Once in battle, use the Summon spell to summon the actor to battle. In this demo he won't be visible due to being designed to work with the side view battle system, but I can assure you this works when implemented, I've just omitted it to cut down on file size and to reduce the chances of interference from other plugins during this test. Once it is your turn to act again (not the summons) go to your skill menu, and the following error will appear.

This bug can be stopped by changing the restrictions on the spell "Fire". If you have restrictions on any other spell that the player has not learned in game yet, the bug will not happen, it only happens when the player has a spell in his inventory that has the restrictions note tag applied.

Wow - Very nice. I watched the video & it makes it super clear how to reproduce the bug:

I'll be linking to this bug report in the future as another example of writing a great bug report!

​

Joyfully,

Joy Diamond,

P.S.: If no one else looks at it later today, I'll be sure to take a look at it (I have to head out to church now and then visit a friend afterwards to work on the MICA - Monster Is Coming ARGGH! game together ... so I can't look at it for quite a few hours ... but after that I can ...)

2017-11-20 12:00am UTC I'm looking to reproduce the bug now

2017-11-20 12:20am UTC Bug has been reproduced due to the excellent video by KawaiiKid .... but bad news ...

The bug is triggered inside of the rpg_core.js as a recursive call. These are hard bugs to find ... sometimes very hard ...
(NOTE: The bug is probably not in rpg_core, but just triggered there ...)

2017-11-20 12:30am UTC Ok, now we are looking at the code that is in the above stack trace ...

Ok, this is looking a bit more positive ... It is probably a recursive object that is self-referential from one of the other two plugins that is causing this bug ...

2017-11-20 12:45am UTC Ok, now we have modified the code & can see it in the debugger:

2017-11-20 1:20am UTC GRR, found a totally unrelated bug in rps_core.js!! Took me half an hour .... I'll report on it later ...

2017-11-20 2:00am UTC So have found the self-referential object & what it means:

It is basically Harold._summons[0]._battleSprite.parent.parent.parent.parent.stage.stage

Update: After looking at this 3 & a half hour, I have a very good idea of the bug. How to fix it is another matter though ....