Max enchant behaviour improvement
Posted: Sat Apr 17, 2010 10:19 am
Hello,
Was studying the maximum enchant handling this morning and I found what I consider as an incoherence.
The max enchant value is set in two places, first in the configuration and also in the AbstractEnchantPacket class.(com.l2jserver.gameserver.network.clientpackets)
I think the behavior goes wrong beacause in AbstractEnchantPacket we have a per scroll max enchant control while in the configuration you set a value for all the scrolls at once.
Right now the configuration value overrules the values in AbstractEnchantPacket unless the AbstractEnchantPacket is lower than config value.
I think it would be better to use configuration as a default configuration and if the max enchant set in AbstractEnchantPacket is different from 0 then it overrules the config.
I noticed this because I was implementing the Master of Enchantement Event.
In this event, it has to be possible to reach a +23 enchant. But our server has limited the max to +18.
So to do this, we had to increase the default enchant up to +23 and narrow this value (in the AbstractEnchantPacket) to +18 for all single scroll enchant except the special scroll for this event. (13540)
I will fix this myself for our server but I wanted to share my point of view and maybe the patch if there are interested people.
Cheers,
Ghurdyl
Was studying the maximum enchant handling this morning and I found what I consider as an incoherence.
The max enchant value is set in two places, first in the configuration and also in the AbstractEnchantPacket class.(com.l2jserver.gameserver.network.clientpackets)
I think the behavior goes wrong beacause in AbstractEnchantPacket we have a per scroll max enchant control while in the configuration you set a value for all the scrolls at once.
Right now the configuration value overrules the values in AbstractEnchantPacket unless the AbstractEnchantPacket is lower than config value.
I think it would be better to use configuration as a default configuration and if the max enchant set in AbstractEnchantPacket is different from 0 then it overrules the config.
I noticed this because I was implementing the Master of Enchantement Event.
In this event, it has to be possible to reach a +23 enchant. But our server has limited the max to +18.
So to do this, we had to increase the default enchant up to +23 and narrow this value (in the AbstractEnchantPacket) to +18 for all single scroll enchant except the special scroll for this event. (13540)
I will fix this myself for our server but I wanted to share my point of view and maybe the patch if there are interested people.
Cheers,
Ghurdyl
