04-29-2024, 01:23 PM
(This post was last modified: 04-29-2024, 01:25 PM by DerVVulfman.)
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.
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.