sudoxreboot/habitica
1
0
Fork 0
mirror of https://github.com/sudoxnym/habitica.git synced 2026-07-22 03:34:14 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
No description
1167 commits 3 branches 0 tags 1.6 GiB
JavaScript 52.3%
CSS 23.8%
Vue 23.1%
SCSS 0.6%
Find a file
Alice Harris 964d1a640c allow quest progress from attack skills BEFORE quest starts 
Currently, if you do Brutal Smash or Burst of Flames BEFORE you start a quest, they do NOT damage the quest boss if you start the quest later in the day (this is the opposite of how tasks work). This also means that if you are not on a boss or collection quest, then those skills can't damage the World Boss. I think this is counterintuitive and I think users are expecting those skills to act on Drag'on even when they are not on a quest.

This change causes damage from the skills to be treated just like damage from tasks - it's applied to quests started later that day and to Drag'on.

THIS HAS NOT BEEN TESTED. Sorry. :( I have broken my VM temporarily.
2014-07-13 15:44:05 +10:00
css feat(summer): summer event 2014-06-20 15:28:29 -06:00
dist allow quest progress from attack skills BEFORE quest starts 2014-07-13 15:44:05 +10:00
img feat(quests): seahorse quest 2014-07-07 14:56:47 -06:00
locales fix(dilatory): update completion wording 2014-07-10 13:04:24 -06:00
script allow quest progress from attack skills BEFORE quest starts 2014-07-13 15:44:05 +10:00
test fix(tests): add in freeRebirth 2014-06-22 14:10:25 -07:00
.gitignore Rebalance potion drop ratios 2013-12-07 20:16:13 -05:00
.travis.yml allow any branch in travis builds 2013-10-27 16:23:02 -03:00
favicon.ico add a bunch of possible shared items for now, will clean up later 2013-03-11 14:50:00 -04:00
Gruntfile.js Create spritesmith CSS in a single pass. 2014-03-27 23:00:54 -07:00
index.js [https://github.com/HabitRPG/habitrpg/issues/1977] APIv2 WIP - start of a framework where operations are shared between client & server. If the op is called on the client, it updates the user & then POSTs to the server with op of the same name. If called on server, it updates the user and user.save()s 2013-12-11 21:42:05 -07:00
LICENSE chore(license): reference main repo's license here 2014-01-27 15:52:19 -08:00
package.json fix(tests): temporary fix to some i18n issues in habitrpg-shared algo tests 2014-05-11 15:56:40 -06:00
README.md fix readme: use npm test to run tests 2013-11-23 23:33:24 -03:00

README.md

Build Status

Shared resources useful for the multiple HabitRPG repositories, that way all the repositories remain in-sync with common characteristics. Includes things like:

  • Assets - sprites, images, etc
  • CSS - especially, esp. sprite-sheet mapping
  • Algorithms - level up algorithm, scoring functions, etc
  • View helper functions that may come in handy for multiple client MVCs
  • Item definitions - weapons, armor, pets

##Installation

  • npm install

  • grunt - after you've made modifications and want to compile the dist files for browser

  • Node.js

    • require ('coffee-script')
    • require('./script/algos.coffee'), require('./script/helpers.coffee'), etc.

  • Browser

    • Use <script/> tag to include ./dist/habitrpg-shared.js it will export window.habitrpgShared object.
    • // Use `browser.debug.js' if you want to have sourcemaps. - EDIT: Only one file now, and it has sourcemaps. Fix this

  • Note how to invoke scoring function:

    • algos.score(user, task, direction), etc
    • TODO document all the functions

##Tests

  • npm test

##CSS Shared CSS between the website and the mobile app is a fuzzy area. Spritesheets definitely go in habitrpg-shared (since mobile uses them too). Other things, like customizer buttons, may want to go here? As you find sharable components, (1) move them from the website into habitrpg-shared, (2) remove from website & make sure all html/css references are updated.

Currently, all or most spritesheets are available. They're in css/*.css, but that's not what you want. You want /spritesheets.css which is the concat'd file (using grunt) which includes all the spritesheets. I'd prefer this be in /dist/spritesheets.css for consistency, but it's having image referencing weirdness