panda

We'd prefer that this game jam is specifically called out in the advertising material as not being official, e.g. being called "Niko's Intersect Game Jam". JC and I don't really have the free time at the moment to be involved in this, but it's not a bad idea. If this game jam does garner enough interest, we can work on planning a game jam together with the community to take place further into the future when we do have more time to properly support it and provide meaningful prizes.

It doesn't actually do anything. I added it intending to put experimental features behind it, but it never caught on.

1. The screenshot is not an error, you need to follow the instructions 2. Your original post is not in English, but it is posted in the English section

What version of Intersect are you using? What operating system, and what version of that operating system are you using? What overlay are these numbers coming from? What specific CPU model are you using?

I'm not sleeping, 0

@Artheios v0.7.2-beta.2 had a bad workflow file, which worked fine when it was on my personal repo testing it due to bad cache-related configuration. I have since fixed the workflow and v0.7.2-beta.7 has the full downloads, but... they report the wrong version. This is because of the build caching, where it actually skips recompiling the binaries if nothing changes but the build number is based on the actual GitHub run. Before publishing build #7, I ran it once to verify that everything worked correctly in debug mode (it does not publish anything) and so since nothing actually changed between the two, it did not recompile to change the binary number. I think that this probably also applied to when I bumped the version from 0.7.1 to 0.7.2, because I didn't actually modify a .cs file to do that, it was a change in a .props file. Until we have another build that actually changes code however, the binaries will not actually recompile and so the version number won't change -- that said, v0.7.2-beta.7 does contain updated binaries, so you can use that in the interim, let me know if you find any more problems in that. I will see what I can do to make the release information match the binary numbers but that may take a few days.

The inventory window is draggable by default, you do not need to change any settings in those files.

Update on this situation: Wix cannot be used with Intersect's updater system. This is because it disallows uploading .json (which is the format the update manifest is stored in), and .exe (which is the client file format). A video walk-through and text instructions have been added to the official documentation: https://docs.freemmorpgmaker.com/en-US/deploy/updater/

This should be resolved in v0.7.1.117-beta

This is (partially) covered in the documentation: https://docs.freemmorpgmaker.com/en-US/deploy/updater/#creating-an-update

@Blestro If you have it and are interested in a little bit faster turnaround, we can debug this problem on the Discord server. In the mean time, can you try replacing internal static void ProcessUnhandledException(object sender, Exception exception) with the following and see if the crash will dump any information to the logs or the console? internal static void ProcessUnhandledException(object sender, Exception exception) { var currentException = exception; var innerException = false; do { Console.Error.WriteLine(currentException.Message); Console.Error.WriteLine(currentException.StackTrace); var message = innerException ? "Caused by:" : $"Received unhandled exception from {sender}."; Log.Error(currentException, message); currentException = currentException.InnerException; } while (currentException != null); }

@Blestro Can you try checking out specifically this commit (SHA d416695aefe79d7de7b6d88e6dcdf02dbb8916e5) and seeing if you can run without the crash? I have a feeling that the commit immediately after it is the one that is causing this crash with no information, but I have never been able to reproduce it and you are the first person who seems to be able to reproduce it and be compiling the source (which will help debugging it).

Currently we do not have the ability to zoom the camera, so at least until it is something that can be done the recommendation is to just make 16x16 sprites, and then scale up to your desired "zoom" level (don't delete the 16x16 originals though! Zoom is something we want to support but we have not had the time to address it and nobody who has attempted it has succeeded to my knowledge).

"Sprite Cast Anim" is an override for the player sprite added in PR#1347. The gist is that if you have a sprite called "base-male.png" you add "base-male_cast.png" in the same directory as "base-male.png" and it will be an allowed override for the player sprite itself when they are casting.

What is the latest commit that you have?

Only one of the map boundary issues has been fixed, but if you were on B6 until recently you never would have hit the fixed one since it was introduced and fixed in B7.1 months ago. The longer term one has not been fixed (and I am not sure if anyone has figured out a root cause yet).

You can run it with something like Sqlite Studio, or some sort of SQLite DB browser that is not read-only and allows you to run SQL queries in it.

Because this issue is so weird (and happens in the middle of a step) I am not 100% confident in the fix (so if you want to run it, make a backup first and keep it in case someone finds an issue later) but I ran the following script: DELETE FROM Player_Bank WHERE PlayerId NOT IN (SELECT Id FROM Players); DELETE FROM Player_Friends WHERE OwnerId NOT IN (SELECT Id FROM Players); DELETE FROM Player_Friends WHERE TargetId NOT IN (SELECT Id FROM Players); DELETE FROM Player_Hotbar WHERE PlayerId NOT IN (SELECT Id FROM Players); DELETE FROM Player_Items WHERE PlayerId NOT IN (SELECT Id FROM Players); DELETE FROM Player_Quests WHERE PlayerId NOT IN (SELECT Id FROM Players); DELETE FROM Player_Spells WHERE PlayerId NOT IN (SELECT Id FROM Players); DELETE FROM Player_Variables WHERE PlayerId NOT IN (SELECT Id FROM Players);

@PrincessNoodlelimbs So while it wasn't immediately clear as to what was happening, with some debugging it looked like there was a foreign key constraint violation, and when I checked it looks like it was legitimate. You would not have happened to have deleted players from the database, would you? Because there were a bunch of rows in not just Player_Spells (which is modified in the migration that fails for your database) but all of the Player_* tables that referenced players that did not exist in the Players table.

Congrats! I need the latest playerdb that isn't working when you try to upgrade it (so from 0.7.1.74) and if you want to also provide the older DB from before that's fine too, I can use that to make sure I fix the issue for both.

The generic UI art is in default-skin.png and intersect-2021.png, from the screenshot it looks like you are using the intersect-2021 skin. MenuWindow affects only the menu window, for the non-generic windows they each have their own layout files:

Ok, unfortunately the logs aren't giving me a hint as to why the SQLite migration is failing on your PlayerDB. If you could send me a copy via a more private upload (honestly if you wanted you and the playerdb is under 20MB you could use email and send to my public email listed on GitHub, [email protected]) I can see if I can figure out what is going wrong.

Can you upload the logs? (If they don't tell me enough I may also end up asking you to DM me a copy of your DBs but uploaded via something that allows you to delete the file, which the AGD file host does not.)

No. The strings JSON file is for mapping the names or values in the source code to end-user visible text, the formula JSON corresponds to the actual names in the source code which do not change.

Can you check if you can upgrade beyond .74 now? I wonder if the way migrations are applied that a straight upgrade from 0.6 can't go to .77+.