wplace++ breaks other scripts

[CedricKassen]

Hi there 👋🏻

I've build an alternative for Blue Marble, and I've received a bug report that my script isn't working if wplace++ is installed.
I've checked your code and noticed that you're patching window.fetch very destructively, which is most likely causing the issues. Would it be possible to not rewrite every incoming URL, or change the behavior of fetch in any other significant way? I'm pretty sure this is breaking compatibility with other user scripts as well.

Thank you!
Kind regards ^^

[RoootTheFox]

sorry for the late response; but patching fetch is relatively unavoidable in order to catch the initial map metadata request and rewrite it to my selfhosted instance. i might look into "unpatching" fetch after the initial fetch request to hopefully remedy those issues, but from my (albeit limited) testing in the past that has caused issues.

[RoootTheFox]

also; both blue marble and a fork of overlay pro (haven't tried the original) work fine for me, both on chromium and firefox, so these issues (#1 #2) are pretty much impossible for me to reproduce :(

edit: your wplace template manager works fine for me too (firefox)

[RoootTheFox]

technically i can avoid fetch calls by just calling _map.setStyle, but i don't want to place my bets on the current hacky way of getting the map instance to keep working for much longer (plus setStyle can cause some wacky behavior)