Habitica is an open source habit building program which treats your life like a Role Playing Game. Level up as you succeed, lose HP as you fail, earn money to buy weapons and armor.
We need more programmers! Your assistance will be greatly appreciated. The wiki pages below and the additional pages they link to will tell you how to get started on contributing code and where you can go to seek further help or ask questions:
- Guidance for Blacksmiths - an introduction to the technologies used and how the software is organized.
- Setting up Habitica Locally - how to set up a local install of Habitica for development and testing on various platforms.
Habitica's code is licensed as described at https://github.com/HabitRPG/habitica/blob/develop/LICENSE
Found a bug? Please report it to admin email rather than creating an issue (an admin will advise you if a new issue is necessary; usually it is not).
Have any questions about Habitica or its community? See the links in the habitica.com website's Help menu or drop in to Guilds > Tavern Chat to ask questions or chat socially!
CLOSED. Pixel Art Thread: Pets & Mounts
**THIS THREAD IS CURRENTLY CLOSED.
USE THE TRELLO PIXEL BOARD INSTEAD!! https://trello.com/b/vwuE9fbO/habitrpg-pixel-art
This Github Thread is now permanently closed. Feel free to unsubscribe.... and head on over to the new Trello :D
Classes - #943 Quests - #945 Miscellaneous - #946
Pixel artists
Hey guys, been getting a lot of pixel artist chiming in with desire to contribute (which effing rocks! thanks guys!). I'm trying to figure out a way to process this (or decide on someone?), so I figured I'd start a discussion here.
There will definitely be need for more pixel art. I want it to as closely resemble our current setup (browserquest iconset) as possible. We'll need a female avatar, character customizations (tabards, pets, mounts, etc) that people purchase with tokens, custom weapons / armor, and way later down the pike we'll want custom iconsets for white-label (don't worry about that now).
If you want to contribute, read the bottom of this wiki, reply here with maybe a sample? Just so I know it's the "type" of work Habit wants before sending you on designing a lot of stuff, just to have the pull-request denied. Let's keep the convo rolling, if anyone has other suggestions for going about this.
Cron did not run (no quest progress, no damage from incomplete Dailies, Dailies still checked from yesterday) [$270 awarded]
When I logged in this morning my dailies from yesterday were still showing as checked. I tried reopening habitrpg, I tried logging out and logging back in, and I tried waiting (it's been an hour now). No luck, my dailies still show as checked even though I haven't gotten out of bed yet today...
I do have two dailies which I was not supposed to do yesterday (MWF dailies) and they are now showing as tickable so my account clearly knows that it is Monday. Maybe this is just the site's way of telling me those are the only dailies I should do today and I should take the day off from everything else...
edit by admin:
If you experienced some effects of cron but not all of them, then you actually were hit by this bug: https://github.com/HabitRPG/habitrpg/issues/4313 (for example, if some of your Dailies became unticked but not all of them, or if you took Damage from your Dailies even though they remained ticked, or if your Party page shows a quest message for you from overnight).
What to do if your Dailies are still ticked from yesterday:
Go to the Tavern to see if you are Resting in the Inn. If the left-hand column has a large green button that says "Check Out of the Inn", click that, and your Dailies will reset tomorrow (more information about Resting in the Inn). If you didn't see that button, then either wait until tomorrow because your Dailies will almost certainly reset correctly tonight, or:
The $270 bounty on this issue has been claimed at Bountysource.
CLOSED. Pixel Art Thread: Quests
THIS THREAD IS CURRENTLY CLOSED. THE PIXEL BOARD IS UP!!! https://trello.com/b/vwuE9fbO/habitrpg-pixel-art
This Github Thread is now permanently closed. Feel free to unsubscribe.... and head on over to the new Trello :D
CLOSED. Pixel Art Thread: Miscellaneous
THIS THREAD IS CURRENTLY CLOSED. THE PIXEL BOARD IS UP!!! https://trello.com/b/vwuE9fbO/habitrpg-pixel-art
This Github Thread is now permanently closed. Feel free to unsubscribe.... and head on over to the new Trello :D
CLOSED. Pixel Art Thread: Classes & Gear
**THIS THREAD IS CURRENTLY CLOSED. THE PIXEL BOARD IS UP!!! https://trello.com/b/vwuE9fbO/habitrpg-pixel-art
This Github Thread is now permanently closed. Feel free to unsubscribe.... and head on over to the new Trello :D**
Zak's Design Tweaks & Rewrites Thread
Just a log for me to record before/after screencaps of my random interface tweaks. Anyone is welcome to suggest further changes or critique.
This is probably only of interest to UI nerds and members of the dev team.
"two versions of your data" bug / Bizarre cron reset problem - cron runs (boss damage) but leaves Dailies ticked; Dailies do damage when completed (not from sync errors) [$150]
I talked to Alys about this and she said she hadn't heard about this bug before, but it's now happened to me twice in just three days.
Here's what happens in a nutshell:
I have put myself into the Tavern until this problem can be resolved, as I am damaging my party unfairly while we're on a Quest, which is extremely vexing.
edit by admin:
Advice:
This bug occurs when your browser stops syncing correctly with Habitica's server and so the server never finds out that you have taken actions on the website (e.g., it doesn't know that you completed your Dailies). A wide range of odd behaviour can happen when syncing stops. Typically, the website keeps behaving as if all your actions are being recorded, but later when syncing starts again those actions will either be reversed as if they had never occurred or will be re-applied as if they had happened twice.
1. How to fix Dailies that should have become unticked:
There are two ways to untick Dailies without losing Experience (XP), Gold (GP), and Mana (MP):
You will probably find that your streaks for those Dailies have been set to zero. You can reset them by editing each Daily and looking in the Advanced Options part of the edit screen. If you aren't sure what your streaks were, go to Data menu -> Data Display Tool and use the Dailies History section to help you estimate them (for more information see the wiki's Streaks page).
2. How to recover from damage (health loss) caused by Dailies that you did complete yesterday:
When this bug occurs, it can cause you to lose health for Dailies that you had completed on the previous day. If you are in a boss quest, this will also cause the other quest participants to lose health. You and they can regain the lost health by each of you going to Settings -> Site and clicking on the Fix Character Values button. You will be shown a form that you can use to set your Health back to what it should be. If the damage was severe enough to cause you to die, you can also restore your level (increase it by one) and give yourself extra gold to buy back the piece of equipment that you lost.
3. How to recognise this bug as soon as it starts:
Sometimes the first sign of that this bug has occurred is that the blue sync bar does not appear when you are taking actions on the site. So, as you are using the website, keep an eye on the top of the screen where the blue bar should be. You should see it every time you add a task, delete a task, or click on the checkbox or +/- buttons of a task. You should also see it when changing/completing checklist items, and when using Rewards, and when doing a variety of other actions.
Not receiving any drops at all for a significant period of time is another sign that this bug has occurred (although note that drops are random, and depend on buffs and equipment, and have a daily limit that cannot be exceeded, so it is possible to receive no drops without this bug occurring).
If you ever do not see the blue bar when you're expecting it or if you notice anything else that indicates that the website is not syncing with the server, immediately log out of the website and log back in (if you are not sure what your login details are, you can view them at Settings > Site before you log out - in particular, note the email address there and make sure it is correct and current). If the blue bar still doesn't appear when you action tasks, try logging out again. This should stop you being unfairly damaged when cron runs and prevent the other problems this bug causes.
However note that this bug can still occur even when the blue bar keeps working. If you don't see the blue bar, you definitely have this bug. If you do see the blue bar, you might still have this bug. :( See the advice in point 4 for a more certain way to protect yourself.
4. What to do if you experience this bug often:
It is likely that cron problems caused by this bug won't occur if you reload Habitica using your browser's refresh button just before you stop using Habitica for the day. After you've reloaded, do a sync using the sync button in the top right hand corner of the tasks page and then check that your Dailies are still ticked off. If they aren't, tick them again and then repeat the reload and sync.
However a reload is not always a reliable way to stop the bug; sometimes logging out is necessary.
You can also use the Data Display Tool (available from Habitica's Data menu) to examine your Dailies in the "Dailies Incomplete" section. That tool takes its data directly from Habitica's server, so if it shows differences from what you see on the Habitica website, it means that this bug has occurred on the website. Reload the Habitica website then refetch data in the Data Display Tool, and compare again. Repeat until the Habitica website shows the same thing as the Data Display Tool. If reloading the Habitica website doesn't fix the problem, try logging out of Habitica and then logging back in.
I'm sorry it's such a pain. If you've had this problem happen to you just once or twice, it might not be worth the effort of doing this every night, but if it happens to you very frequently, this might stop or reduce it. It's only a workaround - we do intend to make a proper fix, as soon as we can work out what that fix should be.
There is a $150 open bounty on this issue. Add to the bounty at Bountysource.
Quest completed but rewards and completion not recorded for quest participant(s)
I was the quest owner, and started the quest. After three days, the party screen reported us as having completed the quest, but I received no reward. The quest is not listed in my achievements, but it is listed in the other player's achievements.
The quest in question was Attack of the Mundane Questline, Pt. 1: Dish Disaster!
My UUID: 94adb57f-763e-444c-9483-29c1e2b194eb Party member's UUID: c2b855f5-1f53-4d4a-bbf7-e81b1fdc55f9
edit by admin:
What to do if this happens to you:
When a quest finishes, all participants should receive all the rewards listed on the quest scroll.
If any participants did not receive them, go to Help > Report a Bug from the Habitica website's menu (or Guilds > Report a Bug on the mobile app), and post there to say that you did not receive the quest rewards. Include the name of the quest. If you know that it happened to all or most of the quest participants, say that too. You do not need to list all the players affected.
You do not need to comment on this issue; the Report a Bug guild is the best place to report any bugs.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Suggested UI Changes and Problems
Alright. Folks want a place for feedback. Here it is!
Redesign navbar
header.styl
menu.jade
Redesign navbar to:
menu.styl
index.styl
npcs.styl
UUID:1322727e-9911-4ad4-aea9-a5ebd8cba826 User: Pixel
improve link selection when using accessibility options
build(deps): bump core-js from 3.26.1 to 3.27.1 in /website/client
Bumps core-js from 3.26.1 to 3.27.1.
Changelog
Sourced from core-js's changelog.
... (truncated)
Commits
f44604e
3.27.198995dc
add some missed dependencies to entries10517de
add all iterator helpers to(Async)Iterator.from
entries for runtime0f4a279
some stylistic changesda2e4f8
fix a Chakra-based MS Edge (18-) bug that unfreeze (O_o) frozen arrays used a...66c427f
3.27.0c8322b0
allow gc disposed resources before disposing all resources of stack0d9478e
add some comments68c9bf6
smoothed behavior of some conflicting proposals4cc298a
fix a couple of testsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)build(deps): bump flat and @vue/cli-plugin-unit-mocha in /website/client
Bumps flat to 5.0.2 and updates ancestor dependency @vue/cli-plugin-unit-mocha. These dependencies need to be updated together.
Updates
flat
from 4.1.1 to 5.0.2Commits
e5ffd66
Release 5.0.2fdb79d5
Update dependencies, refresh lockfile, format with standard.e52185d
Test against node 14 in CI.0189cb1
Avoid arrow function syntax.f25d3a1
Release 5.0.154cc7ad
use standard formatting779816e
drop dependencies2eea6d3
Bump lodash from 4.17.15 to 4.17.19a61a554
Bump acorn from 7.1.0 to 7.4.020ef0ef
Fix prototype pollution on unflattenUpdates
@vue/cli-plugin-unit-mocha
from 4.5.15 to 5.0.8Release notes
Sourced from
@vue/cli-plugin-unit-mocha
's releases.... (truncated)
Changelog
Sourced from
@vue/cli-plugin-unit-mocha
's changelog.... (truncated)
Commits
b154dbd
v5.0.84a0655f
v5.0.7ef08a08
v5.0.698c66c9
v5.0.5ce97e62
fix: add XMLSerializer to the global scope (#7101)ca97fc2
v5.0.4dd53f26
v5.0.3a859b1f
v5.0.292d80a8
v5.0.1c913cdc
v5.0.0Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.build(deps-dev): bump axios from 1.2.1 to 1.2.2
Bumps axios from 1.2.1 to 1.2.2.
Release notes
Sourced from axios's releases.
Changelog
Sourced from axios's changelog.
Commits
8ea4324
chore(docs): added latest release notes45c4948
chore: build new version6f74cb1
chore(ci): set conventional-changelog header config; (#5406)8de391f
chore(ci): fix automatic contributors resolving; (#5403)341f735
chore(ci): improved logging for the contributors list generator;46085e6
chore(ci): fix release action;f12d01e
chore(ci): fix version bump script by addingbump
argument for target version;75217e6
fix(ci): fix release script inputs;c1fc33c
chore(deps): bump decode-uri-component from 0.2.0 to 0.2.245b29db
GitHub Actions Release script; (#5384)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)build(deps): bump json5 and tsconfig-paths
Bumps json5 and tsconfig-paths. These dependencies needed to be updated together. Updates
json5
from 2.2.1 to 2.2.2Release notes
Sourced from json5's releases.
Changelog
Sourced from json5's changelog.
Commits
14f8cb1
2.2.210cc7ca
docs: update CHANGELOG for v2.2.27774c10
fix: add proto to objects and arraysedde30a
Readme: slight tweak to intro97286f8
Improve example in readmed720b4f
Improve readme (e.g. explain JSON5 better!) (#291)910ce25
docs: fix spelling of Aseem2aab4dd
test: require tap as t in cli tests6d42686
test: remove mocha syntax from tests4798b9d
docs: update installation and usage for modulesUpdates
tsconfig-paths
from 3.9.0 to 3.10.1Changelog
Sourced from tsconfig-paths's changelog.
Commits
80bc810
v3.10.1beb9a47
Add changelog for 3.10.1893b76d
Add register.js to published files9327fa1
v3.10.0766a0e8
Update changelog for 3.10.02cf8b21
Categorize changelogfb67ba2
Update changelog with unreleased PRs079285a
Add file extenstion to typings property value (#151)c49386c
feat(tsconfig-loader): extends config from node_modules without './node_modul...f289c99
fix typo (#165)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.