You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm just worried that the things I finally made can be directly posted on other people's web pages.
I looked at the online tutorials
Found that wasm files and assets files are separated
If he obtains js and wasm files from the browser or crawler
He can turn it into another game by directly modifying the assets.
Is there any way to avoid
I don’t want to introduce too many dependencies, which will cause the exported file to be too large and slow to load.
My minimum requirement is that if the assets is changed, it cannot be run directly.
Is it possible to split wasm, just like a web framework, it can split multiple small files and load faster?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm just worried that the things I finally made can be directly posted on other people's web pages.
I looked at the online tutorials
Found that wasm files and assets files are separated
If he obtains js and wasm files from the browser or crawler
He can turn it into another game by directly modifying the assets.
Is there any way to avoid
I don’t want to introduce too many dependencies, which will cause the exported file to be too large and slow to load.
My minimum requirement is that if the assets is changed, it cannot be run directly.
Is it possible to split wasm, just like a web framework, it can split multiple small files and load faster?
Beta Was this translation helpful? Give feedback.
All reactions