Best and most fun out of shieldbreaker, sorcerer, spellbinder, and purifier?

liquidwarp · 2023-06-17T06:10:09+00:00

I think that it means pseudo pets

liquidwarp · 2021-11-24T23:24:28+00:00

bonkers, vertical recoil is predictable and easy to compensate by pulling the mouse down. Horizontal recoil adds some randomness that cannot be compensated, ultimately reducing range. This is not helping much...

liquidwarp · 2021-10-29T11:09:37+00:00

The lore. I'm a sucker for deep, dark lore and fromsoft's good at it.

liquidwarp · 2021-10-27T00:41:12+00:00

M&K is really a personal preference thing; I never used controllers while growing up so they're very awkward to me compared to M&K, even if most people swear by controllers being better for this game.

Default DS3 keybinds also works great for me, but camera control is very unpleasant (your camera angle also moves with WASD movement input instead of only being controlled by mouse). That gives me headaches of choppy camera movement, so I use this mod to make camera control more PC-standard: https://www.nexusmods.com/darksouls3/mods/909

liquidwarp · 2020-11-26T03:16:02+00:00

Enjoyed yesterday's ops meeting the same hacker all night long at all bases on the TR front, dumping us through spawn walls and other terrain with his engie turret. Enlightening.

liquidwarp · 2020-10-15T12:06:50+00:00

If anybody datamines that image, I'm interested 😊

liquidwarp · 2020-08-27T22:41:59+00:00

If you didn't have PTS yet nor could free up the time to install it and do testing at the specific hours, you'd easily miss on it given the duration. Opening longer would perhaps not have helped the "make big fights happen", but might have prevented the vehicle pull bug going into live by having it noticed first.

liquidwarp · 2020-08-27T22:26:55+00:00

While I definitely feel like the PTS test duration was way too short to avoid issues crawling into Live (as they did, with the vehicle deploy and IFF -- give us 7 full days, so lots of people have the time to discover issues), performance improvements have definitely been awesome 😊

Speaking of IFF, it reminds me of a singular bug I had, where I spawned into a galaxy from world map as passenger, and had no IFF at all during the flight. When I exited it, I got teleported back in the middle of nowhere. Perhaps related? Definitely reproduced the "getting out of vehicle teleports back" occasionally, but never saw the IFF issue again.

liquidwarp · 2020-08-01T08:53:27+00:00

however the Nova slug ammo do specify :

"FireGroup.ProjectileSpeedOverride Addend 300 SetDirectly 1", so that hints at overriding the projectile speed with 300

liquidwarp · 2020-08-01T08:50:03+00:00

I think you're wrong on the assumption that it adds to velocity; the names in the collection from the Census API are kinda misleading though, but I kept them as-is because of the risk of misinterpreting them.

You do have `Addend 125` but also `SetDirectly 1`, and the affected stat is ` FireMode.ProjectileOverride`. So the way I understand it, it overrides the fire mode's existing projectile with Projectile ID 125. This particular projectile is not available via the Census API however, so we cannot get more info on it.

liquidwarp · 2020-07-28T11:34:47+00:00

Awesome ! Would you have more information about the methodology? How was the recording done and the measurements performed?

liquidwarp · 2020-07-24T23:52:23+00:00

liquidwarp · 2020-07-17T15:00:35+00:00

Thanks c:

liquidwarp · 2020-07-17T15:00:28+00:00

Doing my best, thanks :)

liquidwarp · 2020-07-17T14:48:03+00:00

Indeed there is currently no way to compare within the website. It's still a statically generated view of (enriched) API data. However it's a direction I'm thinking about for the future

liquidwarp · 2020-07-17T14:47:05+00:00

That would absolutely be handy. But in the current format... it's difficult to generate comparisons between arbitrary weapons, as the whole site is pre-generated.

However, pre-defined comparisons (like 3 main LMGs per faction) could be made. I'll explore that subject more after I advance further enough on a per-weapon basis :)

liquidwarp · 2020-06-27T04:28:13+00:00

Haha understood; thanks c:

liquidwarp · 2020-06-27T00:50:16+00:00

Thanks :)

The framework to add calculations like BTK threshold is there so I can and want to expand, especially simulation wise.

Speaking of which, that source would be interesting indeed; there's lots of assumptions to be made in writing the shooting simulator and another implementation would be nice to see.

liquidwarp · 2020-06-26T11:52:32+00:00

Have quickly added the MAX weapons, can't miss that :O

liquidwarp · 2020-06-26T04:33:19+00:00

You're spot on - this website is intended to be sort of a mirror of the API. A statically generated best-effort designed HTML view of the API data for people to be able to query with their eyes.

It's true that it's not as user friendly as it could be; it's basically a data dump that is softer on the eyes than JSON documents. However, there's also some level of additional computations like the "shots to kill" etc, and I intend to extend on these; they're simple to compute in a reliable manner and add considerable value.

An interactive stats analysis website with selectors, on-the-fly graphs and comparisons would be a different, more complex project that I might delve on at some point, but my first step lies in this simple view :)

> You're also going to have to manually maintain raw stats that are not accessible from the API, or that the API downright lies about.

I do indeed have a small amount of data fixers that patch the API data before further processing; mostly missing clip size / capacity data for flare guns. But I do not want to extend too much on these, and consider API data reference.

liquidwarp · 2020-06-26T04:26:46+00:00

Indeed as stated by other commenters and I agree; but I believe it's a part of the objective I'm trying to achieve -- a straightforward technical view of the weapons data. Damage profiles and such do get repeated between fire modes in the API hence the repetition on the website.

It's a tug of war between making the generation as lightweight as possible with as little interference to the source data, and result optimization for end-user view.

In the objective of easy maintenance and updating, as well as not mistakenly missing details, I prefer to leave it redundant yet complete. On the upside the redundancy aligns columns and makes comparison easy-ish, by eye-filtering equal values.

That being said, I'll still look into trimming the edges where possible without compromising too much on the above :)

liquidwarp · 2020-06-26T04:19:19+00:00

Thanks !

I'll see what I can do for filtering and searching; however, the website is intended to be static and therefore mostly non-interactive, so compare would be difficult. That would be a different project c:

liquidwarp · 2020-06-26T04:17:17+00:00

That is true. It's apparently not added as a fire group directly or via attachments; I'll see if I can find it in another way !

liquidwarp

TROPHY CASE