Pedro

> What if its akin to the aliases for ip:port allocations? or would it be better to have that specified in the node config? Delay... aliases for ip:port allocations not...

> As far as I'm aware the original version didn't make exceptions for this, I don't see why it should now. i mean the original upgrade use the current directory...

> > i mean the original upgrade use the current directory not? for my case i use a custom directory for the app and the command work with no issues...

Confirmed since 1.10.0, the issue its here https://github.com/pterodactyl/panel/blob/1cfa4100adbd51102fc1afdbc581423fd5582fca/resources/scripts/components/server/files/UploadButton.tsx#L75 where type not handle for all type of files.. this also happen with many other file types..

Example of this patch using. ``` @EventHandler(priority = EventPriority.MONITOR) public void onPlayerTeleport(PlayerTeleportEvent event) { getServer().broadcastMessage(event.getCause().toString()); } ``` ``` @EventHandler public void onPlayerMove(PlayerMoveEvent event) { // Why does this call a...

Rebased and now are two files (thanks indexs) :3

Friday of PR rebased.

Ok i see the upstream JIRA and here.. the issue its related to the NMS try to run again the method because if you use 0 for repair the remain...

ok i need search first... this issue can be solved by https://github.com/PaperMC/Paper/pull/7382

> I think 7382 isn't the right fix for this. What about treating 0 as "cancelled". That will prevent the recursion stack overflow issue. You can still have event spam...