panda

Being completely honest I'm going to need to run the upgrade on your DB through the debugger because while I know what is failing I do not know why, but I also don't have time to do that right now (since I can't even build B7.1 on my computer right now, I will need to fix that first). As an interim solution/test can you try upgrading to 0.7.1.74-beta instead? The log is complaining about something introduced in .75-.77 so I would expect .74 to work (or produce a different error). Also just to be sure, have you only ever used the stock builds that we provide, or have you made source code modifications?

No, because the storage formats of the columns are different between MySQL and Sqlite (they have different features). The only correct way to migrate between the two is via the server migration command. If the migration command is not working you need to file a bug with detailed information on reproducing this including logs and either screenshots/text dump of the server console.

BLOB Fields are not empty, it just shows BLOB instead of their binary data (which is unreadable anyway).

What version of Mono do you have installed? What command did you use to start the server?

@Arufonsu opened a bug report for you and submitted a fix, it will be in tonight's build and should be available in the next 6-12 hours from the time of me writing this.

Looks like you replaced the comma with a semicolon and that is not parseable (resulting in the file being overwritten).

Yes, but it strongly recommended against doing so and not something we can deal with having to support.

0.7.0.126 is not the latest version. I also do not recognize that error even after translating it to English, and can't find results for it. I would suggest making a backup of your current files and then downloading the latest version from the main builds thread and trying again.

You need to provide: - what operating system you are using - what version of the operating system you are using - screenshots of the server console - any log files generated by the server when trying to upgrade (errors.log and Intersect-Server.<date>.log)

Unable to download a file from the URL you provided, the US is IP blocked. You need to provide: - what version you are trying to run - what version of Windows you are on - the errors.log file - the Intersect-Server-<date>.log files from the last three days (since you said it stopped working today and it has been a day since your post)

The Bad Version error is because you compiled your client, and tried to use it with the server you downloaded from us. You need to use your compiled server with your compiled client.

The idea was to have a bridge network running that servers and clients would both connect to. This was an idea that JC had but he has not worked on it since to my knowledge. That said, bandwidth and the servers to run such a network are not free, so someone would be paying the cost.

There are also some videos by Paul Hawse that go into some details. I haven't watched everything but it does seem like he gives decently in-depth explanations (and a very good roast of our lack of good documentation).

Your logs indicate it is trying to load the 0.5.1 core library which sounds like you dropped the latest binaries on top of the old ones. Try deleting all of the files outside of the resources folder and then copying in the new files again.

Which application was it? Client, Editor, or Server? What were you doing when it happened? Please provide your errors.log file.

The layout JSON files do not automatically update to include more or less slots. This is not a bug. I'm not entirely clear about what you are saying about the server changes, but if you think it is a bug, please file one.

One thing to add is right now when the build number changes we may or may not have updated assets. Downloading patch should be sufficient, but if you see something weird like a window not displaying correctly, then there was probably an asset change and you should download upgrade to get any missing asset changes.

It's normal and not an issue. Only errors matter.

Currently building the fix, but please next time open a bug when you encounter a StackOverflowException on a clean build (especially when you know which version causes it). For what it's worth, the SOE only occurs with metrics enabled.

There is a bug fix for inputs that may be related to #1455 merged and present in 0.7.1.57 which is currently building. Please test with 0.7.1.57 or later once available, especially @Ainz Ooal Gown (who I imagine is RecoStar on Github).

Request a Feature Report a Bug From now on we are going to use GitHub Discussions to track and request new features and enhancements, and GitHub Issues for scheduled work and reporting bugs. This is not just so we can kick requests out and never work on them, but we have a lot of open requests that have little community engagement, and many also that lack sufficient details to decide on a final implementation. Discussions, unlike Issues, actually enable us to have a high-level overview of desired features by the community via an upvote system that is visible from the list! We don't get that much information from the Issue tracker, it's mostly just showing us tags and other bits of information that are more useful for when something is actually in progress, rather than the beginning stages of a feature request. This gives us better ability to engage with the community and prioritize features that are actually highly desired by all of you, rather than features getting lost to time on page 6 or 7 of the issue tracker because we have no idea how many people actually want them to be implemented. We look forward to engaging more with the community with this new change!

I opened PR 1463 that fixes this bug. While I'm confident in the fix I'm going to let the other devs look at it first before merging. The fix should be in 0.7.1.51 (0.7.50 is going to be built in a few hours but it will not have the fix, it has two other minor fixes).

Thank you for providing the actual steps needed to diagnose the issue rather than just saying "settings don't save but they used to!!!". The information he provided is actually the step-by-step instructions I needed. Like Aru said I already pulled in a fix for this and I ran a rebuild, have just been waiting for it to finish publishing the new version before responding. The 0.7.1.49 client should fix the issue.

The API runs on TCP and the game connection is on UDP. It looks to me like you didn't allow inbound connections over UDP.

The chat tab buttons are right below the section you modified.