Merge branch 'dev'

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,27 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[BUG]"
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: "[FEATURE]"
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/pull_request_template.md

@@ -0,0 +1,37 @@
+<!-- Be sure that your work is based off `dev` branch. -->
+
+## Description
+
+Please include a summary of the changes and the related issue or feature.
+
+**NOTE**: The merge process is as follows:
+- Your pull request should be directed to `dev` branch. 
+- When it will be merged in `dev`, we will compile and merge within a `release/` branch and then push into `main` for final release.
+
+Fixes # (issue)
+
+## Type of change
+
+Please select the right one.
+
+- [ ] (Patch) Bug fix (non-breaking change which fixes an issue)
+- [ ] (Minor) New feature (non-breaking change which adds functionality)
+- [ ] (Major) Breaking change (fix or feature that would cause existing functionality to not work as expected and requires modifications in existing functionality to ensure expected behavior.)
+- [ ] This change requires a documentation update
+
+## Which package(s) are impacted ?
+
+  - [ ] duel
+  - [ ] cmd/Duels
+  - [ ] cmd/refService
+  - [ ] Misc (documentation, etc...)
+
+## Checklist:
+
+- [ ] I have performed a self-review of my code
+- [ ] I have commented my code
+- [ ] My changes generate no new warnings
+
+## License
+
+I am contributing & releasing the code under the [MIT License](https://raw.githubusercontent.com/SixofClubsss/Duels/main/LICENSE).

CHANGELOG.md

@@ -0,0 +1,24 @@
+# Changelog
+
+This file lists the changes to Duels repo with each version.
+
+## 0.1.0 - December 23 2023
+
+Duels v0.1.0 is a showdown style game built on DERO, essentially over or under determined on chain
+
+### Features
+
+* Imported into dReams and stand alone dApp
+* Users can duel Dero assets  
+* Users can equip their characters with items
+* Regular, death match and hardcore game modes
+* Ref oversees regular mode and gives odds based on asset stats
+* Win defeated characters items in death match 
+* Character graveyard for death match defeats
+* Hardcore mode is no odds or ref, quick and simple
+* Hardcore mode and death match can be combined
+* Leader board to track player wins and losses
+* Auto claim NFAs
+* refService `cmd` for cli ref service
+* Character collections: Dero Desperados, High Strangeness, Death By Cupcake
+* Item collections: Desperado Guns

README.md

@@ -1,7 +1,7 @@
 # Duels
 Dero asset duels.
 
-Written in Go and using [Fyne Toolkit](https://fyne.io/), **Duels** is built on Dero's private L1. Powered by [Gnomon](https://github.com/civilware/Gnomon) and [dReams](https://github.com/dReam-dApps/dReams), **Duels** allows Dero users to pit their Dero assets against each other in PvP duels. Modeled after the duels that took place in the days of wild west, **Duels** has a variety of game modes to choose from. 
+Written in Go and using [Fyne Toolkit](https://fyne.io/), **Duels** is built on Dero's private L1. Powered by [Gnomon](https://github.com/civilware/Gnomon) and [dReams](https://github.com/dReam-dApps/dReams), **Duels** allows Dero users to pit their Dero assets against each other in PvP duels. Modeled after the duels that took place in the days of wild west, **Duels** has a variety of game modes to choose from. The game mechanics are essentially higher/lower, where the outcome is derived on chain.
 
 
 ![goMod](https://img.shields.io/github/go-mod/go-version/SixofClubsss/Duels.svg)![goReport](https://goreportcard.com/badge/github.com/SixofClubsss/Duels)[![goDoc](https://img.shields.io/badge/godoc-reference-blue.svg)](https://pkg.go.dev/github.com/SixofClubsss/Duels)
@@ -11,17 +11,18 @@ Duels dApp with full features is available for download from [dReams](https://dr
 ![windowsOS](https://raw.githubusercontent.com/SixofClubsss/dreamdappsite/main/assets/os-windows-green.svg)![macOS](https://raw.githubusercontent.com/SixofClubsss/dreamdappsite/main/assets/os-macOS-green.svg)![linuxOS](https://raw.githubusercontent.com/SixofClubsss/dreamdappsite/main/assets/os-linux-green.svg)
 
 ### Features
-- Regular Duels
-- Death match Duels
-- Hardcore Duels
+- Regular Duels (odds used, requires ref)
+- Death match Duels (winner gets defeated characters items)
+- Hardcore Duels (no odds or ref, quick pace)
+- Combine hardcore and death match modes
+- Graveyard with defeated character revivals
 - Outcome determined by SC
 - Character and item assets with ranking system
 - Payout odds determined by ranking system
-- Graveyard with character revivals
 - Leader board to track wins/loses
 - Multiple currencies supported
 - Auto claim NFA assets
-- Local DB image storage
+- Local DB storage
 - Ref service
 
 ### Build