Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error [data/scripts/talkactions/gm/position.lua:8: attempt to call a nil value] #1846

Closed
2 of 5 tasks
luanluciano93 opened this issue Nov 19, 2023 · 0 comments · Fixed by #1912
Closed
2 of 5 tasks
Labels
Priority: Low Minor impact Status: Pending Test This PR or Issue requires more testing Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@luanluciano93
Copy link
Contributor

Priority

Low

Area

  • Datapack
  • Source
  • Map
  • Other

What happened?

2023-11-17 00:50:00 - /home/otserv/data/scripts/talkactions/gm/position.lua:8: in function </home/otserv/data/scripts/talkactions/gm/position.lua:3>]
2023-11-17 00:50:02 - [2023-17-11 00:50:02.016] [error] Lua script error:
2023-11-17 00:50:02 - scriptInterface: [Scripts Interface]
2023-11-17 00:50:02 - scriptId: [/home/otserv/data/scripts/talkactions/gm/position.lua:callback]
2023-11-17 00:50:02 - timerEvent: []
2023-11-17 00:50:02 - callbackId:[]
2023-11-17 00:50:02 - function: []
2023-11-17 00:50:02 - error [/home/otserv/data/scripts/talkactions/gm/position.lua:8: attempt to call a nil value
2023-11-17 00:50:02 - stack traceback:
2023-11-17 00:50:02 - [C]: at 0x555555799f70

What OS are you seeing the problem on?

Linux, Windows

Code of Conduct

  • I agree to follow this project's Code of Conduct
@luanluciano93 luanluciano93 added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Nov 19, 2023
@github-actions github-actions bot added Priority: Low Minor impact Status: Pending Test This PR or Issue requires more testing labels Nov 19, 2023
@beats-dh beats-dh linked a pull request Nov 20, 2023 that will close this issue
@beats-dh beats-dh removed a link to a pull request Nov 20, 2023
@beats-dh beats-dh linked a pull request Nov 20, 2023 that will close this issue
dudantas added a commit that referenced this issue Nov 25, 2023
Refactored the '/pos' command in the game's scripting to support multiple input formats more robustly. The command now accurately interprets positions from table format '{x = ..., y = ..., z = ...}', the 'Position(..., ..., ...)' format, and the standard 'x, y, z' coordinate format. The update includes improved error handling and clearer user feedback for invalid inputs.

Resolves #1846
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low Minor impact Status: Pending Test This PR or Issue requires more testing Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
1 participant