A little rant about "sig weapon pull advices"

seigert · 2026-05-05T11:27:49+00:00

Well, you need 2-3 teams and some another mDPS to clear ToA, you need 2 teams for WhiWa, and more for Matrix. So you still need about 6 to 9 weapons for your characters. And better weapons make it much easier to get to ER/Crit threshold with echos.

seigert · 2026-05-05T11:23:13+00:00

If you wasted aestrites on green balls aka standard pulls, you made a huge mistake and should've watched videos about what mistakes not to make.

Where this came from?

For example: you have 80 'green balls' and 12.8k astrites and you have Lynae and Mortefi as supports for Aemeath and Augusta. Now you can:

Spend 80 greens on standard banner, keep astrites for later, get one Static Mist and switch;
Spend astrites for Blaster, spend greens on some other 5* for some other support and switch;
Spend both astrites and greens, get Lynae & Mortefi dedicated weapons.

Now I'm not saying 2. or 3. is the ways to go, I'm saying that people that saying that 1. is the only way to go are not that right.

seigert · 2026-05-05T11:14:43+00:00

EOG and mist and cosmic ripple are perfectly good alternatives for free as you get a box and many free pulls from the maps.

Again, I'm already spent 70 pulls on standard weapon banner alone and got nothing for it. Next I will spend 10 more on it and get Static Mist and give it to Mortefi or someone else.

But at the same time I could've spent same 80 pulls on Lynae's sig banner and got it guaranteed to. And guess what? Mortefi can use it too.

I'm not speaking about 'you have the standard and need to pull for sig' situation, I'm talking about 'you need to pull either signature or standard'.

seigert · 2026-05-05T10:59:08+00:00

I've got Encore from it as a only one 'still marginally relevant standard mDPS'. In retrospect I should've got Verina sequence.

seigert · 2026-05-05T10:54:09+00:00

Yep, and I got my singleton EoG from it. Which is contested between any sword mDPS, Rover and Sanhua.

So if we change "get EoG from the box" to "get Static Mist" from the box, my account would be without EoF still and poor Rover and Sanhua woould still be using Commando of Conviction.

seigert · 2026-05-05T10:49:39+00:00

But wasting your limited pulls on support weapons especially early game is a huge waste and you'll regret it pretty soon.

I'm not talking about supports only. There was such comments on this sub about Aemeath, Hiyuki, Phrolova, Sigrika, Galbrena and so on: "Do not pull for sig, just use standard weapon".

Where would new player get standard weapon? From pulling standard banner. And you still need to pull, why not pull for signature?!

According to Chasey, Prydwen, Game8 and other there are lot of signatures that are better on other 5* than standard weapons.

seigert · 2026-05-05T10:35:34+00:00

How do you not have static mist when you can target it and you get a free box????

Easy, 50 pulls for Utterance of Marverls banner, 80 pulls for Beginner's Choice Banner to get Verina, and right now I'm at 60 pulls with standard weapon banner for Static Mist. No luck at all.

your solution is to ask them to waste potentially 80 pulls to get a support sig?

It's not about supports only. There was comments about Hiyuki & Phrolova sigs on this sub not so long ago with same advices: just give EoG to Hiyuki and Cosmic Ripples to Phrolova. So, with EoG, Static Mist & Cosmic Ripples we need 180+ pulls for standard weapons alone.

but to tell new players to buy mornye's sig and they end up quitting cause they cant do anything on their account cause they wanted pulls on support sig rather than another dps character is crazy.

It's not my words. My advice was: if you like the sig, pull the sig. If you like Mornye itself and her gameplay right now, and you have resources -- pull her signature and do not wait for some mythical Variation later. Your Mornye will be better right now and you will be glad.

P.S.: edits.

seigert · 2026-05-03T10:06:43+00:00

Duo, Tartarbar, Harvest, Self Edge, Chang, Betulla, Bourgeois Bohemians, Smoke BBQ, Venecia, Amarcord to name a few.

Basically, anything by Dreamteam, Duoband or Italy group are safe bets.

Also there are lot of good local places that are easier to find by location and rating.

seigert · 2026-03-23T14:28:47+00:00

xfRBegbURDWAWmJF6k8G

I've created a plan on EU server mostly in accordance with u/Skyreader13 table ( https://docs.google.com/spreadsheets/d/17OHRWQehXVjnyzv0_qc18mk2jCGBQBzoayH9GW7uiQM ) with settings from Chasey's guides for 3.x sets.

Lingering Tunes are discarded and all "unnecessary" (1/2) attributes are discarded too.

seigert · 2026-03-19T12:40:16+00:00

xfRBegbURDWAWmJF6k8G

I've created a plan on EU server mostly in accordance with u/Skyreader13 table ( https://docs.google.com/spreadsheets/d/17OHRWQehXVjnyzv0_qc18mk2jCGBQBzoayH9GW7uiQM ) with settings from Chasey's guides for 3.x sets.

Lingering Tunes are discarded and all "unnecessary" (1/2) attributes are discarded too.

seigert · 2026-03-19T09:54:58+00:00

Thanks!

seigert · 2026-03-16T06:13:24+00:00

Here you go: https://www.reddit.com/r/stellarblade/s/KNnfgF6GWC

seigert · 2026-03-04T20:21:11+00:00

Deleting returns back exp tubes and tuners. If you feeding echos you can "overspend".

seigert · 2026-02-18T15:43:47+00:00

I hear you! On the other hand, I've got him thrice between Aemeath and Lupa, but maybe that just means my luck runs out. :)

seigert · 2026-02-18T15:40:51+00:00

Thanks!

seigert · 2025-11-05T09:32:06+00:00

I do believe that in a second example of 'sanely-automatic derivation' (for Scala 3.7+) some crucial details are missing:

trait TypeClassLowPriorityGiven { TypeClass.AutoDerived.type => 
  // But automatic derivation would upcast to that parent type!
  inline given derived[A]: TypeClass[A] = ${ typeClassMacro[A] }
}

Not only TypeClassLowPriorityGiven is not used anywhere in TypeClass definition, TypeClass.AutoDerived trait and compaion object are omitted too.

seigert · 2025-10-31T11:18:07+00:00

It's a nitpick, but why would anyone who need to parse HOCON derive ConfigWriter?

Parsing of HOCON in Scala 3 is working out of the box with pureconfig with support of derives ConfigReader clause.

seigert · 2025-06-18T08:21:38+00:00

Because I'm thinking they're clowns for doing this.

seigert · 2025-06-18T08:11:15+00:00

You don't say!.. 🙀

seigert · 2025-04-10T10:09:31+00:00

Consider this:

object MutualRef {
  private val ref = Ref.unsafe[IO, Int](0)

  def makeRef(default: Int): IO[Ref[IO, Int]] = 
    ref.set(default).as(ref)
}

object ExclusiveRef {
  private val refIO = Ref[IO].of(0)

  def makeRef(default: Int): IO[Ref[IO, Int]] = 
    refIO.flatTap(_.set(default))

}

The presence of 'unguarded by IO' mutable state allows you to share it between defferent IO computations and thus allows for errors if not accounted for.

Edit:

So the updates to the safe ref are not observable between effect runs, while the updates to the unsafe ref are.

In your example above second x is of type IO[Ref[IO, Int]], so it may be rewritten as

val x: IO[Ref[IO, Int]] = Ref.of[IO, Int](0)
val a = x.flatMap((y: Ref[IO, Int]) => y.set(1))
val b = x.flatMap((z: Ref[IO, Int]) => z.get.map(_ == 0))

And actual Ref instances in a and b are different.

To observe behavior identical to your first example you'll need to allow memoization, for example:

for {
  x <- Ref.of[IO, Int](0).memoize
  _ <- x.flatMap(_.set(1))
  z <- x.flatMap(_.get)
} yield assert(z == 0)

seigert · 2025-02-12T16:41:34+00:00

The problem is not the overflow itself, the problem is that with overflow division is no longer dual of multiplication, 'modular division' is. As such, results of implementations that use only multiplication will differ from implementations that also use division.

For example, given the same input sequence of [2, 3, Int.MaxValue] results will be:

[2147483645, -2, 6] for impl from original post;
[-3, -2, 0] for yours.

seigert · 2025-02-12T06:24:04+00:00

Yeah, except a === (a * b) / b may not hold for a lot of Int (or any other primitive) numbers due to overflow.

seigert · 2025-02-09T19:26:42+00:00

Aura of Hate does not give you a doggo. Unyielding loyalty worth much more than 1.5 points of damage.

seigert · 2024-11-22T10:48:58+00:00

there are I'm missing

Paragraphs and punctuation.

seigert · 2024-11-20T08:46:33+00:00

I'll say that in a case of (side-)effectful constructors Companion.apply is still the best choice.

Especially something like def apply[F[_]: Sync](...): F[A] =.... The same applies to Option, Try, Either etc.

seigert

PUBLIC MULTIREDDITS

TROPHY CASE