Velocir_X":1ajwrult said:
Fenwick I think it may be something with they're hookshot
may some method its event or script uses
I'll take a look later
I'll have to look again at it this week.
But still awesome work Fenwick :thumb:
I'm curious how would I disable the hookshots combat?
(I am planning on just using it as a puzzle mechanic)
Give me some time, I'll add a switch you can set in the Scripts Configuration area.
Edit: UPDATE -
Fenwick Lorecarver's - Hookshot v1.1 RMXP --->
Clicky
Update:
1) Added the ability to "Grab" and draw into you, any Items you Create in an Event, if created Correctly
(Look at the Demo's Items to see how they were created. You also have to have an icon with the name of the
Event Item, in the "Icons" folder for this to work. Insert proper "Comments" on the first line of the active Page
of the Event Item.)
2) The ability to choose the collection SoundF/X for when collecting an Event Item on the screen, with Volume/Pitch
3) The ability to turn the Hookshot Tool ON/OFF for "Combat Use". Used if you do not want to harm any Enemies
with the Hookshot Tool, but use the Hookshot Tool strictly for Puzzle games, etc...
4) Tweeked how Civillians were treated when hit with the Hookshot Tool. These events are setup under the Enemies
Tab in the Database under the name: "Civillian" It is used for all characters you deem as Civillians, they do not
take damage when hit by the Hookshot Tool, but will remark on you doing so. Their Hit Points are never shown,
that is why we can use the one Enemy "Civillian" setup for all NPC's (None Player Characters who are not
Enemies) Or are, but can not be harmed as enemies. But, you could alwasy just use the Configuration in the
XAS "Battler" configuration area for characters such as those.
NOTE:
I have not updated the Word Document supplied with this Demo, sometime when I have time, I will update it.
I will continue to keep working on this version for XAS v3.4 until I or someone else figures out what in the XAS System script is causing the Incompatibility. This way when we find and correct the problem for implimentation, it will be easy to update the demo for XAS v3.5.
EDIT -
For Idea To Make Compatible With XAS v3.5:
Say, anyone know how to put a "Wait For Move Completion" in script format? I've tried putting it into a Move Route Script command, but that did not work
Fenwick Lorecarver