-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues/Bugs found in general #149
Comments
Ill take a closer look tomorow, but morik does exist, atleast in my monster pack(im using the one printer released not the one someone else released - that is full of glitches...) The problem is or was(dunno if I changed the script here on github) is that its the wrong uid or aid in the script, so when you use the item it will always return false before even trying to spawn the monster. Ghost charm, also know about that bug, is on my todo list. Anni should be working - gonna do a test when I can gather my team to test it or when I have the time to mc 3 other clients. Insted of removing the metatag function (my bug sorry) change it to |
Yeah morik is lacking in this revs pack (since it was "patched" away by a contributor. Nice addition! |
this can be close? is already fixed right? |
Well morik isent a spawm, you use the 'weapon rack' and he spawns
|
so ned to remove the spawn and the action for weapon rack have? |
Yalahar and annihilator works now. |
BUGs:
General BUG:
Annihilator quest:
In Service of Yalahar:
Quests.lua:
Fixing:
Annihilator Quest:
at annihilatorQuestDoor.lua, you will see this:
when in the XML and Map the UID is:
So a quick fix for this would be changing the item.uid == 2215 to:
at at annihilatorQuestLever.lua, you will see this in line 69:
which means it will be teleporting p who is the lever pulling player, and him only, to fix this we can replace this line with:
In Service of Yalahar:
simply add this line in spawn.xml nearly line 15100:
Add a new file in data/monsters/outlaws called morik.xml:
add this line to monsters.xml:
under:
<!-- Outlaws -->
(nearly line 600)
So far this is what I have fixed, any help will be appreciated.
The text was updated successfully, but these errors were encountered: