Yes, refactoring can be adjusting the code inside your libraries or adjusting your structure entirely (obviously not rewriting as much as possible).
Also, I would say that since the two rely on each other so much, you could probably save a lot of space just combining them into one library. I know I’m just restating my opinion from earlier, but unless you use these libraries for anything else, it probably makes sense to make a so-called “PlayerHandler” that handles data and kicking. The fact that they rely on each other means either you’re mixing too much, or they should be combined into one module.
I’m not an expert, but unless it’s some crazy extreme circumstance, try to decide based on how much the modules have in common. If there’s a lot, then you could merge them. If it’s not a large similarity, it could be a good idea to have a central library with their differences (but that’s also annoying to set up, as you might guess).
If you have some control script instead that manages these libraries, it would be able to give the libraries access to each other without having a circular dependency - you can just pass methods or call methods based on how your game logic is set up.
There’s a lot of options, usually it comes to personal preference + what the specifics are of your code layout. It might be worth playing around with multiple configurations if you have the time for that