05-17-2024, 01:00 AM
Sorry to take so long to answer. Real life got in the way.
I followed the instruction and the problem persists.
I placed the code below my copy of the script and the problem persists. So I did your second suggestion and I think the guilty party is Blizzard's Stormtronics Custom Menu System. Kind of amazing it took this long for this unholy behemoth of a script to cause trouble.
(04-29-2024, 01:23 PM)DerVVulfman Wrote: First, he said he deleted every script within his duplicate project except for yours and the default scripts. So no additional scripts should have been involved.
STILL, to narrow this down....
STEEL? With the same said 'duplicate' project you used, go into its 'Data' folder, the one that contains all of the .rxdata files.
COPY a "Skills.rxdata" file from a blank project and PASTE it into the Data folder of your duplicate, thereby erasing and resetting your Scripts Database. After doing that, you should have nothing in the Scripts database but your Default Scripts without chance of possible accidental corruption.
Then paste your currently set up copy of KSkillsEquip into your project.
This should give you the same result as you did when you eliminated every custom script as previously instructed unless something was tweaked within your default scripts.
If you find that the problem no longer exists with this method, then something was indeed wrong with your default scripts, something corrupted and altered.
If you find that the problem still exists, then it is indeed KSkillsEquip.
No ambiguity.
I followed the instruction and the problem persists.
(04-29-2024, 01:37 PM)kyonides Wrote: Those steps should be followed for certain, but I know it makes no sense to think that my script is causing that issue. Especially when the code doesn't alter the item consumption feature while using the direct or check system.
KIND OF IMPORTANT EDIT
Just in case Wulfo's recommendation fails, and there is any possibility that KEquipSkills XP could be kind of permissive at the time that it performs the corresponding direct or check tasks, try this piece of code as a separate script.
Code:class Game_Party
def teach_item_skills?(item_id)
return if item_number(item_id) == 0
@actors.find {|actor| actor.teach_item_skills?(item_id) }
end
end
It's a slightly modified version of the same method already present in the main KEquipSkills script because it only adds this line of code:
Code:return if item_number(item_id) == 0
SUGGESTION
You could also discard any external influence following a modified version of Wulfo's debugging methodology. Instead of starting eliminating scripts and all that stuff, you pick a copy of my demo, with default scripts untouched plus 2 KEquipSkills scripts plus Game INI Data Extractor and start adding your custom scripts one by one.
I placed the code below my copy of the script and the problem persists. So I did your second suggestion and I think the guilty party is Blizzard's Stormtronics Custom Menu System. Kind of amazing it took this long for this unholy behemoth of a script to cause trouble.