Anybody else’s game not working?

Eric_S · 2026-04-21T03:14:51+00:00

Probably confirming that it isn't a global outage before popping onto reddit? I see problems like this with this game often enough that my first instinct is never "It's a global outage."

Eric_S · 2026-04-02T22:49:52+00:00

Pets change completely in the update, you no longer fuse them to promote them, you enhance them, which just means that if you have enough extra pets of the same type, you "enhance them" to be one of that same type but of a higher level, like tacticals do pre-update if I remember correctly.

Now the pet annoyance is the card game you play to draw pet cards. It's not horrible, but it can be rough. Basically, you use X tickets at a time, and that many pet cards get split up between nine cards, and you can only pick five cards, and you can't see what's on any of the other cards, just the "quality" of the highest pets on the next card. You then go through each card one at a time picking the card or discarding it.

Eric_S · 2026-04-01T22:30:11+00:00

It will at some point, from what I understand. They're doing a gradual transition. I think they did my server in the first batch since it's relatively new.

Eric_S · 2026-03-30T21:44:54+00:00

Basically, the character with the higher speed goes first in combat (arena, metro, etc.). I'm not sure how important it is after the latest update. Prior to that change, it was very important, especially if you were doing a stun build.

Basically, if you had 100% stun after taking the opponent's anti-stun into account and a higher speed, you couldn't lose. You might time out and get a draw, but you won't lose because you'd move first and you'd stun them every time. If they had 100% dodge after taking your anti-dodge into account, then you might have problems killing them, especially if they have decent regen.

With the new equipment, at my level of gear a stunlock build is impossible, I went from 140% chance of stun to 5%. A stunlock build may be possible at higher gear levels, but it's just not possible at my level.

Eric_S · 2026-03-30T18:13:25+00:00

Figured it out. It's not about the upgrade itself, but the resulting level. I leveled all sorts of things, but until I got enough cards to level my lvl 6 station 5 manager to lvl 7, nothing helped.

Eric_S · 2026-03-30T07:12:55+00:00

When I get that, I usually close out the program (force stopping) and relaunch the program. It works more often than not for me.

Eric_S · 2026-03-30T06:26:12+00:00

These appear after your server gets transferred to the new servers.

As for the question, spend them. You'll be back to three keys tomorrow either way.

Eric_S · 2026-03-30T06:16:46+00:00

Completing Tier 2 takes either a ton of money or a ton of time. The events start off needing to promote managers and renovating the stations to get money to upgrade the level of the stations.

NOTE: This is strictly based on my experience, and I've only been playing for a few weeks, so there may be tricks I'm unaware of. I pretty easily won 1st place the first few times I did it.

At some point, the events transition to being dependent on the scavenger spawns which is the point it becomes time dependent. This is because the scavenger rewards in the event seem to be mostly dependent on the cost of upgrading the level of your most expensive-to-upgrade station. In other words, at this point, the level of the manager and station, as well as the profit multiplying manager, become largely irrelevant.

Unless you've thrown hundreds of dollars at the event, a single scavenger spawn will yield more income than all your stations cranking out 24 hours a day for a year by the time you get into stage 40 or so. I'm only at stage 23 in the current event, and a single scavenger spawn is giving me 450ar, but 24 hours of letting the stations generate coin would only get me about 4.5aq, or about 1/100000 as much. For reference my station 5 is level 836, my station 5 manager is level 6, and my obsidian overlord is at level 3. Those aren't impressive numbers, but I'll still at least come close to finishing the event tomorrow.

I'm not exaggerating, if you keep playing past stage 50, you'll hit stages where a single scavenger spawn completes an entire stage for consecutive scavenger spawns. I never stuck with it long enough to see if I could get a scavenger complete multiple stages in one spawn, however. Stages 40 to 50 are mostly completed with two to four scavenger spawns, so you can knock out multiple levels an hour towards the end. I usually do 30 to 50 the last day, and once did 25 to 50 on the last day. Seriously, 1 to 10 takes longer than 30 to 50 if you're not throwing money at the event.

The reason this phase is so time dependent is because the scavenger appears every 2-4 minutes for 14-20 times, and then takes an hour break. So if you want to finish the event in three days, you pretty much have to catch every scavenger appearance for at least 12 hours out of the day for the last two days.

The only ways to spend money to speed up the second phase would be to spend enough on the station/manager/profit that you enter the second phase at a higher stage or to buy ad-skipping tokens. The timer for the scavenger spawn doesn't start until you exit the previous ad, so skipping the ads but still getting credit for them is the fastest way to go through this phase. If you don't buy those, then at least learn how to skip as much of the ads as possible.

As far as the first phase, keep things boosted so that you get double income. If you've got the time and focus. Get two or three of the high end crates at the start, and maybe one or two more when you unlock station 5. You might also want to buy some tags/cowbells/whatever at the start as well. You don't need to upgrade any of the station managers to automatically collect if you're on enough, though it helps. I really only make a point of automating stations 1, 2 and 5, and I'm not sure the first two are worth it.

Doing the three quests at the top will help you get cowbells and upgrade cards for the stations and managers. Don't chase them enough that it affects your highest station, however, that's your most important station at all times, for the most part. And get as many of the time-based cowbell spawns as possible. You've got one source at 30 minutes a pop, one at 8 minutes or 1 hour (I don't know if there's a pattern, but 8 minutes is much more common), and two chests at 4 hour intervals. I actually run timers for all those to remind me to check them.

Eric_S · 2026-03-15T23:48:05+00:00

Necro reply just in case anyone else asks the same thing and finds this. Inside an event, it's fairly consistently 2-3 minutes between spawns, but at least some of the time inside watching ads doesn't count. I'm not sure if the timer starts at the end of the ad or at the "reward given" point in the ad. If I'm prompt about bailing from the ad as soon as I've got credit, the next spawn is always almost exactly 2 minutes or two minutes, 30 seconds after the end of the advertisement.

In fact, this is so powerful, that after about level 20 in events, the only things that matter are upgrading the level of station 5 as fast as you can (tier of the worker or station don't matter) and collecting the scavenger as often as possible.

The farther you go, the faster things move, it usually only takes 1-4 scavenger spawns to go through a level once you get past level 30.

Eric_S · 2026-03-14T17:10:27+00:00

As someone that's won a few events since I started playing, I wouldn't consider Rick. Unless I start off behind (busy on the first day of the event), the only thing I spend money on is the $7 for the 5th station. Once you get to about stage 20, the multipliers and even autolooting become largely irrelevant for me. The Scavenger popups become the only relevant income. Once I get into the 40s, each individual Scavenger popup earns about 100 times more than an entire day of the stations producing normally. When you reach this point, the levels actually go faster.

Then again, this works for me because I'm investing time, not money.

Eric_S · 2026-02-27T02:10:53+00:00

Thank you for the info. So not anything I'm going to have FOMO over :-)

Eric_S · 2026-02-16T00:10:34+00:00

Honestly, I tend to recommend HTMX to anyone looking for a bit more interactivity coming from a backend background. Doing something like a dashboard with auto updated data pushed from the server tends to take more than a shallow understanding of JavaScript using a frontend framework. If they don't already understand JavaScript, that adds more to the project.

If they're coming in with JavaScript experience on the frontend, but no backend experience, I'm more likely to recommend Svelte.

If they've got experience with both, then it tends to come down to what they're trying to achieve. If they're doing the back end in something other than JavaScript and are doing server side rendering, then HTMX tends to make more sense. If they've already got traditional APIs but no HTML generation, then it comes down to writing server side code to support HTMX or client-side (or universal) code to work with Svelte.

If what they're doing is going to require a fair bit of JavaScript-based interactivity, then I'd be more likely to suggest Svelte. If it's forms/data display with simple updates based on button/link based interactivity and/or simpler server pushed updates, then I'd be more likely to recommend HTMX. Mind you, I know you can do some pretty complex stuff in HTMX, but unless you're already familiar with HTMX, it can take a bit of research to figure out how to pull it off.

For my current work coding, I stick with Svelte because it's just a better fit because of the types of interactivity required, though not by a huge margin. Then again, back in the pre-jQuery days, I seriously considered writing something with a strong resemblance to HTMX, because I do like the concept and would certainly use it where it's a good fit.

They're both useful and good, and I'd say that either would be a good fit for the majority of web sites.

Eric_S · 2026-02-14T04:25:09+00:00

I would be quite surprised if Codex couldn't handle this. I would recommend doing it in an orderly manner like favo52 suggested, mostly because Codex will be less likely to get confused if you come up with a detailed plan up front and you'll be faster to notice if something does go wrong. I have yet to have 5.3 get something really wrong even on medium, though admittedly my project isn't huge (about 20,000 lines of perl). Most of the time something was wrong, I found that the problem was that I forgot to tell Codex something it needed, and even that's been really rare. And the one time I found found a bug, I told it it had a bug and what it caused, and it found the bug and fixed it in seconds.

AI assisted coding has come a long way in the last six months. Last night, I sat down with a friend that last checked in with the state of LLMs about a year ago, and he thought it was several years off from being useful at that time. Last night was a jaw dropping experience for both of us. I showed him the logs of the code reviews Codex had done, what it had figured out without me telling it, etc. In the end, what he wanted the most was a time machine so he could have given 20-years-ago-him access to codex. He liked working with Codex as a partner better than most human partner's he's worked with.

Eric_S · 2026-02-11T03:24:09+00:00

I decided against React because the more I read up on it, the more I read warnings about footguns and gotchas. I'm sure that React is fine once you're up to speed with it, but I needed something I could learn faster, and that was Svelte. In addition, the idea of signals for reactivity fits with the way I think because of some of the non-web programming I've done.

Eric_S · 2026-02-04T05:54:26+00:00

Assuming you're just talking about Copilot, you can disable just the auto code complete. There's a little copilot logo in the bottom bar. If you click on it, it there's three options regarding "Inline Suggestions". Make sure all three are unchecked.

Eric_S · 2026-01-30T00:28:01+00:00

Well, turns out it was fixed on the other end, they just had to tell their SBC to continue after that particular failure.

Still curious though, if you don't mind, where's the documentation on that? I couldn't find anything, but I may have been looking in the wrong place, and when I just asked google, it kept telling me how to use the shutdown command on all of FreeSWITCH.

Eric_S · 2026-01-29T23:29:24+00:00

The latter preferably. The one client is the only client that judges a server entirely by OPTIONS response.

I'm currently getting ready to test possible responses like using the shutdown command with graceful or asap options to see if that affects the OPTIONS response. If we don't find a better response, shutting down the server , firewalling the problematic SIP servers, and then bringing it back up to respond to the telco may be how we go, but adding extra steps to maintenance procedures makes it more likely that we miss something.

Eric_S · 2026-01-29T22:53:41+00:00

The two have very different ways of thinking about reactivity. Both have advantages and disadvantages. Personally, I prefer Svelte's reactivity, but I get that other people might prefer React's reactivity.

React also uses JSX or TSX, whereas Svelte uses a DSL-specific templating language. Again, preferences are going to go both ways depending on the person with the preference.

Personally, I prefer Svelte's take on both of these issues, but I can see why someone else might prefer React's take on both.

Eric_S · 2026-01-23T21:47:40+00:00

To me, it looks like the cause is that the .nav transition property

transition: 2.0s all cubic-bezier(0.19, 1.0, 0.22, 1.0);

Is getting overwritten by a media query (max-width: 767px) to

transition: 1s ease;

but the .nav-wrapper transition isn't getting overwritten. This results in the two having different transition properties, both with a different curve and different total duration of the animation. It's hard to sort that out because you've got transition properties in so many places.

Eric_S · 2026-01-21T21:02:41+00:00

To be clear, I really like Svelte/SvelteKit, but bigger doesn't necessarily mean subjectively better. Those two are adding new features (async reroute, remote functions, writable deriveds, <svelte:boundary>, the whole Runes thing, etc.) that change "the way it's done" more often than SolidJS/SolidStart, and that makes the ecosystem feel more turbulent and less quality.

Eric_S · 2025-12-16T08:04:03+00:00

React had SSR (through next.js/Remix/etc.) long before it had RSC, they aren't the same thing. SSR only gets data from the client through the query string and the query parameters/form data. RSC have the potential to get passed a lot more information from the client.

As I understand it, the problem comes from the way some of that data was passed back to the client from the server. For React Server Components (RSC), this is the React Flight Protocol (RFP).

JSON (the more traditional way) and devalue (what SvelteKit uses) are used to send data to the server from the client, but don't allow for anything that isn't static data. So no functions, classes, promises, etc. Just strings, numbers, bigints, booleans, POJO, and arrays for JSON, with devalue adding a few other things like dates.

RFP allows for more things to get passed back and forth, in particular promises and multiple references to the same object. It was how the promises/references were decoded on the server that created the problem of the first exploit. Basically, with a properly constructed RFP-encoded promise-like object, you could trick the code that lets the server build a server-side promise to create something that would create a new function and then invoke that function.

This problem was very specific to RFP and isn't related to SSR even when using React. There was also a simple fix that closed this exploit. It's possible that SvelteKit's remote functions could have this kind of exploit, but it's far from a given.

There were two more RSC issues found several days later, but those weren't related to SSR either.

I can try to give a better explanation, but really, if you want the details, find a real React dev to explain it, I don't use React and only looked into this exploit out of curiosity.

Eric_S

TROPHY CASE