関連記事

Why Singularity is NOT on a Fake Timer

Why Singularity is NOT on a Fake Timer

Background

For many years Hello Games have run community rewards. The most prominent being the Quicksilver rewards. They work by linking your efforts towards the community goal to their server. This makes the missions available, monitors our completion of any missions and adds to a global counter.

As a pacing mechanism, the speed at which things progress is set by HG manually, to make more desirable items slower or make single items in a set faster. They either do this by setting the number of required contributions or by using a contribution modifier. (I am not sure which but they would be functionally the same.)

They sometimes adjust the contribution during the progress. Usually when they have other plans, like a specific update that includes themed items. The most notorious time was during the first expedition that used a community reward, which had to have a cut-off to approximately meet a specific deadline when an interview would be published. Unfortunately this may have led to the perception we have today, where some assume this is always the case.

They will also change the overall count occasionally. If the servers get overloaded and no contributions are registered for a period then they extrapolate the progress and adjust things. If they have an update ready to roll on a specific date and the current item hasn’t quite reached the goal they will either increase the multiplier or just set it to done. They occasionally do this when they just want to speed the progress of individual parts of grouped items. This may be timer related but it has never been egregious. Just the last few percentage points to better pace when the new rewards arrive. We have also seen them just give up when things are badly bugged, and make the item available as part of a patch.

Leviathan

The second expedition to use a community counter was Leviathan, and it serves as a clear example of how it works and what happens when things go awry.

Leviathan had a four part goal. We started the expedition with C-Class modules and each goal increased these, B through S then X.

HG capped individual contributions without making that information public, this gets into data mining territory which is not really appropriate in this sub but it stands to reason HG would take action against manipulation by players to break their counters. At the time some players complained that it was obviously fake but we know exactly what happened because it was tracked and recorded.

Things began OK but something went wrong with the B-Class counter. It even began to drop. HG fixed this and just gave us the Bs and set the A counter going.

That counter went without a hitch quickly reaching the goal. As did S. This probably surprised HG because a great many users were saying they didn’t want to do that expedition. And yet it was very successful and the counters went fast.

HG clearly decided that they needed to pace out the X-Class reward they seemed to set it far too slow. We can see some evidence of a form of intervention, but notably not based on a timer artificially increasing the numbers. It was either manual or algorithmic.

In summary, first it was bugged, then it was OK for two stages, then it was obviously manipulated for the last stage.

Singularity

HG had a specific date in mind for Singularity. It was timed to coincide with the Apple developer’s conference. They needed to switch their community server over to the expedition but the QS cloak wasn’t quite finished naturally. So they appeared to increase the multiplier dramatically or reduce the number of contributions required, giving it a huge boost on the last day.

They were then free to set the counter for the expedition. If the count was fake they wouldn’t have bothered. They could just have left the cloak to finish naturally and put the next quicksilver item up. Leaving the expedition pretending to act like a second counter. This is perhaps the most compelling reason to not believe the rumours about a counter. Fake counters don’t need this much effort and wouldn’t need manipulating.

Now, perhaps predictably, given the slower pace of updates this year, the Singularity expedition has proved popular, but unfortunately it has also confused a lot of players who didn’t grasp how it worked. The upshot of this is some thought it was bugged and wondered why they couldn’t finish the expedition and some wanted to test the system and hand in several hundred seeds (even thousands) by duplication and presumably a macro.

As we learned in Leviathan, that experiment was doomed. HG know some players will try this. A thousand contributions wouldn’t move the counter significantly enough to be visible because they know it isn’t feasible and have stopped that happening. I will include the graphs from that time. It is technically a form of data mining but it is not spoiling anything so I hope it is seen as appropriate.

Leviathan Misson Progress

Conclusion

Overall this isn’t fakery, this is pragmatism and a sense of fairness. And, in the unlikely event that progress slows down enough that we look like failing the last goal, HG may aid the speed of progress. Yes, that is manipulation, but that isn’t the same as a fake timer.

Now, I can already tell by the cry of cheating by many on social media, that the received wisdom that there is a timer will probably stick for a while. It has stuck before. Any “evidence” that supports this received wisdom will be probably believed by those predisposed to. If the counter needs adjusting or we have more bugs, then it will only add to this perception.

Eventually, when the community that monitors the counters switch their systems to allow monitoring of this expedition, we will hopefully be able to see real time progress information. Then we will be able to judge what really happened. But that data is best left to the areas of the internet where it is appropriate to discuss data mining in more detail.

Suffice to say, if you are worried or concerned that HG are only pretending there is a community counter for the goals the actual evidence doesn’t support this. They have haver used timers to directly manipulate the numbers in that way, or to pretend our efforts are meaningful when they are not. They have sometime changed things for good reason but never in a way that seeks to pull the wool over our eyes. The counters are real and we are watching closely.

submitted by /u/Jkthemc
[link] [comments]

続きを読む シェア
0

There's nothing better than "permadeath" with scarce resources to make you appreciate the ...

When I first started playing a few months ago I was in normal mode and got insanely lucky. In the first
couple weeks I had an exotic land right in front of me in a space station and I had *just* enough to buy it with trade-in. The first freighter I was offered was an “S” class. And then not long after that I found a second exotic (a yellow and gold royal.) I even found a star system with three awesome planets (Bountiful, Tropical, Paradise.) For a while it was fun but got boring pretty quickly.

I kept that save but decided to start another one on permadeath with the difficulty ratcheted up a bit. MUCH harder and definitely frustrating, but a lot of fun! A lot more animals attack me on planet surfaces and pirates definitely seem more skilled in fights (a couple times I barely made it out alive after prolonged battle, when in my other save I’d dispatch them in less than a minute.)

I think I am just over 15 hours into it and still hanging in there. I have an “A” class fighter for a ship, and have not seen a single “S” class anything. I’ve only been offered one freighter so far and it was a “C.” I was in two other battles where I could have been offered a freighter but accidentally shot them while fighting the pirates and then had to deal with pirates AND sentinels with no reward for it. The struggle is real. Me in my other save: “Oh look, another exotic. I’ll add it to my collection.” Me now: “OMG is that sodium?! WOO HOO!”

submitted by /u/MashTunOfFun
[link] [comments]

続きを読む シェア
0

Big Experimental Branch patch - June 15 2023

Big patch on the Experimental branch today, these fixes should go public soon.

Including

  • Fixed an issue that could prevent the Singularity expedition from converting into a Normal mode save after it was completed.
  • Fixed an issue that caused the ship at the start of the Singularity expedition to be missing its Vesper Sail.
  • Fixed an issue that caused Sentinel Interceptor ships to be worth 10x as much as other ships when salvaging.

Full List:

https://steamcommunity.com/app/275850/discussions/0/6516193260167070838/

Experimental Branch 15/06

  • Players are now able to rebind movement to the cursor keys without that automatically resulting in them moving around while navigating the quick menu.

  • Fixed an issue that prevented the cursor from rendering while re-binding controls in the Game Mode options screen.

  • Fixed an issue that caused a number of options to be missing from the options menu, or some options to appear when they should not.

  • Fixed an issue that caused the Terrain Manipulator menus to scroll the wrong way in VR.

  • Fixed a rare issue that could leave player-owned Interceptor ships without any installed technology.

  • Fixed an issue that could cause the starship’s landing gear to be incorrectly raised after save/loading within a landed ship.

  • Fixed an issue that caused first-person cockpit exit animations to fail to play.

  • Fixed an issue that could prevent the Singularity expedition from converting into a Normal mode save after it was completed.

  • Fixed an issue that caused the ship at the start of the Singularity expedition to be missing its Vesper Sail.

  • Fixed an issue that caused incorrect collision on outpost landing pads.

  • Fixed an issue that could cause players to be ejected from the Multi-Tool comparison screen when attempting to pin repair instructions for a Multi-Tool they do not yet own.

  • Fixed a rare issue that could cause players to be erroneously told their inventory was full when claiming the reward for “Wayfarer” milestone.

  • Fixed a rare issue that could cause the galaxy map Mission Path to point to the wrong destination system.

  • Fixed an issue that prevented starship distress beacons from animating correctly.

  • Fixed an issue that could cause Multi-Tools belonging to other players to become attached to NPCs.

  • Fixed an issue that could result in players becoming permanently stuck to the chair in the Guild Envoy’s area of the Space Station.

  • Fixed an issue that caused Sentinel Interceptor ships to be worth 10x as much as other ships when salvaging.

  • Fixed an issue that allowed too many Communication Stations to spawn on expedition planets.

  • Fixed a rare issue that could cause the current expedition to end early.

  • Fixed a Mac-only issue that caused large bases to be loaded very slowly.

  • Fixed an issue that prevented some freighter engines from being correctly recoloured when choosing a new engine trail.

  • Fixed an issue that could cause the depth of field effect to be applied far too strongly on some platforms.

  • Fixed an issue that could cause black speckles to flicker across the screen during interactions that made use of the depth of field effect.

  • Fixed a graphical glitch that could occur in the Atlas’ particle effects when playing on Switch.

  • Fixed an issue that caused eyeballs to be positioned incorrectly within a specific Traveller-style head in the Appearance Modifier.

  • Fixed a graphical issue that could cause the player to briefly appear while teleporting.

  • Introduced a rendering optimisation for VR.

  • Fixed an issue that could allow too many creatures to spawn when playing in multiplayer.

  • Introduced a memory optimisation related to planetary creatures.

  • Fixed a crash related to synchronising freighters in multiplayer.

  • Fixed a crash related to the Multi-Tool.

  • Fixed a hang related to reloading missions.

  • Fixed a crash related to base part rendering.

  • Fixed a rare crash related to the mission log.

  • Fixed a rare crash that could occur in VR.

  • Fixed a PlayStation 4 crash related to reporting bases.

submitted by /u/_No_Mans_Skywalker_
[link] [comments]

続きを読む シェア
0

Community

Weekly Bug Report Thread

This thread is followed by Hello Games. Please add your bug reports to this thread. You can also report bugs to Hello Games at the Zendesk. Before reporting a bug be sure you have installed the latest Patch or Hot Fix, information is located on this page. Please include platform and version.

This weekly thread is to help keep bug reports manageable. It is a scheduled weekly thread and not related to any specific release. You do not have to repost bugs to this post if you have already reported them on a previous post.

If you’re requested to send your save file to Hello Games see this post

submitted by /u/AutoModerator
[link] [comments]

続きを読む シェア
0

Can I create a custom squadron from ships I would be scrapping otherwise?

So here’s what I was thinking. You can hire an NPC to your squadron from any space station for example, right? Now what happens if BEFORE hiring them I buy their ship by swapping it with one of my ships that I would be scrapping otherwise? Will I get THAT ship to join my squadron?

Obviously it depends on the pilot too how well they will do in a fight, but this way I could have a squadron made up of Living Ships or fully equipped Sentinel Interceptors, right? Or, in theory I can claim the Starborn Runner as many times as I want if I’ve finished the expedition, can I just keep selling a Starborn Runner by swapping with them AND hire said pilot equipped with the Starborn Runner now? Can I have a full squadron of them?

I’ll test this out soon with a sentinel that I’d scrap otherwise and get back to you, but if this works I think it is huge, so much potential to create an amazing fight squadron this way!

submitted by /u/Sn00PiG
[link] [comments]

続きを読む シェア
0

Popular Posts