星之一角

What have you found for these years?

2016-04-07

GW2 WvW Zerg Bursting Chronomancer

Post on official forum: Re: Help with a WvW Chrono Build for group play

So since I've been playing in group with a bursting mesmer for a while
now, I would like to put my two cents here. In short, I am running this
build: WvW Zerg Bursting Chronomancer

I mainly play with a group of 20~50 against another group of 20~50,
acting as a bomb and taking enemies down with low health or glassy ones.

This is basically a power build because condition damage doesn't work
too well in this context and shatters could hardly hit with condition
weapons. Greatsword is somehow the only viable weapon for AoE damage.

I need at least two stun breaks to survive due to lack of stability,
and Decoy and Blink are the best ones especially for Blink, it's
truly a life saver because this build is quite glassy. Only 3 pieces
of trinkets are Captain and the rest are all Berserker. I should heal
or blink even if I only took one shot in general.

Mirror was taken due to fast recharge so it works well with
Mender's Purity. Cleansing two conditions is not a lot, but with
15 seconds cooldown it's acceptable. Also given this pirate ship meta,
reflection could come in handy when I'm aimed by a Ranger, too.

Restorative Illusions is not always necessary. I only take it when
we're out of number and having only around 20 people. If cleansing
is not an issue, I'll take Protected Phantasms instead. Fighting
against 20+ people, illusions basically die immediately so this would
be necessary to land Phantasmal Berserker, and it still dies immediately
after distortion ran out so I would shatter it immediately, too.

So here's how a fight goes:

Basically just stay a bit behind our train. Whenever I see a good chance
or whenever the commander calls, drop Gravity Well and Continuum Split.
Drop Well of Calamity accordingly if it's not a good enough chance,
or when Gravity Well is on cooldown. Use Blink as a gap closer accordingly.
Sometimes Decoy would work, too.

Shatter fast and don't try to save illusions. Shatter works very well
when I'm around the enemies with Illusionary Reversion and Chronophantasma.
Just smash the buttons when enemies are around. This would be a very
strong burst with Greatsword. Use Blink and Decoy to escape accordingly.
(or even Decoy to shatter for the extra illusion)

Take Veil or Portal Entre accordingly, of curse.
Swap a Berserker ring with a Solider ring if we're so out of number.

*

On the other hand, I really admire how ND (Never Die) plays. I don't know
how they run Chronomancer in detail, but this would be the build from my
observation: WvW Zerg Support Chronomancer
Eat this food: Plate of Mussels Gnashblade

A lot of slots are empty because I have no idea. Try your own creativity.
This build is very, very cooperative though. Heralds are much needed as well.

Basically it's a boon sharing build, stacking 25 stacks of stability and
maintain permanent resistance. The use of Temporal Curtain was very impressive
as well. They could kill 5+ people standing on the wall in a burst.

I don't see pirate ship meta on them and they could take down double or
even triple enemies (e.g. 15 vs 30). Both tanky and destructive.
In the end often enemies just ran away seeing them.

This definitely doesn't work without a voice chat.

2016-02-25

Finally got letsencrypt done

Finally got letsencrypt done.

I don't quite understand why the official scripts were so complicated,
but finally I got it done with letsencrypt.sh (Thanks Ash for
recommending it) along with some scripts from letsencrypt-nosudo.

This is a note for what I've done in case I need to do this again.
First let's clone it first:

git clone git@github.com:lukas2511/letsencrypt.sh.git
cd letsencrypt.sh

Then let's generate a private key and a signing request:
(This was from letsencrypt-nosudo)
openssl genrsa 4096 > domain.key
openssl req -new -sha256 -key domain.key -subj "/" -reqexts SAN -config <(cat /etc/ssl/openssl.cnf <(printf "[SAN]\nsubjectAltName=DNS:example.com,DNS:www.example.com")) > domain.csr
Note that the second command cannot run under Fish,
and I would like to know if there's any way to create a wildcard certificate?
I tried to use *.godfat.org however it seems letencrypt doesn't allow it.

Let's setup the other configs:
echo example.com www.example.com > domains.txt
mkdir .acme-challenges

Finally setup Nginx for acme-challenge:
(Note that letsencrypt.sh would write files into it and clear it after done)
# /etc/nginx/nginx.conf
location /.well-known/acme-challenge {
  alias /home/example/letsencrypt.sh/.acme-challenges;
}

Begin hitting letencrypt:
./letsencrypt.sh --signcsr domain.csr

You'll get the certificate printed on stdout. Not sure if there's a way to
output it to a file, but anyway you could just copy it and put it in a file.
I'll assume you put it in domain.crt and we could continue
setting up Nginx:
mkdir dist
# Download the other certificate from letsencrypt (source)
wget https://letsencrypt.org/certs/lets-encrypt-x1-cross-signed.pem
# Bundle it for the final certificate:
cat domain.crt lets-encrypt-x1-cross-signed.pem > dist/ssl.crt
# Setting up the final files
cp domain.key dist/ssl.key
chmod 600 dist/ssl.key
chmod 644 dist/ssl.crt
sudo chown root:root dist/ssl.*
sudo cp dist/ssl.* /etc/nginx/

And here's the relevant Nginx config:
# /etc/nginx/nginx.conf
server {
  listen 80;
  listen 443 ssl http2;
  ssl_certificate ssl.crt;
  ssl_certificate_key ssl.key;
  ssl_session_timeout 5m;
  ssl_prefer_server_ciphers on;
  ssl_protocols TLSv1.2;
  ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-RSA-DES-CBC3-SHA:ECDHE-ECDSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';
}

After restarting Nginx, you could verify it with ssltest.

P.S. Thanks to StartSSL started involving something with China
pushing me forward this. I was so lazy figuring out how it works
before. The world deserves free/cheap secure connections for
independent developers/organizations.

All texts are licensed under CC Attribution 3.0