#369 XPMultiplier in ruleset_details table not working

Fechado
2 anos atrás foi aberto por gitasaurus · 5 comentários

Increasing the value of rule_type XPMultiplier in ruleset_details does not change the amount of experience received from completing quests or killing spawns, using AOM client.

Increasing the value of rule_type XPMultiplier in ruleset_details does not change the amount of experience received from completing quests or killing spawns, using AOM client.
image comentado 2 anos atrás
Colaborador

it should all XP is derived from float Player::CalculateXP(Spawn* victim) -- againts spawns least, can't say for quests

what are you setting XPMultiplier to -- did you restart your world server after changing the value?

it should all XP is derived from float Player::CalculateXP(Spawn* victim) -- againts spawns least, can't say for quests what are you setting XPMultiplier to -- did you restart your world server after changing the value?
gitasaurus comentado 2 anos atrás
Autor

Thanks for the feedback. I hope I am doing something wrong.

Tested again this morning.

I opened LAUNCH EQ2EMU.bat with SET SQLUPDATE=2. The XPMultiplier was set at 2.0 . After logging into the game and killing a green lvl 5 spawn I received 13 xp. Closed EQ2.

I then changed the XPMultiplier to 0.5 and closed the three command windows. I opened LAUNCH EQ2EMU.bat with SET SQLUPDATE=3. I logged into the game and killed the same green lvl 5 spawn and received 13 xp. Closed EQ2.

I then changed the XPMultiplier to 4.0 and closed the three command windows. I opened LAUNCH EQ2EMU.bat with SET SQLUPDATE=3. I logged into the game and killed the same green lvl 5 spawn and received 13 xp.

I also verified in the xp bar that the starting xp total plus the earned xp from killing the spawn equals the new xp total, so it does not appear to be a display issue.

Let me know if I am missing a step.

Thanks for the feedback. I hope I am doing something wrong. Tested again this morning. I opened LAUNCH EQ2EMU.bat with SET SQLUPDATE=2. The XPMultiplier was set at 2.0 . After logging into the game and killing a green lvl 5 spawn I received 13 xp. Closed EQ2. I then changed the XPMultiplier to 0.5 and closed the three command windows. I opened LAUNCH EQ2EMU.bat with SET SQLUPDATE=3. I logged into the game and killed the same green lvl 5 spawn and received 13 xp. Closed EQ2. I then changed the XPMultiplier to 4.0 and closed the three command windows. I opened LAUNCH EQ2EMU.bat with SET SQLUPDATE=3. I logged into the game and killed the same green lvl 5 spawn and received 13 xp. I also verified in the xp bar that the starting xp total plus the earned xp from killing the spawn equals the new xp total, so it does not appear to be a display issue. Let me know if I am missing a step.
image comentado 2 anos atrás
Colaborador

thats my mistake there is a xp multiplier in the zone table that works, this rule does not

thats my mistake there is a xp multiplier in the zone table that works, this rule does not
image comentado 2 anos atrás
Colaborador

found the problem, there is no default global ruleset in the variables table

insert into variables set variable_name='default_ruleset_id',variable_value='1',comment='Default ruleset';
found the problem, there is no default global ruleset in the variables table ``` insert into variables set variable_name='default_ruleset_id',variable_value='1',comment='Default ruleset'; ```
image comentado 2 anos atrás
Colaborador

adding an error message for when that variable is not set..:

22:46:34 E Rules     : Variables table is missing default_ruleset_id variable name, this means the global rules will be code-default, database entries not used.  Use query such as "insert into variables set variable_name='default_ruleset_id',variable_value='1',comment='Default ruleset';" to resolve.
adding an error message for when that variable is not set..: ``` 22:46:34 E Rules : Variables table is missing default_ruleset_id variable name, this means the global rules will be code-default, database entries not used. Use query such as "insert into variables set variable_name='default_ruleset_id',variable_value='1',comment='Default ruleset';" to resolve. ```
image citou este problema em um commit 2 anos atrás
image fechado em 2 anos atrás
Faça login para participar desta conversação.
Carregando...
Cancelar
Salvar
Ainda não há conteúdo.