panda

The ZIP files available for download are picking specific files for inclusion in the build, what files they are are all listed in the publicly available bundles included in the main repo.

FYI you should use the MGCB pipeline tools from the version of MonoGame we are using which is 3.8.1 not 3.7.1 See the MonoGame documentation to install it. I think this is "ActionMsgFont" in the client's config.json.

So there is not a way to turn off the shadows, but the shadow is also not off center. What I am seeing in the screenshot you provided is either the background itself has a large transparent border (it shouldn't), or you changed something in the JSON that is creating that padding. The default assets have a shadow but I wouldn't have even noticed this if nobody brought it up, that's how imperceptible it is.

Follow the compilation instructions in the repo. They specifically say to use git and not download the source as an archive, based on the directory path in your screenshot it looks like it's from an archive https://github.com/AscensionGameDev/Intersect-Engine#compilingdevelopment

I don't know of a shadowing issue, if I had to guess I would think this is something with your GUI .json files or the shadow is baked into the GUI image.

Because 1. The feature goes against the vision of the main repo (too specific of a feature) 2. Now the dev team has to maintain another feature (but more importantly one we do not agree with being in the engine) 3. There are definitely changes that need to be made to make it main repo quality, so it's not "already implemented"

Send your game data to pandacoder@pm.me and I will inspect the DB. I do not think data was corrupted, but I do think your specific game data exposed a bug in the engine after migration. Reminder that you should also always be backing up your game data before changing versions of the engine.

No, this feature will not be getting merged into the main branch.

You need to provide: 1. Exactly what version of Intersect you were on 2. Exactly what version of Intersect you migrated with 3. If you had any source modifications, plugins, etc. prior to migrations

Making it so the game server can server pages/static assets in addition to the API. This is to make it easier for someone getting started to serve updated assets to multiple computers/people for a small dev team. I added a basic leaderboard to make it so the home page wasn't completely barren though.

I had posted screenshots of this a few weeks ago but I am finally getting back to finishing this stuff using the embedded web server:

Just as an FYI your patch does not include the MySQL migration (which do require setting up a MariaDB/MySQL server locally to create) and will only work for people using a SQLite player database.

That engine was likely ancient and didn't have textures with transparency (something like DX7 Mirage Source/Eclipse). Intersect only supports textures with transparency, so you will have to remove the background yourself if you are intending to use something that comes with a non-transparent background color.

It is not a patch, it is built into the engine directly. You need an updated version of the engine.

You do not use mono anymore, just run it directly.

This specific error happens most often when the application is closing and not everything is cleaned up in the correct order. I think all of the crafting crashes should be fixed right now (I'm guessing a separate error triggered this one) but in this case it's a matter of just restarting the client. I will look into preventing this error from hiding other errors so it's more clear what the issue is in the logs if the root cause happens again.

You're going to have to change the source for this. The hitbox is hardcoded to be the tile a sprite is standing on, and the the tile is expected to be where the "feet" of a sprite are, which applies when the sprites are intended to be at a ~45deg angle, but your game is 90deg angle looking directly down at the map.

To ditto Gibier but add something additional: If you have a translation, please share it so other people can use it. One other thing is that right now a language selector would effectively be useless. You could change the UI, but you cannot change the server's strings, and you cannot change the language of the content. We have been looking into improving this but adding translatable content (the thing holding this back) is not an easy task.

@TerrafydeCan you please send your DBs to pandacoder@pm.me so I can examine them and debug why the crash is occurring?

@TerrafydeIs this error log from trying 0.7.2-beta.65, or 0.8.0-beta.#?

Looking at that, those must be sections @jcsnider added. They just links to .zip files and not supported, nor are they maintained. JC can chime in, or you can go use XFall's PHP script which I know he recently updated and he maintains.

In addition to what @Smoot said: 1. Try the last 0.7.2-beta build (0.7.2-beta.65) 2. Please include the logs (and screenshots of the error in the server console if there are no logs) with any future reports. 3. There are no compiled downloads for before 0.7.2-beta as they were hosted on our TeamCity server that has been since shut down (but the source is still available on GitHub to compile from, not that I recommend doing so).

If you are using @XFallSeane's PHP update script (the pastebin is gone by the way) you should post in the appropriate thread (which I can't actually find for some reason), but docs.freemmorpgmaker.com will not help you with a bad PHP script, which the error message points to.

null standard input will kill the server, you need to run it in a screen (inside the docker container).