thijsvanloef
Feature/enhanced palworld settings
Context
- Providing convenience for modifying ini files (presented in a visible json format, with hints and setting ranges)
- Managing descriptions in multiple languages
- (Planned) Simplifying configuration changes and restarts by implementing a basic admin server
- (Planned) Managing server backup schedules
- (Planned) Detecting memory leaks and managing automatic restarts
- (Planned) Managing periodic server message sending features
Choices
- Please feel free to decline if this is not desired.
- I developed this for personal use and sharing, but sharing it as it takes too much time to develop everything on my own.
Test instructions
- So far, testing has only been conducted locally, and Docker testing is planned for this week to update it soon (1d ~ 3d)
- I tried to remove as much Korean as possible, but due to it being 03:33 AM Korean time, some might have been missed as I need to leave for work.
Checklist before requesting a review
- [x] I have performed a self-review of my code
- [ ] I've added documentation about this change to the README.
- [x] I've not introduced breaking changes.
Hi @NERDHEAD-lab, first of all I want to thank you for taking the time to create this PR. However I do believe this is a much too complex change to merge into the codebase. I do not have the knowledge/time to support a Python script for advanced config generation. I do however appreciate the time you took writing this and encourage you to open your own repository building on top of my repository
Hi @NERDHEAD-lab, first of all I want to thank you for taking the time to create this PR. However I do believe this is a much too complex change to merge into the codebase. I do not have the knowledge/time to support a Python script for advanced config generation. I do however appreciate the time you took writing this and encourage you to open your own repository building on top of my repository
Thx for comment @thijsvanloef Given the extensive modifications required to integrate ini parsing, decryption, and JSON provisioning capabilities directly, I'm planning to address this by deploying a separate Docker container. This container will leverage the rcon port and mounted volumes for file manipulation, thereby reducing coupling. Apologies for the delayed acknowledgment, and I appreciate your patience and review.