Tim Kurvers
Tim Kurvers
> For your tilesets are you using any spacing/padding? That causes me issues sometimes No spacing/padding on the tileset. Only difference between the entities is the rectangle selection (as far...
A potential workaround here is to force webpack into the browser-compatible branch, using the [`DefinePlugin`](https://webpack.js.org/plugins/define-plugin/): ```js new webpack.DefinePlugin({ 'typeof process': JSON.stringify('undefined'), }), ``` We're currently using this successfully (https://github.com/wowserhq/client/commit/8c61884f1c0575e15a63d9bcb5b8a1bad3810d62) but...
Agreed @hmans, definitely safer to fix from within. Like your approach 👍
That's totally true, didn't think about that. I suppose binding the skeleton to the submesh is enough?
:+1: You mentioned something about a flat plane fog as opposed to circular, does that apply to both `Fog` and `FogExp2`?
The core library of Wowser currently starts loading in textures using WebWorkers, this is not really necessary when building – say – a bot.
I'm assuming the current implementation should result in some funky stuff by loading the wrong doodads? Do we have any examples? Would love to see that 😄
According to [this issue](https://github.com/3rd-Eden/FlashPolicyFileServer/issues/9) it's due to `policyfile` using `process.EventEmitter`, which has been removed in Node 7. Using Node 6 should work. This is not `wowser`-specific, but is probably something...
Ah, great reference, that has to be it :+1: Tracked by #97 and #98 in that case.