Crashing when you see consumables from monsters.

Hi there! I have a noob question, my problem is I deleted all the consumables that will drop in the monsters, but they still dropping. I deleted it because when I tried to farm when I change my view I will get crashed. I used V19 Source, help :)

Here's some codes that I did.
And this Aibatt still dropping Lolipop. :confused::confused:

MI_AIBATT1
{
Maxitem = 1;
DropGold(60, 90);
DropItem(II_GEN_GEM_GEM_TWINKLESTONE, 300000000, 0, 1);
DropItem(II_GEN_GEM_GEM_TWINKLESTONE, 300000000, 0, 1);
DropItem(II_GEN_MAT_ORICHALCUM01, 100000, 0, 1);
DropItem(II_GEN_MAT_MOONSTONE, 100000, 0, 1);

Have you take a look in your propDropEvent.inc? There you can set up the general drops.

Ressiing your datas?

Thanks! I will check it.

Quote:

Originally Posted by KingKeesie Ressiing your datas?

What do you mean ressiing, sorry.

Quote:

Originally Posted by ​Lumi Have you take a look in your propDropEvent.inc? There you can set up the general drops.

Sweet! Thank you very much, I will check it I wish it works

Debug your error?

If it is based on your view, it is probably your maximum rendered object array is too small.

Quote:

Originally Posted by Avalion Debug your error? If it is based on your view, it is probably your maximum rendered object array is too small.

It is not only for first person, it is general, I literally deleted all the unnecessary drops like consumables for the monsters, but they still dropping it. And I do not know why...

PropDropEvent.inc handles some item drops based on level of mob. Look at that. But if it is dropping too much, maybe lower your drop on your server to decrease the amount of drops. You can also edit the individual drop chances of said items in PropMoverEx.inc and PropDropEvent.inc.

Secondly, if it is crashing due to maximum view of objects, you can increase the array size to allow more objects to be rendered on the user's client -- which is why I mentioned it. If you wanted to keep drops in rather than removing the drops.

Although, debugging would be the best choice as you can find out your error through it, and fix it in the source rather than trying to fix your resource so your source doesn't yell at you.

Quote:

Originally Posted by Avalion PropDropEvent.inc handles some item drops based on level of mob. Look at that. But if it is dropping too much, maybe lower your drop on your server to decrease the amount of drops. You can also edit the individual drop chances of said items in PropMoverEx.inc and PropDropEvent.inc. Secondly, if it is crashing due to maximum view of objects, you can increase the array size to allow more objects to be rendered on the user's client -- which is why I mentioned it. If you wanted to keep drops in rather than removing the drops. Although, debugging would be the best choice as you can find out your error through it, and fix it in the source rather than trying to fix your resource so your source doesn't yell at you.

I tried it aready in propmover, and drop rate for the server but it wont. Maybe the last hope I can do is to check the propdropevent and the array size. Thank you!

Open some Data in your Resource using Notepad++
CTRL+F => enter the II_ => Search Options => *.*
Select path of the Resource folder and SCAN

Try edit your data.res, datasub1.res and datasub2.res if you didnt did it already

Quote:

Originally Posted by KingKeesie Try edit your data.res, datasub1.res and datasub2.res if you didnt did it already

I was about to sleep and caught some stupid.

Drops arenot loaded on cliwnt. Propdropevent is server sided only file and propmoverex if not already can be made server sided only file too (drops and silly ai shit)

Sent from my LG-H812 using Tapatalk

Quote:

Originally Posted by Avalion I was about to sleep and caught some stupid. Drops arenot loaded on cliwnt. Propdropevent is server sided only file and propmoverex if not already can be made server sided only file too (drops and silly ai shit) Sent from my LG-H812 using Tapatalk

i know that but propmoverex is also in these datasubs if im right? on default

Quote:

Originally Posted by Dr. Peacock Open some Data in your Resource using Notepad++ CTRL+F => enter the II_ => Search Options => *.* Select path of the Resource folder and SCAN

I will try this step! Thank you very much for help!

Quote:

Originally Posted by Avalion PropDropEvent.inc handles some item drops based on level of mob. Look at that. But if it is dropping too much, maybe lower your drop on your server to decrease the amount of drops. You can also edit the individual drop chances of said items in PropMoverEx.inc and PropDropEvent.inc. Secondly, if it is crashing due to maximum view of objects, you can increase the array size to allow more objects to be rendered on the user's client -- which is why I mentioned it. If you wanted to keep drops in rather than removing the drops. Although, debugging would be the best choice as you can find out your error through it, and fix it in the source rather than trying to fix your resource so your source doesn't yell at you.

Hi there! Sorry to bother again, where can I find the array size that you said? Some clues to start with thank you :)