Closed GladieUO closed 6 months ago
It also happenes while @dclick on the normal food that is final product, not dropping from monsters etc... :-/
I dont think the fix helped.
it looks like an issue from script file, d_itemprop.scp line 72.
same error shows up with .xshow more2 on same item. The thing is, other values even tho they are 0 just show 0 instead of error. It seems like its still expecting someting to be in more2 or more1 even tho there dont need to be anything. 😫 But it is just annoying warning, nothing major.
Yes because the system changed for these types, and before they were on TDATA's, and now you have to move TDATA values from TDATA to MORE values to fix it. What I mean is; for example mr_nothing is set on TDATA1 before for trees, but now it changed to MORE1 so you need to add MORE1=mr_nothing under @Create trigger to fix this issue, but it can cause issues on already created trees so I don't know why someone made this change, because he didn't update X-Scripts depends on this update, also it wasn't necessary even if it should be added, it should added as override instead of removing tdata1.
Okay I sent another fix for it to fix warnings even MORE1 on Trees not looking implemented at all, I will take a look for later on, but this update should fix all warnings.
solved on dev branch, thank you!
Hi there is this warning if you try to open .info on the items with these types and if they dont have more1 or more2.
t_rock, if you dont set more1 on an item with this type, everytime you open .info it shows the warning. Shouldnt code check if more1 exist first, before validating it?
t_crops, same warning but if the more2 is not set, which is override value for the TDATA2, also should check if its valid first?
t_meat_raw same problem
t_food same problem