It is possible ? (custom_loadout) problem.

[eduetr]

I think custom_loadout problems with this, the player is born with custom_loadout normal if it disconnects and reconnects him back with the loadout of the instance. My members have to custom_loadout skin_soldier, but when he disconnects the skin but keeps the inventory items and backpack are lost.

[Peep]

Yes, there is currently a custom loadout problem.

Sometimes players, when logging in, will get stuck on a loading screen (something went wrong, disconnect and try again). They usually retry multiple times, and eventually get in but without their custom loadout. If they die they will spawn in fine, but the problem will repeat itself later.

One of my players also reported that if you stay on the something went wrong screen without retrying you actually will spawn in with your custom loadout. I have not been able to test this theory yet.

[thevisad]

https://github.com/thevisad/DayZ-Private-master#github-support-issues

[Peep]

Service Provider: NFOservers.com Server Type (dedicated, vps, dayz server only): Dedicated World Name: Chernarus Reality branch(1.7.5 or 1.7.6): 1.7.6 DayZ_Code version: 1.7.6.1 Download for RPT/HiveLog: http://bmrf.me/download/Logs.7z Download for dayz_server.pbo/mission.pbo: http://bmrf.me/download/Files.7z HiveEXT.DLL version: I don't know where you get the version number, but it's the latest in the github as of now. MySQL Version: 5.6 Server name: BMRF DayZ #4 - 1.7.6.1 |VETERAN|PRIVATE HIVE|WHITELIST| - http://bmrf.me - Hosted by Billy Mays Remembrance Foundation Packages used to build: invcust, buildings, killmsgs, ssZeds Deatiled description of issue: Users will sometimes not spawn with a custom inventory, and will get stuck on Requesting Authentication, which eventually puts them at "something went wrong, disconnect and try again". They will usually get in eventually if they keep trying, but will not spawn with any custom loadout. If they die, it will usually fix the problem and they get a proper spawn, however it seems to be random and the problem will reoccur. I have reports from one user that if you wait at the "something went wrong" screen, you will actually get in after a few minutes with your custom loadout. I have yet to confirm this myself. This started happening since 1.7.6 and continued in the 1.7.6.1 release. I have 535 entries in the cust_profile table, but I don't think that would matter.

[thevisad]

Thanks Peep, I will look at the logs

[thevisad]

First thing I noticed is instance is set to 4 via the mission file; however, inside the mission its set to 2. Everything else looks ok. Whats your instance set to in the database?

[Peep]

It's also set to 2.

It's weird because we later changed our second instance to use it's own database, freeing up the second instance in the original database. I wanted the people who played on the server with a database wipe to have access to their tents and vehicles elsewhere, so a fourth server was born and it took the previous instance number. Nothing to be worried about.

[thevisad]

Recompile the dayz server with 2 as the instance and move just the mission file over and make sure to change it in your config as well.

On Sat, Mar 2, 2013 at 1:12 AM, Peep notifications@github.com wrote:

It's also set to 2.

It's weird because we later changed our second instance to use it's own database, freeing up the second instance in the database. I wanted the people who played on the server with a database wipe to have access to their tents and vehicles elsewhere, so a fourth server was born and it took the previous instance number.

— Reply to this email directly or view it on GitHubhttps://github.com/thevisad/DayZ-Private-master/issues/165#issuecomment-14323815 .

[Peep]

So you're saying the name of the mission file would have an effect on things? Where else is the mission number defined other than inside the mission on one line and in the database?

I already have another server using the dayz_2.chernarus mission file name. I guess I'd have to change it to 5, though I've had this setup for months now and it doesn't explain the issue popping up just now.

[thevisad]

The instance number is defined in the mission name, the config file at the map rotation towards the bottom, the database and inside the mission file itself. Yes it will have an effect on how the server reacts.

On Sat, Mar 2, 2013 at 1:18 AM, Peep notifications@github.com wrote:

So you're saying the name of the mission file would have an effect on things? Where else is the mission number defined other than inside the mission on one line and in the database?

— Reply to this email directly or view it on GitHubhttps://github.com/thevisad/DayZ-Private-master/issues/165#issuecomment-14323875 .

[Peep]

That change would require some downtime on a few servers, which I wouldn't be willing to do at this time of day. I'll get back to you when I can do this, though.

I would rather see if this issue only effects people who are on the specific server I reported, rather than all of them, which would give me an answer to this without downtime. Still skeptical that renaming the pbo file would do anything when the database, server config, and contents of the mission are correct. You can name a mission file anything so long as it's set properly in the config, there are no hardcoded filepaths as far as I'm aware.

Still though, I will try it if I can prove isolation of the issue to that specific server which would provide proof of concept.

Thank you for the help so far, I appreciate it.