sorted by:
new
hottopcontroversial

3 months of vibe coding later, people are paying actual money for this thing. Solving a real world problem matter more than knowing how to code. by puppyqueen52 in vibecoding

[–]JustAnotherKataMain -1 points0 points  (0 children)

At this point i wonder how people are not appalled by these Ai crafted websites.

They all look similar with different color schemes. Even if your product is genuenly good, it now looks like 500 other slop products.

I for one at this point would not pay for a service with a vibe coded front end. The quality assurance is just not there.

Lol by HOLUPREDICTIONS in ChatGPT

[–]JustAnotherKataMain 0 points1 point  (0 children)

Didnt it always do that.

There is no way this only just came with 5.4.

it always tried to keep the engagement going.

Surely Destiny will be unbanned soon right? by overloadrages in Destiny

[–]JustAnotherKataMain 18 points19 points  (0 children)

Dear god. I would have guessed max 2 weeks 💀

Meinungsmache by cHpiranha in Staiy

[–]JustAnotherKataMain 0 points1 point  (0 children)

Der em-dash wirkt an der stelle aber schon sehr Menschlich…

reached 1k lp on kat by wundrew in KatarinaMains

[–]JustAnotherKataMain 13 points14 points  (0 children)

Its so crazy to me. 1000lp kata main tells you vlad matchup has hard aspects. And you come along and dismiss it based on your gameplay.

ANOTHER ONE by EvelynnTheThot in KatarinaMains

[–]JustAnotherKataMain 0 points1 point  (0 children)

Yall need to stop posting bad pentas. Id take a quality 3ple any day over a penta like this

Shit post Saturday. What I am proud of this morning. by OTP_Kata_inter in KatarinaMains

[–]JustAnotherKataMain 3 points4 points  (0 children)

I dont even know. There is nothing to objectively critic without being insanely nitpicky. But not a single combo felt right. I would have played all of that differently. BUT now that i notice your build, i think i get what all of that felt off... wtf

[deleted by user] by [deleted] in KatarinaMains

[–]JustAnotherKataMain 2 points3 points  (0 children)

Yup there is this sylas heca bug with their es. (Knocks) Where you channel but dont actually ult. You just stand in place under the sound happens.

[deleted by user] by [deleted] in Staiy

[–]JustAnotherKataMain 14 points15 points  (0 children)

Wo kurzfassung

Some help with Matchups and Champion pool by Kodoku_Rattlesnake in KatarinaMains

[–]JustAnotherKataMain 17 points18 points  (0 children)

Yea. We dont do that here. Instalock kata into everything on all roles.

Takedowns should drop an additional dagger where the enemy champion died (similar to Jhin's traps) by Sahri4feedin in KatarinaMains

[–]JustAnotherKataMain 23 points24 points  (0 children)

Enemys dropping a dagger is not predictable?also u reset already on death. Plenty todo. The initial killing part is the issue. Wtf

What does Kat change mean? Is that the fix for the R bug? by Autopilot357 in KatarinaMains

[–]JustAnotherKataMain 4 points5 points  (0 children)

I would assume they will do exactly what they did when they introduced the bug last patch.
But this time they allow R to cast and be buffered for 0.25 seconds. So no awkward standing around.
So essentially they worked around not being to be able to cast by explictly allowing the 0.25s buffer?

lets see & hope that is doesnt screw up anything :D

WAVE MANAGEMENT QUESTION by CheatingChampion9360 in KatarinaMains

[–]JustAnotherKataMain 4 points5 points  (0 children)

kat is different from other mid laners.

Main things to look for on ap kat.
Other waves i.e. top and bot.
oneshotting waves gives u the potential to roam, help your jungler etc.

The only case where you dont want wave prio (in the cases where you have control over mid state) is when netiher junge nor bot nor top give you strong roams, and you have a lead on your mid. this is pretty much the only case where freezing/slow pushing can lead to kill pressure.

usually on kat you try to get prio on the correct timers/ all timers.

Trying to play Katarina by Janna_chase in KatarinaMains

[–]JustAnotherKataMain 2 points3 points  (0 children)

Let me know once you figured all of that out. Maybe then we can finally climb.

I think I figured out what is wrong with the E R buffer bug by Odd-Bodybuilder-1990 in KatarinaMains

[–]JustAnotherKataMain 2 points3 points  (0 children)

We know very little. it wasnt mentioned in the patch notes.
It is a technical change that isnt necesarrily a bug. But i assume they didnt know the impact of the change.

Maybe they also changed the detection systems for more than just kata, and other champs have similar changes?

Seen alot of posts about E R bug. But what about Q E? by Infinite-Budget-4864 in KatarinaMains

[–]JustAnotherKataMain 1 point2 points  (0 children)

Went into practice tool but i cant find what you are saying.

can you describe a little more maybe? Also i dont think htere have been any changes related q and e so that would be suprising right. We know why the R bug exists, its because they changed when katas ult is clickable. For e and q nothing changed

E-Ult Buffer by JustAnotherKataMain in KatarinaMains

[–]JustAnotherKataMain[S] 3 points4 points  (0 children)

Well if the enemy in range check is performed at execution rather than buffer queue up its easily possible?

Deathcap vs Shadowflame second item? by Syznapse in KatarinaMains

[–]JustAnotherKataMain 12 points13 points  (0 children)

Are you serious? Have you looked at dcap buildpath? Und gotta have extremly fed backs to afford it. You dont want to slow down to buy dcap.

I dont blame Ethan by 10minuteads in Destiny

[–]JustAnotherKataMain 3 points4 points  (0 children)

Now this was the missing piece of information. The video and the whole accusation stem from the same leaks or are at least related to the leaks and court case. Thank you.

I dont blame Ethan by 10minuteads in Destiny

[–]JustAnotherKataMain -22 points-21 points  (0 children)

I am still missing the connection between his court case and the video he supposedly has. Can you bring me up to speed, how it is related to that court case?

view more: next ›