issues
Data license: AGPL · Data source: ACEmulator Project
1 row where user = 15372630
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date), closed_at (date)
id ▼ | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
457225519 | MDU6SXNzdWU0NTcyMjU1MTk= | 2015 | Potions filling up the wrong resource pool. | Roteleks 15372630 | closed | 0 | 2 | 2019-06-18T02:13:25Z | 2019-06-18T04:32:05Z | 2019-06-18T04:32:05Z | NONE | <!-- IF YOU DON'T FILL OUT THE FOLLOWING INFORMATION YOUR ISSUE MIGHT BE CLOSED WITHOUT INVESTIGATING --> ### Bug Report or Feature Request (mark with an `x`) ``` - [x] bug report -> please search issues before submitting - [ ] feature request ``` ### Repro steps. - Stamina potions display that it is restoring stamina but it erroneously refills the mana pool. - Health potions display that it is restoring health but it erroneously refills the stamina pool. - Mana potions just don't work at all. The message displayed reads: '_Mana Elixir (8002470E) contains invalid vital Mana_' ### The log given by the failure. The server does not report any errors or warnings. ### Desired functionality. Potions should refill the appropriate resource type. ### Mention any other details that might be useful. This was tested with the Stamina Tincture, Stamina Brew, Health Elixir, and Mana Elixir. I've restarted ACEmulator, and the Windows 10 VM that runs it, neither made any difference. | {"url": "https://api.github.com/repos/ACEmulator/ACE/issues/2015/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | completed | ACE 79078680 | issue |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issues] ( [id] INTEGER PRIMARY KEY, [node_id] TEXT, [number] INTEGER, [title] TEXT, [user] INTEGER REFERENCES [users]([id]), [state] TEXT, [locked] INTEGER, [assignee] INTEGER REFERENCES [users]([id]), [milestone] INTEGER REFERENCES [milestones]([id]), [comments] INTEGER, [created_at] TEXT, [updated_at] TEXT, [closed_at] TEXT, [author_association] TEXT, [active_lock_reason] TEXT, [draft] INTEGER, [pull_request] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [state_reason] TEXT, [repo] INTEGER REFERENCES [repos]([id]), [type] TEXT ); CREATE INDEX [idx_issues_repo] ON [issues] ([repo]); CREATE INDEX [idx_issues_milestone] ON [issues] ([milestone]); CREATE INDEX [idx_issues_assignee] ON [issues] ([assignee]); CREATE INDEX [idx_issues_user] ON [issues] ([user]);