improve: adjustment in player event

[luanluciano93]

Description

• Renamed the 'config' Table for Clarity: The table previously known as 'config' has been renamed to enhance readability and understanding of its purpose.
• Added Conditional Checks to Prevent Null Returns: Implemented multiple conditional statements throughout the code to ensure that functions do not return null values, thereby improving the reliability and stability of the code.
• Optimized 'exhaust' Table Handling: Moved the 'exhaust' table outside of the function's scope for better efficiency. Additionally, set its value to null at the end of the addEvent function to ensure proper cleanup and prevent data persistence issues.

Behaviour

Actual

can generate errors, such as:
[error] Lua script error: scriptInterface: [Event Interface] scriptId: [data/events/scripts/player.lua:Player@onMoveItem] timerEvent: [] callbackId:[] function: [] error [data/events/scripts/player.lua:249: attempt to index a nil value stack traceback: [C]: in function '__index' data/events/scripts/player.lua:249: in function <data/events/scripts/player.lua:234>]

Expected

do not generate errors.

Fixes #issuenumber

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Test Configuration:

• Server Version: canary main
• Client: 13.21
• Operating System: Windows

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I checked the PR checks reports
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

[luan]

@luanluciano93 can you explain what this this in the description please? I can review the code but if I don't know what you're trying to do it's hard to do it quickly..

[dudantas]

I understand the intention behind the proposed changes in the pull request, but it's important to be cautious when altering code that is already functioning correctly. Changes like these can be prone to introducing bugs, especially if not well understood or documented. Could you please provide more details about the changes you are proposing? Additionally, I request that you follow our project's standard pull request template, which will help us better understand the context and rationale for these changes.

[luanluciano93]

done