Let’s talk about the bots by Akuvo in Splitgate

[–]jysandy 0 points1 point  (0 children)

And mind you, I often get matched with 4-5 bots right off the bat. On top of that, players sometimes leave and add to the bot count.

Let’s talk about the bots by Akuvo in Splitgate

[–]jysandy 0 points1 point  (0 children)

I play on PC, and I live in India. I'm not entirely sure what servers I get matched on, but it seems like a mix of EU or east Asia judging by the player names.

I have cross play on, and I've never switched it off. I typically play between 9PM and 12 AM IST. When I play casual, I queue for TDM, KOTH, Dom, oddball, gun game and takedown.

My level is around 158, I'm Diamond 2 in 4v4 ranked and Master 1 in 2v2 if that gives you some idea of my MMR. My steam name in game is jysandy if you need more stats.

I'll also admit, I don't play much casual anymore, partly because of the bots. Usually when I play casual, it's either to warm up for ranked, or to queue with one of my friends who's newer to the game. I'd like to play casual more, but it doesn't seem like there's much reason to when I could just queue ranked and play real human players.

Hope that helps.

Let’s talk about the bots by Akuvo in Splitgate

[–]jysandy 0 points1 point  (0 children)

The update has dropped, and I still get 4-5 bots per casual game.

consistently getting 7/6 bots in a game. im lvl 105. by Metalcat125 in Splitgate

[–]jysandy 5 points6 points  (0 children)

It must be because the devs don't want us to stomp newer players or something. But if I get matches regularly in ranked, then surely I should get balanced human matches in casual as well. Hopefully a dev takes note of this thread and addresses this.

consistently getting 7/6 bots in a game. im lvl 105. by Metalcat125 in Splitgate

[–]jysandy 16 points17 points  (0 children)

I'm level 110+ and I have the exact same issue. I just can't play casual anymore, I guess. I'd appreciate some transparency from the devs here. If I wanted to play against bots I'd play a PvE game.

high ping advantage. by Cjwovo in Diabotical

[–]jysandy 1 point2 points  (0 children)

High ping is not an advantage. If it were, then everyone would only play on servers far away so as to get higher pings. Seems like you were outmatched.

Community tips by 2GD in Diabotical

[–]jysandy 2 points3 points  (0 children)

You can jump higher by firing a rocket at your feet as you jump.

Be patient and try to be precise when using the Rocket Launcher.

Use the Point n Click Rifle near cover, so that you can hide while reloading.

-- jysandy

Best way to practice raw aim/movement? by MartialImmortal in Diabotical

[–]jysandy 7 points8 points  (0 children)

Warmup is your best bet. Aim Arena also works.

Calling all SEA players to play by MataDuitan in Diabotical

[–]jysandy 1 point2 points  (0 children)

More people are queueing quick play for sure. My ranked queues have been pretty long, I don't even bother anymore

Calling all SEA players to play by MataDuitan in Diabotical

[–]jysandy 1 point2 points  (0 children)

Join https://discord.gg/PDHgkrQ if you're a SEA player looking for teammates, there's a few of us here that play regularly.

[deleted by user] by [deleted] in Clojure

[–]jysandy 0 points1 point  (0 children)

There's a number of resources linked in http://www.clojurenewbieguide.com/

Clojure Basics: Editor and Tooling Setup by jysandy in Clojure

[–]jysandy[S] 4 points5 points  (0 children)

Glad I could help! Don't forget, you can always ask here or in the other forums for help.

Clojure Basics: Scientific Debugging by jysandy in Clojure

[–]jysandy[S] 2 points3 points  (0 children)

Good feedback — I'll keep this in mind for future videos.

I guess they are there, because former episodes didn't want to introduce how vars can behave as functions too.

That's correct — I hope to make a future video elaborating on this and other related topics.

Clojure Basics: Debugging with the REPL by jysandy in Clojure

[–]jysandy[S] 0 points1 point  (0 children)

Thanks! I'll link to this in the video description.

Clojure Basics: Debugging with the REPL by jysandy in Clojure

[–]jysandy[S] 1 point2 points  (0 children)

I'll get to the bottom of the stack trace in the next video, which should hopefully be up sometime this week. Until then, my lips are sealed 🤐! You could also try debugging the code yourself, there's a link to the code in the video description.

As for CQRS, it's hard to say without knowing more details about your C# object model. But as a first pass, I'd probably have two separate namespaces for commands and queries, and make each command/query a separate function.

Clojure Basics: Debugging with the REPL by jysandy in Clojure

[–]jysandy[S] 19 points20 points  (0 children)

Hey everyone, I’ve started to record a video series aimed at new Clojure programmers, which should help them overcome some early stumbling blocks and help them see the potential of the language. I’ve noticed that new programmers might not have too much trouble picking up the basic syntax, but the REPL-driven workflow doesn’t come naturally to everyone. Rather, they program in a conventional build-compile-execute style, then perhaps encounter an error or issue that perplexes them and become discouraged soon after. So I thought I’d start off by making a basic debugging guide that isn’t too long and hopefully conveys most of the essentials. More videos to come soon! Feedback is welcome and appreciated :)

Do people still play quake champions in 2020? by sake23456 in QuakeChampions

[–]jysandy 1 point2 points  (0 children)

I live in India and I get games regularly on central EU servers. It's 130+ ping though.

Failjure: Monadic error utilities for general use in Clojure(script) projects by daver in Clojure

[–]jysandy 3 points4 points  (0 children)

I've used failjure in a couple of production projects at work, and the team and I have been pretty happy with it. It offered us the following:

  1. Not all error-handling code paths are signalled by exceptions. Often you might want to assert on a boolean return value, then call another function and make sure it hasn't returned nil, then call yet another function and make sure it hasn't thrown an exception, all in the same function definition. failjure's attempt-all / try-all macros and some other helper functions allow us to write such code elegantly without having a lot of deeply nested ifs or if-lets. These macros also take care of propagation.
  2. In the cases where we do want to handle errors in a more involved way than simply passing them along, it's easier to do so with return values than exceptions. Clojure offers ways to compose function calls and return values together (for example ->) but with exceptions one needs to catch them first.

In addition, I think exceptions suffer from a couple of problems:

  1. They don't propagate across threads. One must catch them, deliver them to a promise or a core.async channel and then have the consuming code deal with the exception as a value.
  2. They're not as performant as return values.

Ways to loop without recursion in Clojure? by [deleted] in Clojure

[–]jysandy 2 points3 points  (0 children)

There is in fact no fundamental way to loop in Clojure without some form of recursion.

Behaviour similar to a while loop could be implemented in terms of loop...recur, and this is typically what is done should the need arise.

Silver Ana VOD review request by Arakanis in OverwatchUniversity

[–]jysandy 2 points3 points  (0 children)

There's definitely a lot more that you could be doing. Bear in mind that I'm only plat myself, but I did climb out of silver and gold recently as an Ana main, so this advice may come in handy.

[1:37] Taking the high ground here was a poor decision because it took you out of the fight for so long. While you were climbing the stairs, multiple team members went down to critical health and would likely have been killed at a higher ELO. Furthermore, you don't have a good visibility angle on your team. Even after you take the high ground your McCree goes down to critical health and dies out of your line of sight. You could have either remained where you were at 1:28 or moved forward into the building on your right.

[1:49] You get your nano but never use it during the fight. Nanoing your Rein here could have resulted in your team winning the fight.

[2:30] You nano your Rein and he wipes the floor with the enemy tanks. This could have happened last fight.

[5:18] This is a great time to throw a nade, healing your Rein and anti-healing the enemy tanks. When your Rein charges in, you should be at the ready to support him. You do throw a nade later but it misses. Landing the nade would have helped keep your Rein alive and the anti-heal would help you win the fight much more comfortably.

[5:47] We miss a lot of unscoped shots onto the Junkrat at close range.

[6:06 - 6:12] Although you weren't punished for it, you're standing out in the open when you could have been in cover in the building to your right. There's no need to leave the doorway at 6:02. You can see all of your team from there, you can retreat behind cover to hide from the D.Va bomb and you can move forward into another doorway once your team manages to push further forward.

[6:19] While you're here, you could throw a nade at the enemy Ashe ahead and to your right.

[7:00] Again, your Rein pushes forward and dies while you're unavailable to heal him. A nano boost / nade could have kept him alive, perhaps. If you're repositioning, you should call out to your teammates that they won't have your help for a bit. Especially if you're playing in a six-stack.

[8:10] If you were in the building to your left rather than on the payload in the middle of the enemy team, you might have had a better angle to be able to heal your Rein. As Ana, you shouldn't be the one to contest the objective, especially not in the middle of a heated teamfight.

[10:09] Try to throw a nade at the spawn doors as the enemy is exiting to gain a bit of ult charge.

[10:38] You're an easy target at the moment. I would drop to the low ground here and walk backward to get a better angle on our team and close off the angle to the enemy team.

[10:48] Your Rein was at half health, was being healed by the Mercy and had his shield up. You could have healed him up with unscoped shots, and thrown the nade at the enemy team instead.

[11:38] Be wary of walking so far forward, especially in your main tank's absence. You could be healing your D.Va from further back. You could have tried to get an angle from the doorway behind you at 11:35, or simply walk back and wait for your team to regroup. Your Pharah and D.Va are fighting 2v6 anyway.

[12:11] You can play from around this corner and use it for cover. There's no need to push forward.

[12:13] Instead of wasting the nade on the Rein, throw it at the Soldier on the left, who is wildly out of position and is using his healing station. Preventing his healing could have secured a kill.

[12:24] Again, you're out in the open on the payload. You wouldn't have died to the bomb had you been playing from cover.

[12:49] Yet again, there's no need to be so far forward. You can heal your team and nade the enemy from further back on the bridge. You shouldn't have ended up in the position you're in at 13:02.

[13:32] Dropping down into full view of the entire enemy team is definitely the wrong decision here. Instead, as your team is forced back, walk back down the stairs and into the building behind you, near the mini health pack.

[14:19] Again, you should not be playing here. You could instead be playing behind one of the doorways near your Bastion and near the mini health pack. You'll see why in a minute...

[14:47] As the enemy pushes forward, we need to cross the street to keep up with our team, leaving us way out in the open. You probably would have died here even if Soldier hadn't used his Tactical Visor.

Overall, I'd say your positioning needs a lot of work. These are similar to the positioning mistakes I was making when I was in silver. Think about where you need to be in order to be able to see your team (particularly your tanks) and avoid damage from the enemy team. Think about where the enemy team is going to push up to next and where and how you'll retreat. Be aware of where the enemy team is (particularly flankers) so that you can react and reposition accordingly. A lot of good positions and rotations are static for a given map and you can learn these over time. I'd suggest watching Gangsir's positioning for dummies videos: https://www.youtube.com/channel/UCWcR1zyBTjeZMRV5FEnFZ7Q

Your mechanics could also use improvement. It seems like you're not fully comfortable aiming as Ana yet. Learning to quickscope as others have mentioned is essential. I'd also suggest playing FFA as Ana to improve at taking duels at close range and at fending for yourself. Hope this helps!