Pirate RPG
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
No files, tests, or entry points are named. Start by reviewing the existing Go prototype and turn the open design questions into concrete specifications for anti-bot strategic mechanics and region battles; done means both systems have defined rules and interactions.
Written by the indexing model from the issue text.
Description
Current design
- Mythical setting, including things like Kraken, Davy Jones and magic(maybe)
- Different regions
- Players can travel between regions
- Mobs vary in difficulty depending on the region
- Every region can be ruled by a player clan
- From time to time a clan can be challenged for control of a region
- The ruling clan can collect taxes on transactions happening in that region
- The ruling clan sets the tax rate, incentivizing people to travel between regions and set the rate to optimize revenue(laffer curve).
- Farming is done by exploring islands in a region
- PvE can be done by attacking vessels in the current region
- Player's ship can be upgraded with different items(cannons, etc)
- Players can pick a faction after leveling to a certain point:
- Navy: gets rewards for hunting pirates
- Pirates
- Ship crews?
- Items
- Stored in player's inventory
- Each has a type(Weapon, Armor, Ship Part) and attributes
- Fishing
TODO
- Find mechanics that require strategic thinking and is hard to automate, to avoid bots topping leaderboards
- Figure out how region battles work
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from douglascdev/hashbot
-
gameOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
douglascdev/hashbot#21 ·
-
undo commandOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
douglascdev/hashbot#20 ·
-
rename commandOpen
Difficulty 3/5 1-2 days Newbie friendliness 25/100
douglascdev/hashbot#19 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
douglascdev/hashbot#18 ·
-
Prefix commandOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
douglascdev/hashbot#15 ·
All issues in douglascdev/hashbot
Similar issues
-
self-host checker: E021 bound check reads an untyped literal at i32, not the type the call bindsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
JakeChampion/lang#11055 ·
Maintainers usually reply within 1 day
-
priority: low status: ready for dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hyperledger-labs/fabric-smart-client#2033 ·
Maintainers usually reply within 1 day
-
agent-butler-finding agent-research bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
jordansmall/spindrift#4249 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
acceptance-tests phase-coding schema-coverage testing triaged
Difficulty 2/5 1-2 days Newbie friendliness 84/100
elastic/terraform-provider-elasticstack#5053 ·
Maintainers usually reply within 1 day