Atlas Server Manager (Discontinued Source available) 4.4

[Joker]

Is this already abandoned?

 

[BattleSheep]

Is it really THAT important for you to troll this discussion? Don't you have anything better to do?

i only report a bug, you start to fight me.. if i see your other posts i think you are only here to make trouble.. Software has to work, just because a feature is not important to you they don't have stayed bugged..

 

[smooreace]

Software NEEDS to work the way it was designed to work. That doesn't mean that if it doesn't work how YOU want it that its a bug. So you arent here reporting a bug. Youre making a request.

 

[Menthelice]

Is this already abandoned?

Seriously the developer got probably RL stuff to do. He does this in his freetime for free. Show some appriciation!

 

[smooreace]

Seriously the developer got probably RL stuff to do. He does this in his freetime for free. Show some appriciation!

Its all about gimmi gimmi!

 

[baylf2000]

So version 15.61 was just released, and yet the steamcmd "+app_info_print" still shows the old version number. It's definitely broken. I had to quite asm and do a steamcmd "+app_update 1006030 validate" to get the newest version. I'll try and see if I can find the right place to ask the game devs about it. Unfortunately after I force the update, the app still does this: "[Atlas] Current BuildID: 3496928, Updating To BuildID: 3487616". I'm guessing the "!=" check is still there, instead of ">".

In the mean time, I have a couple of humble suggestions for the app.

1. That an additional "Check for updates now" button be added, which forces an update check, and completes the update if it detects one.
2. That the current "Force Update" button be set to acually perform an update + validate, without doing a version check first. That way if we know there is definitely a version available we can force the update anyway.

Also, it might be worth having a look at steamdb.info. Ther're database is updated within a minute or two and always has the correct build id. (https://steamdb.info/depot/1006031/) They actually have their full source code available on git (https://github.com/SteamDatabase). They use SteamKit somehow, but they're code it a bit beyond me, and anything related to steam and its APIs is an insane nightmare to figure out.

 

[smooreace]

There is absolutely zero need to validate in the update process. All it does is wasting time running a validation long enough to realize it needs updated and THEN starts updating. If we are FORCING an update it should be because we KNOW it needs it, not because we think it might.

 

[baylf2000]

There is absolutely zero need to validate in the update process. All it does is wasting time running a validation long enough to realize it needs updated and THEN starts updating. If we are FORCING an update it should be because we KNOW it needs it, not because we think it might.

WHY are you so toxic? What happened to you in your life to make you so vile and hateful?

Besides all of that, you also, yet again, don't know what you're talking about. The "+validate" portion of the steamcmd I was talking about in my post performs a very important function. It does the equivalent of the steam client "validate files" function. So if you run the command, and it finds an update, it will download and install it. If it finds no update, it will validate the local files instead. This is common practice across multiple management apps and has been for years.

 

[keroo]

I can confirm it doesn't update from ASM, i have to use a bat file.

 

[smooreace]

WHY are you so toxic? What happened to you in your life to make you so vile and hateful?

Besides all of that, you also, yet again, don't know what you're talking about. The "+validate" portion of the steamcmd I was talking about in my post performs a very important function. It does the equivalent of the steam client "validate files" function. So if you run the command, and it finds an update, it will download and install it. If it finds no update, it will validate the local files instead. This is common practice across multiple management apps and has been for years.

I obviously know exactly what it does, and know that it only needs to be done when the problem arises (which has never been the case on the server side of things since day one of Ark, Dark and Light, Conan, 7DaystoDie, Rust, Atlas, or any of the others that I might have missed since the day they were released. The ONLY thing it WILL do is increase downtime while it runs its course. And what fool runs an update when they don't KNOW the update is available, again negating the value of the validation?! But hey.. if downtime doesn't matter to you then by all means... fire away. The difference here is that I do this full-time. And all you can do is come back crying because I told you that your BELIEF is wrong. That doesn't make me toxic.. it makes you a tantrum throwing child.

In fact... I've probably been HERE longer than you've been dealing with game servers judging from your activity! When you have the background I have THEN come back and try to tell me Im wrong.

 

[baylf2000]

@OwnProx It's a horrible hack, but I've added a small function to my version to scrape the above steamdb html page to get the correct available version, and it seems to be working fine. It just detected and applied the most recent update that was release a few minutes ago. It's terrible I know, but it's about the only solution I can think of to the broken steamcmd until they fix it. I tried reporting the issue to grapeshot, but was told it's nothing to do with them and they don't care. Still looking for the appropriate area in steam to report the issue to.

 

[Michidu]

Let's get back to topic. Those useless fights only make it harder to find a real bug reports/suggestions for the developer.

 

[Baltazar]

Hello. Where can i download this tool?

 

[Foppa]

Hello. Where can i download this tool?

Go to the Overview and click on the download button in the upper right corner

 

[Baltazar]

Go to the Overview and click on the download button in the upper right corner

thanks

 

[scottr69]

@OwnProx It's a horrible hack, but I've added a small function to my version to scrape the above steamdb html page to get the correct available version, and it seems to be working fine. It just detected and applied the most recent update that was release a few minutes ago. It's terrible I know, but it's about the only solution I can think of to the broken steamcmd until they fix it. I tried reporting the issue to grapeshot, but was told it's nothing to do with them and they don't care. Still looking for the appropriate area in steam to report the issue to.

For me it isnt the fact it isnt detecting an update. It in fact knows there an update but skips the process because he clears the "UpdatePaths" using "UpdatePaths.Clear();" in the GetCurrentBuildID function before he uses it in the next function where it skips updating completely because it does not have any "updatepaths" to update and skips the rest of the update function. At the end of that function he in fact clears it again, most likely where he intended it to be and simply he forgot to delete it in the first one. It corrects the issue completely. I have fixed a number of issues and will pass that info to @OwnProx once I am finished with my corrections. Then he will likely release it again. But for me, there is no point in just band-aiding one error just to find another one and release it again and again.

 

[Joker]

My post had absolutely nothing to do with gimmi gimmi gimmi or if the Dev has real life issues.

it's the complete lack of communication from the Dev here about issues with something they released. There was frequent communication at first and then absolutely nothing. I'm not using this solution at this time honestly because it's broken and chose to just use some powershell scripts to automate things.

I hope the Dev does communicate their intentions for the manager because it did seem as though it was off to a good start.

 

[baylf2000]

For me it isnt the fact it isnt detecting an update. It in fact knows there an update but skips the process because he clears the "UpdatePaths" using "UpdatePaths.Clear();" in the GetCurrentBuildID function before he uses it in the next function where it skips updating completely because it does not have any "updatepaths" to update and skips the rest of the update function. At the end of that function he in fact clears it again, most likely where he intended it to be and simply he forgot to delete it in the first one. It corrects the issue completely. I have fixed a number of issues and will pass that info to @OwnProx once I am finished with my corrections. Then he will likely release it again. But for me, there is no point in just band-aiding one error just to find another one and release it again and again.

Regardless, the fact remains that the method of detecting an update by using steamcmd is definitely broken. It does not detect an update when it is released. I have confirmed this on multiple platforms and with other developers. You can see it for yourself. As of the time I write this reply, steamcmd returns the following:

                "branches"
                {
                        "public"
                        {
                                "buildid"               "3497453"
                                "timeupdated"           "1548325826"
                        }
                }

And yet the current version is definitely 3503307, as returned by SteamBD. I'm not saying this will be the situation forever, but right now THAT is why the app is not updating. When I replace the function that uses steamcmd to get the available buildid with another function that uses steamdb, the rest of the process functions perfectly, without any changes you mention above.

So this is no fault of @OwnProx , but a bug with steamcmd, and it affects all the management apps as they all use the same method to detect updates. It seems to only apply to Atlas though, as the Ark apps that use the same method still work perfectly.

 

[kessef]

Regardless, the fact remains that the method of detecting an update by using steamcmd is definitely broken. It does not detect an update when it is released. I have confirmed this on multiple platforms and with other developers. You can see it for yourself. As of the time I write this reply, steamcmd returns the following:

                "branches"
                {
                        "public"
                        {
                                "buildid"               "3497453"
                                "timeupdated"           "1548325826"
                        }
                }

And yet the current version is definitely 3503307, as returned by SteamBD. I'm not saying this will be the situation forever, but right now THAT is why the app is not updating. When I replace the function that uses steamcmd to get the available buildid with another function that uses steamdb, the rest of the process functions perfectly, without any changes you mention above.

So this is no fault of @OwnProx , but a bug with steamcmd, and it affects all the management apps as they all use the same method to detect updates. It seems to only apply to Atlas though, as the Ark apps that use the same method still work perfectly.

If you have found a solution, could you give us the executable so we can have the auto updates working? Thank you

 

[smooreace]

Regardless, the fact remains that the method of detecting an update by using steamcmd is definitely broken. It does not detect an update when it is released. I have confirmed this on multiple platforms and with other developers. You can see it for yourself. As of the time I write this reply, steamcmd returns the following:

                "branches"
                {
                        "public"
                        {
                                "buildid"               "3497453"
                                "timeupdated"           "1548325826"
                        }
                }

And yet the current version is definitely 3503307, as returned by SteamBD. I'm not saying this will be the situation forever, but right now THAT is why the app is not updating. When I replace the function that uses steamcmd to get the available buildid with another function that uses steamdb, the rest of the process functions perfectly, without any changes you mention above.

So this is no fault of @OwnProx , but a bug with steamcmd, and it affects all the management apps as they all use the same method to detect updates. It seems to only apply to Atlas though, as the Ark apps that use the same method still work perfectly.

The problem with all of that, and I can't explain why so don't ask, is that when you manually run a steamcmd update it works flawlessly. So what's the difference in how doing it through the server manager and doing it manually?