bb010g

.

bb010g

let nixpkgs = import ./nixpkgs.nix; in
import "${nixpkgs.nixpkgs}/nixos" {
  configuration = {
    imports = [
      ./configuration.nix
    ];
  };

  system = "x86_64-linux";
}

bb010g

HISTSIZE=50000
SAVEHIST=50000
HISTFILE=~/.zsh_history

# sane zplug installation defaults
if [[ -z "$ZPLUG_HOME" ]]; then
  ZPLUG_HOME="${XDG_DATA_HOME:-$HOME/.local/share}/zplug"
fi
if [[ -z "$ZPLUG_CACHE_DIR" ]]; then
  ZPLUG_CACHE_DIR="${XDG_CACHE_HOME:-$HOME/.cache}/zplug"

bb010g

import * as fs from 'fs';
import * as ts from 'typescript';

function flat<T>(arr: T[][]): T[] {
  return arr.reduce((acc, val) => acc.concat(val), []);
}

const noDecorators = undefined;
const noImportClause = undefined;
const noInitializer = undefined;

bb010g

So, IMHO, you've got a few main aspects to a game's combos: execution, length, paths, variety, and flexibility.

Execution is what most people think of first when they think of combos. Good execution is a requirement to use combos, with good varying by game. Shorter combos are easier to execute, longer combos are harder. Let's go through some games. (I'll also start to tackle length here.)

• If you want a game without combos, play Divekick.
• Super Street Fighter 2 Turbo and Fantasy Strike are games that focus heavily on short combos that are based around jump-in > normal x special (x being cancel). You have to time your jump-in button correctly to leave your opponent in hitstun long enough for you to throw out and hit with your grounded normal, and then execute your special move before your cancel window is up. So, with Ryu, you might do jHK (jumping heavy kick) cMK (crouching medium kick) fireball (down>downforward>forward+heavy punch motion). This is short, but feels alright. The timing is satisfying becau

bb010g

Keybase proof

I hereby claim:

• I am bb010g on github.
• I am bb010g (https://keybase.io/bb010g) on keybase.
• I have a public key ASCFVKliI5x9FgE9mXUlSXV8v06x1c_RMICP2xDKQs9Y6go

To claim this, I am signing this object:

bb010g

Comments are for explaining non-obvious algorithms. If your function has a strange signature that doesn't make it's basic utility obvious, it should be renamed and the interface possibly rethought. If it's just a weird algorithm, document the crap out of it in documentation comments, not normal comments. If your internal code needs comments to be readable, refactor until the flow is understandable. If someone is left wondering why you did something a certain way, comment why. (A good sign for this is if it took you a while to come up with that piece of code.) If someone is left wondering what your code even does, rewrite it.

bb010g

I get why String vs &str is a thing beginners struggle with, but it's never an issue in actual code, at least more than Vec<T> vs &[T] is. &[T] is a slice of borrowed memory. Vec<T> is owned memory. String and &str talk about verified UTF-8 strings. String -> Vec<u8>. &str -> &[u8]. Use in exactly the same way you would your normal hunk of memory types.

Beyond that, when you want to get a slice of your vector, you use &vec. When you want to get a &str out of your String, use &string. When you want to copy a slice into a new vector, you use

bb010g

use Crypt::Random;

class Roll {
  has Int:D $.dice = 1;
  has Int:D $.sides is required;
  has Int:D $.constant = 0;

  method parse(Str:D $str) {
    if $str ~~ /[$<d>=(\d+) d]? $<s>=(\d+) [\+ $<c>=(\d+)]?/ {
      self.new(dice => ($<d>:v || 1).Int, sides => ($<s>:v).Int, constant => ($<c>:v).Int);

bb010g

The PMCC Matrix room has a voice system in place to prevent spam. Here's what you need to know:

Why can't I talk?

A user must have voice status to send messages in #pmcc:matrix.org. If you're not voiced, you'll receive a permission error when you attempt to talk.

How do I get voice status?