Lily's Item Identifier - Printable Version+- Save-Point (https://www.save-point.org)
+-- Forum: Material Development (https://www.save-point.org/forum-8.html)
+--- Forum: Scripts Database (https://www.save-point.org/forum-39.html)
+--- Thread:
Lily's Item Identifier (/thread-4014.html)Lily's Item Identifier - DerVVulfman - 03-22-2012
Lily's Item Identifier
Version: 1.1
Version: 1.1
Introduction
This lets you create an NPC as a character who can identify unknown items. By this, you can make an item on the screen as an 'unknown sword' that you may not be able to use until it is identified by your expert.
Script
(>Click<)
Instructions
Plenty, and in the script itself.
Compatibility
An RPGMaker XP script. Compatible with both Gullaume777's and DerVVulfman's Multiple Slots scripts and DerVVulfman's Super Simple Cursed Items script.
Terms and Conditions
Free for use, even in commercial games. Only due credit is requested.
RE: Lily's Item Identifier - yamina-chan - 03-22-2012
My first reaction was a sequel of joy since this reminded me at Blaze&Blade. Reading the instructions I noticed it was different after all but still a nice script.
This is not why I'm posting however.
No matter how many times I read the instructions, no matter how I set things up, no matter how I shaped the scene call, I always got this if I tried to call it:
![[Image: 19tq3o.jpg]](http://i42.tinypic.com/19tq3o.jpg)
Said line reads:
PHP Code:
if price <= $game_party.gold
RE: Lily's Item Identifier - MGC - 03-22-2012
DerVV > I didn't had the bug yamina-chan reported, but I had some other problems :
lines 657 and 666, there is :
657 : @difficulty = 100 if difficulty > 100
666 : if difficulty > @skill
That should be always @difficulty. (Perhaps it's a characters conversion problem with Word ?)
Moreover, when I succesfully identified all my items, the window was still here and the cursor pointed on a blank space. It crashed when I validated (@difficulty = nil line 657).
RE: Lily's Item Identifier - DerVVulfman - 03-28-2012
To yamina-chan:
I believe the issue is that you didn't properly set up the second 'set' of arrays that gauges item, weapon or armor prices and difficulty ratings. I replicated the error by screwing mine up. Since then, I rewrote the instructions... in detail.
To MGC:
It wasn't just that one @difficulty, but a couple of them.
And with that....
BUMP
To version 1.1
To version 1.1
Basically, I added more instructions and examples, and fixed a pair of @difficulty values.