• I - HP
• II - 공격력
• III - 방어력
• IV
  • [전사] 반격 피해 중 가장 등급이 높은 것
  • [아처] 콤보 피해 중 가장 등급이 높은 것.
  • [메이지] 스킬 피해 중 가장 등급이 높은 것.
• V
  • [전사] 콤보 피해감소
  • [아처] 콤보 피해감소
  • [메이지] 콤보 피해감소
• VI
  • [전사] 치명저항보너스, 추가 치명피해 중 택1
  • [아처] 치명저항보너스, 추가 치명피해 중 택1
  • [메이지] 치명저항보너스 고정

1. 전사(검사, 광전사 공통)

1순위 콤보 피해감소
2순위 반격피해

2. 아처(헌터, 윈드아처 공통)

1순위 에어본
2순위 콤보 피해감소 or 반격 피해감소
3순위 콤보피해

3. 메이지(소서러, 치유술사 공통)

1순위 에어본, 스턴
2순위 콤보 피해감소 or 반격 피해감소
3순위 스킬 치명피해

균등하게 강화해주시면 됩니다.

• IV 를 가장 많이 강화하시고
• 그 다음 I = II = III 를 많이 강화
• 가장 마지막으로 V, VI 를 강화하시면 됩니다.

Korean Language Pack W3C Validation Sublime Text Keymap open in broser Live Server indent-rainbow htmltagwrap HTML S

Materia Material Icon Theme

dasdfasdf

Jekyll is a static site generator that's perfect for GitHub hosted blogs (Jekyll Repository)

Jekyll Now makes it easier to create your Jekyll blog, by eliminating a lot of the up front setup.

• You don't need to touch the command line
• You don't need to install/configure ruby, rvm/rbenv, ruby gems ☺️
• You don't need to install runtime dependancies like markdown processors, Pygments, etc
• If you're on Windows, this will make setting up Jekyll a lot easier
• It's easy to try out, you can just delete your forked repository if you don't like it

In a few minutes you'll be set up with a minimal, responsive blog like the one below giving you more time to spend on writing epic blog posts!

1. Directory backup
2. svn update --set-depth empty ( 파일이 삭제됨 - del )
3. svn update --set-depth infinity ( 파일이 추가됨 - add )

Fork this repo, then rename the repository to yourgithubusername.github.io.

Your Jekyll blog will often be viewable immediately at http://yourgithubusername.github.io (if it's not, you can often force it to build by completing step 2)

Enter your site name, description, avatar and many other options by editing the _config.yml file. You can easily turn on Google Analytics tracking, Disqus commenting and social icons here too.

Making a change to _config.yml (or any file in your repository) will force GitHub Pages to rebuild your site with jekyll. Your rebuilt site will be viewable a few seconds later at http://yourgithubusername.github.io - if not, give it ten minutes as GitHub suggests and it'll appear soon

There are 3 different ways that you can make changes to your blog's files:

1. Edit files within your new username.github.io repository in the browser at GitHub.com (shown below).
2. Use a third party GitHub content editor, like Prose by Development Seed. It's optimized for use with Jekyll making markdown editing, writing drafts, and uploading images really easy.
3. Clone down your repository and make updates locally, then push them to your GitHub repository.

Edit /_posts/2014-3-3-Hello-World.md to publish your first blog post. This Markdown Cheatsheet might come in handy.

You can add additional posts in the browser on GitHub.com too! Just hit the + icon in /_posts/ to create new content. Just make sure to include the front-matter block at the top of each new blog post and make sure the post's filename is in this format: year-month-day-title.md

1. Install Jekyll and plug-ins in one fell swoop. gem install github-pages This mirrors the plug-ins used by GitHub Pages on your local machine including Jekyll, Sass, etc.
2. Clone down your fork git clone [email protected]:yourusername/yourusername.github.io.git
3. Serve the site and watch for markup/sass changes jekyll serve
4. View your website at http://0.0.0.0:4000
5. Commit any changes and push everything to the master branch of your GitHub user repository. GitHub Pages will then rebuild and serve your website.

I've created a more detailed walkthrough, Build A Blog With Jekyll And GitHub Pages over at the Smashing Magazine website. Check it out if you'd like a more detailed walkthrough and some background on Jekyll. 🤘

It covers:

• A more detailed walkthrough of setting up your Jekyll blog
• Common issues that you might encounter while using Jekyll
• Importing from Wordpress, using your own domain name, and blogging in your favorite editor
• Theming in Jekyll, with Liquid templating examples
• A quick look at Jekyll 2.0’s new features, including Sass/Coffeescript support and Collections

✓ Command-line free fork-first workflow, using GitHub.com to create, customize and post to your blog
✓ Fully responsive and mobile optimized base theme (Theme Demo)
✓ Sass/Coffeescript support using Jekyll 2.0
✓ Free hosting on your GitHub Pages user site
✓ Markdown blogging
✓ Syntax highlighting
✓ Disqus commenting
✓ Google Analytics integration
✓ SVG social icons for your footer
✓ 3 http requests, including your avatar

✘ No installing dependancies
✘ No need to set up local development
✘ No configuring plugins
✘ No need to spend time on theming
✘ More time to code other things ... wait ✓!

Open an Issue and let's chat!

You can use the Quick Start workflow with other themes that are set up to be forked too! Here are some of my favorites:

• Hyde by MDO
• Lanyon by MDO
• mojombo.github.io by Tom Preston-Werner
• Left by Zach Holman
• Minimal Mistakes by Michael Rose
• Skinny Bones by Michael Rose

• Jekyll - Thanks to its creators, contributors and maintainers.
• SVG icons - Thanks, Neil Orange Peel. They're beautiful.
• Solarized Light Pygments - Thanks, Edward.
• Joel Glovier - Great Jekyll articles. I used Joel's feed.xml in this repository.
• David Furnes, Jon Uy, Luke Patton - Thanks for the design/code reviews.
• Bart Kiers, Florian Simon, Henry Stanley, Hun Jae Lee, Javier Cejudo, Peter Etelej, Ben Abbott, Ray Nicholus, Erin Grand, Léo Colombaro, Dean Attali, Clayton Errington, Colton Fitzgerald, Trace Mayer - Thanks for your fantastic contributions to the project!

Issues and Pull Requests are greatly appreciated. If you've never contributed to an open source project before I'm more than happy to walk you through how to create a pull request.

You can start by opening an issue describing the problem that you're looking to resolve and we'll go from there.

I want to keep Jekyll Now as minimal as possible. Every line of code should be one that's useful to 90% of the people using it. Please bear that in mind when submitting feature requests. If it's not something that most people will use, it probably won't get merged. 💂‍♂️