Git Product home page Git Product logo

blitzkit's Introduction

About

Currently Working On...

featured project

Languages

top languages

blitzkit's People

Contributors

dependabot[bot] avatar imgbotapp avatar tresabhi avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

blitzkit's Issues

BOT Bug

The bot cant serch period or anything commands. Please fix it thanks.
Screenshot_2023-09-21-21-45-04-488_com discord

Tank Compare Labels layout

Currently, labels in tank compare are too long, which take up too much room and makes the statistic comparison difficult to see all in one page. Several solutions:

Create subtypes for certain statistics.
So instead of:

  • Dispersion
  • Dispersion moving
  • Dispersion hull traversing
  • Dispersion turret traversing
  • etc...

Do this:

  • DISPERSION (header)
  • base
  • moving
  • hull traverse
  • turret traverse

This would massively reduce the space necessary for a bunch of words which essentially just take up hella room. You should also do this for stats which are separated by ground resistance. Instead of doing "traverse speed on X terrain" just do a header with hard medium soft below. This applies to p/w (you can just abbreviate this as well tbh, and make a dropdown with the full name when people tap / hover on it), camo values (moving, stationary, shooting, on fire etc.)

Tank compare statistics layout

The space between the row of numbers / labels and the lines are massive. Squishing them down would make it easier to take screenshots or look at the entire stat category at once instead of continuously scrolling up and down
In the space where there is a single stat in the tank compare, blitzstars fits 2 or 3 rows

Blitzkit general statistics organization and labels

This applies to statistics for both tank compare and tankopedia.

Minor thing: "Fire" IMO could just be "firepower"

Under the firepower header, several things should be cleaned up and reorganized into their own sub-categories:

  • Items that are related to what shell the tank is firing should be in its own category. You could just label it "shell" and put the shell selector beside it in the tankopedia
  • Items that are related to gun handling should be in its own category as well.

You could also separate hard stats from soft stats entirely (this is what blitzhangar does). Do the above, but completely separate gun handling, and put it under its own header separate from "firepower"

Either way, the main issue with "Fire" is that compared to maneuverability and survivability, it's a huge massive category with a bunch of unformatted stats which makes it hard to instantly identify what you want to look at. Having a bit more formatting here with the proper indentations would make both tank compare and tankopedia much easier to read

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.