management assumes that a character's active job is the only job they hold. However, many servers use multi job scripts
Ideal solution
Write an abstract API for the getting/setting/updating of jobs and players that can be implemented for multi job support. And then add the functions to config. Since different multi jobs have different db schemas and ways of handling, this creates a generalized interface like structure so that someone implementing support for their multi job script need not re-write and/or modify the core of the resource.
In the future, PRs could also add support for specific multi job resources through implementing this interface and providing the set of implementation functions, or passing them around as snippets.
The problem
management assumes that a character's active job is the only job they hold. However, many servers use multi job scripts
Ideal solution
Write an abstract API for the getting/setting/updating of jobs and players that can be implemented for multi job support. And then add the functions to config. Since different multi jobs have different db schemas and ways of handling, this creates a generalized interface like structure so that someone implementing support for their multi job script need not re-write and/or modify the core of the resource.
In the future, PRs could also add support for specific multi job resources through implementing this interface and providing the set of implementation functions, or passing them around as snippets.
Alternative solutions
No response
Additional context
No response