PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Add monster PoB codes for import and predefines for basic types

Open
#3,089 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Lua
Stars
5.4k
Forks
2.4k
Avg merge
1d 12h
Merged PRs (30d)
26

Description

Check for duplicates
  • I've checked for duplicate issues by using the search function of the issue tracker
Is your feature request related to a problem?

I'd like to compare my character against specific monsters and see where things aren't working the way I expected.

Describe the solution you'd like

I'd like to be able to get a monster PoB code similar to the character one that included all the monster stats and effects. Then I could import that monster - or maybe even all the monsters on the next level - and see where things are going off the rails or not what I expected. Next step, an in-game commnad to dump these codes for all the the monsters on the screen (lol trying to mouse over some hasted beast to type Alt-C or something). Merry this to an on death macro and you've got the start of a "WTF just killed me?!" tool.

My reason for this was that today I ran into some monsters than I found almost impossible to kill, and it took me way too long to look everything up on PDB and even then I still had questions. Last night I ran ran into an invulnerable monster on Beach map,, and couldn't even ding the guy for a bar. I still have no idea what was up with that.

Describe alternatives you've considered

Imports similar to items, but these are more similar to characters and a PoB code would still be useful to copy them around. Also, the monsters will often have various statuses specific to the fight and you. Marry this with a

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests. Start by tracing the existing character PoB import/export flow and how monster stats and effects are represented, then determine the scope for encoding and importing them. Done would require a settled design for monster codes or predefined basic types, plus a clear validation path.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.