panda

So my question is what else is in that directory? Because from looking myself, IGE uses Newtonsoft.Json 13, and the error nvh had is Newtonsoft.Json 12 -- which Intersect uses. Makes me think IGE was dumped into the same directory as the Intersect client and then run. That said, I get a totally different error on clicking Update because IGE doesn't create the temp directory if it does not already exist.

Like I quoted from the actual documentation (not speculation), it's image/pixel format. We should add a try-catch to find out what the specific files are blowing up.

The client and editor both have autoupdaters for assets. Artists and musicians would be using other pieces of software for their work, but when they have something usable for the other people working on the project the assets they made can be added to the autoupdater. Maps, quests, events, etcetera are all done via the editor, which will be connected to a server. Multiple people can be working on it different pieces of the game content at once (e.g. different maps, different NPCs).

From the GDI+ documentation for the failing call:

Even 0er.

Supporting a WebGL client is not as simple as "we use mono, let's just compile it for the web", so... short answer: No. Slightly longer answer (but still no): We use Monogame for the client. The shortest route to a WebGL client is if Monogame supported a WebGL build. There is currently no official support for that, only prototypes still. The other route to a WebGL client is Unity. We do not have a working Unity client, and we have no plans for an official Unity client.

Correct, it does not load UI position from the JSON file. It only loads the URL.

-2

-1

-1

nopers 0000

I mean all of you downloaded Intersect for years before it was open source. If anything, the plugin system could open up an easier avenue for people to make cheats for games.

n0pe2

Hey if you guys say 0 it makes Damian's life easier.

-1

00

Damian is literally awake right now why are we even counting? And JC takes night shift even though he says nothing.

0

0

I'm for additional logging and am willing to provide input on how to structure it, but this is definitely something that should be contributed. I'd suggest opening a feature request on Github so we can have further detailed discussion on what specific things things should contain, etc. as a target for a PR.

ngrok does not support UDP and will not work.

Not seeing anything obvious in those logs. @jcsnider Any ideas? The version not being the same I would think is a different issue.

Can you delete your error logs and regenerate them. There's nothing in the logs that would explain the symptoms you are describing.

Can we have the error log too?

Or alternatively work on learning how to use the engine and in a couple of months when the dust settles make source changes then.