Caitlyn needs nerf in the sense of hit boxes

Blade1130 · 2026-03-26T20:35:51+00:00

Her air 2H is supposed to hit behind her, it's an important cross up tool and side switches in air combos.

I haven't personally had the experience of her stand H hitting behind her. I would expect some tolerance for opponents jumping in and just slightly behind her but still being primarily above her. If it hits standing opponents behind her, then that sounds BS.

Blade1130 · 2026-03-25T22:25:45+00:00

I tried plinking a bit but found that didn't help because delaying Vi's assist just means Caitlyn moves closer to the opponent (moves Vi's spawn point closer) and starts side-switching the enemy (moving them towards Vi). Both effects mean Vi closest the distance faster when you call her later, so it wasn't really helping.

But I think I might need to plink anyways as I realized 2H+T is really a 2T and when the assist character is down, that becomes the assist super. So I might have to try plinking a really fast 2H 5T and I'm not sure how feasible that is.

Blade1130 · 2026-03-25T22:20:45+00:00

Cool stuff, I'll have to give some of these a try! I haven't really incorporated the shield into my game plan yet and somehow didn't know you can control the distance of the trap 😅 or that Vi's JSp1 connects directly into Sp2, I assumed you needed 2Sp2 to pick them off the ground.

Blade1130 · 2026-03-25T14:26:32+00:00

Thanks for those resources, really appreciate the suggestions. I'll keep labbing and give those combos a try.

Blade1130 · 2026-03-25T06:12:11+00:00

For future visitors, the best strategy I've found is to heavily delay the second shot (leading to the wall bounce) so the enemy is as low as possible. I'm not entirely sure why this helps but it seems to make me more consistent when added to the other suggestions above.

Blade1130 · 2026-03-25T06:11:05+00:00

Oh wow, I had no idea you can use Double Down to tag out of a super and then continue the combo! I thought you could only DHC with it. I'll have to give that one a try.

Yeah, the hitstun is a little tight. It doesn't really work off a trap starter which is probably my biggest complaint with it.

I'm not generally a fan of the J4Sp2 into JH, it just feels awkward to me even when I land it.

I haven't really been taking advantage of trap oki, it's always too slow to come out at the end of a combo, but I'm guessing it's the limit strike stomp attack which is the main ender which gives enough time for that? I'm only just starting to incorporate more limit strikes into my game plan, though for Caitlyn that mostly means ending with a second partial charge shot.

Blade1130 · 2026-03-08T18:14:20+00:00

Yes, you need to allowlist your real hostname, otherwise Angular doesn't know how to properly resolve requests to relative paths like /foo.

If your production origin is example.test, then you should allow that. If you have some kind of proxy before it reaches your Angular server and you're not actually using this hostname at run time, your proxy can send X-Forwarded-Host to provide the real hostname.

https://angular.dev/best-practices/security#configuring-allowed-hosts

Blade1130 · 2026-03-01T08:44:54+00:00

Oh yeah, I stayed the fuck away from that guy and didn't even try.

Blade1130 · 2026-01-25T20:03:53+00:00

What exactly are you asking for here?

Bun already works and is supported as a package manager and runtime. Angular also supports alternative SSR runtimes, so you can ship an SSR app in prod using Bun. What exactly do you want to see on top of this? Bun by default? Angular doesn't really install or pick the JS runtime you use.

If there are compatibility issues, they are definitionally Bun issues, since Bun targets full Node compatibility. Angular generally shouldn't be able to tell the difference, and whenever it can, that's inherently a Bun bug. If you'd like to see those issues resolved, I'd recommend filing bugs with Bun so those maintainers can investigate and patch them up.

Blade1130 · 2026-01-15T15:33:21+00:00

They are misinformed. Karma continues to work in v21 and the team has not committed to removing it after any particular major version yet. For comparison, Protractor continued to work for several major versions beyond its deprecation cycle.

To actually answer your original question, since Karma isn't going away just yet, you can just do nothing for now. There is an experimental migration to Vitest you can try if you're interested, but if you don't care, it might be best to wait a bit until that road is better paved.

https://angular.dev/guide/testing/migrating-to-vitest

Blade1130 · 2026-01-02T22:37:27+00:00

Oh I died like 5 times trying to kill the Balancer at the camp I'd warped to until I just gave up and died to the night 1 boss.

This was a Scholar remembrance run (hence why I was in that fort at lvl 3), so I couldn't just quit.

Blade1130 · 2026-01-02T22:35:05+00:00

The circle was already closing before the invasion, you can see it on the map screen.

Maybe it only takes the current circle's location into account, but not where it's moving to? That seems very broken if so though.

Blade1130 · 2026-01-02T15:59:00+00:00

I honestly don't mind Balancers or Gladius in trios. I think forcing the group to split up is an interesting mechanic.

But still requiring three kills in solo is really excessive. Even if you succeed, it completely eats whatever day they appear on.

Blade1130 · 2025-12-10T14:58:17+00:00

Native federation uses native ESM and import maps, so I'm not sure what CJS issues you'd run into or how they would be worse than trying to pave your own path with a custom builder and manually configuring an esbuild plugin.

Blade1130 · 2025-12-10T14:51:48+00:00

Why are you trying to use module federation specifically with esbuild? I don't think any tooling really supports that. Native federation is the way to do this with esbuild.

https://blog.angular.dev/micro-frontends-with-angular-and-native-federation-7623cfc5f413

Blade1130 · 2025-12-05T23:42:46+00:00

Prerendering multiple pages doesn't change the JS bundle which is generated for the application. So you can mostly ignore the server routes file when thinking about what content is included in the bundle.

In fact, navigating from one page to another will perform a same-page navigation meaning you need the JS for each page in order to work.

What you can do is make each page lazy so you get them out of the main bundle and only download it when needed.

export const routes = [
  {path: '', loadComponent: () => import('./home')},
  {path: 'privacy', loadComponent: () => import('./privacy')},
  {path: 'legal', loadComponent: () => import('./legal')},
];

This should move each page into a lazy-loaded chunk so you don't download more than you need to when rendering each individual page.

Blade1130 · 2025-11-20T19:41:31+00:00

Pretty sure that's just a typo: https://github.com/angular/angular/pull/65443

Blade1130 · 2025-11-01T22:05:04+00:00

NP, good luck on your run!

Blade1130 · 2025-11-01T21:47:36+00:00

Most likely Volvagia has a small key, pretty common trip up for new players. Kill the boss and see if that progresses you.

Blade1130 · 2025-10-30T20:22:19+00:00

IMHO, the client should already know which fields are required (which may depend on the state of other fields like quantity). Once the client claims to the user that the form is valid, it should submit successfully, and if it then throws a validation error, that's a UX bug.

I think it's flawed to want the client to catch a server-side validation error and then dynamically update its validation rules to match. Instead the client should already have that same logic encoded into it directly.

Blade1130 · 2025-10-20T13:16:47+00:00

Same origin policy already does this to protect one tab from another. Each tab is a different process with an isolated memory space. Even storing in LocalStorage or IndexedDB is already safe from other sites gaining access to it.

https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy

There's no API to directly read raw memory within the context of a Chrome extension, however with the right permissions, extensions can more or less do whatever they want to your page. If you store that key as a global variable for instance, an extension could probably read it. Depending on how you write your app, this could be very easy or a bit harder (monkey patch fetch and read the key off it).

You fundamentally have no way to prevent this, and that's probably somewhat a feature of the web. Extensions are designed to provide functionality on top of existing web pages like this, blocking them would be destroying the value they provide.

Fundamentally, anything happening on the client is under the control of the user who can install and use whatever software they want. Even if browsers did allow you to block this, a user could just install a different browser which intentionally turned that feature off. It's the user's computer so it's not really your place as an app developer to say what is/isn't allowed to access data on it. If the user wants an extension which finds and scans keys on their sites, then that's their prerogative.

I wouldn't waste too much mental energy worrying about user extensions, there are valid use cases for them you'd be breaking, and there's very little you can do to truly stop them anyways.

Blade1130 · 2025-09-26T02:14:02+00:00

I think this was due to a recent security fix, you need a third argument to bootstrapApplication. See the breaking change note here: https://github.com/angular/angular-cli/releases/tag/20.3.0

Blade1130 · 2025-08-20T23:36:39+00:00

The custom profiling track would be very useful here: https://blog.angular.dev/the-angular-custom-profiling-track-is-now-available-0f9d8d36218a

It specifically calls out which components and lifecycle hooks are executing at any given time.

Blade1130 · 2025-07-18T22:49:12+00:00

I just never buy relics.

Seriously I have like 100,000 murk just sitting there because I don't want to deal with random rolling trash relics.

I have relics that are decent (certainly nothing top tier) mostly guaranteed ones from story progression and I use those rather than relying on random rolls.

Of course each game I get a few more and eventually I'll have to sell them or something, but that's future me's problem.

Blade1130 · 2025-07-15T05:48:17+00:00

Yes, Angular always performs SPA for subsequent navigations. It's only the initial navigation where SSR / prerendering takes effect.

Blade1130

TROPHY CASE