Release 1.0.0 (#27)

* [ADD] Discord System

* [REMOVE] Socket System

* [FIX] Webhook Spam

* [CHANGE] Update Webhook System

* [ADD] Github Templates

* Update Readme

* [CHANGE] Update settings loader

* Update Changelog

* [ADD] Avatar Picture

* Fix Pre-Commit Issue

* Update Changelog

Author: Geuthur

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,35 @@
+name: Bug Report
+description: File a bug report.
+title: "[BUG]: "
+labels: ["bug"]
+projects: ["eve-alert"]
+assignees:
+  - octocat
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/geuthur/EVE-Alert-Opensource/blob/main/CODE_OF_CONDUCT.md).
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/suggestion_report.yaml

@@ -0,0 +1,28 @@
+name: Suggestion Request
+description: What the program should have.
+title: "[SUGGESTION]: "
+labels: ["suggestion"]
+projects: ["eve-alert"]
+assignees:
+  - geuthur
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this suggestion request!
+  - type: textarea
+    id: suggestion
+    attributes:
+      label: Draw your suggestion
+      description: Draw your suggestion, or write code, or anything that can help us understand your suggestion.
+      placeholder: Draw your suggestion here!
+    validations:
+      required: true
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/geuthur/EVE-Alert-Opensource/blob/main/CODE_OF_CONDUCT.md).
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,18 @@
+Please include a summary of the changes and the related issue number (if applicable).
+
+## Description
+
+### Type of Changes
+Please select the type of changes made in this pull request:
+- [ ] Bug Fix
+- [ ] New Feature
+- [ ] Documentation Update
+- [ ] Other (please specify):
+
+### Checklist
+Please ensure the following before submitting your pull request:
+- [ ] I have read the [contributing guidelines](https://github.com/geuthur/EVE-Alert-Opensource/blob/main/CONTRIBUTING.md).
+- [ ] My code follows the code style of this project.
+- [ ] I have performed a self-review of my code.
+- [ ] I have commented my code where necessary.
+- [ ] All new and existing tests passed.

CHANGELOG.md

@@ -1,3 +1,23 @@
+## [1.0.0] 2025-03-30
+
+### Changed
+
+- Removed Socket System
+  - The Socket System has been removed and we now use Discord Webhook to share Intel.
+- Setting Loader
+  - Missing Keys will be created.
+- Update Dependencies
+  - Open-CV Updated to 4.11.\*
+  - ScreenInfo to 0.8.1
+  - MSS to 10.0.0
+
+### Added
+
+- Discord System
+  - All alarms are sent to a Discord webhook with the system name.
+- dhooks-lite
+  - Discord Webhook library
+
 ## [0.9.0] - 2025-01-08
 
 ### Changed

CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][mozilla coc].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][faq]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[faq]: https://www.contributor-covenant.org/faq
+[homepage]: https://www.contributor-covenant.org
+[mozilla coc]: https://github.com/mozilla/diversity
+[translations]: https://www.contributor-covenant.org/translations
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html

CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# Contributing to This Project
+
+Thank you for considering contributing to our project! Here are some guidelines to help you get started.
+
+## Getting Started
+
+1. **Fork the repository**: Click the "Fork" button at the top right of the repository page.
+
+1. **Clone your fork**: Clone your forked repository to your local machine.
+
+   ```sh
+   git clone https://github.com/geuthur/EVE-Alert-Opensource.git
+   ```
+
+1. **Set up the upstream remote**: Add the original repository as a remote to keep your fork up to date.
+
+   ```sh
+   git remote add upstream https://github.com/geuthur/EVE-Alert-Opensource.git
+   ```
+
+## Pre-commit Hooks
+
+We use pre-commit hooks to ensure code quality and consistency. Please make sure you have pre-commit installed and set up.
+
+1. **Install pre-commit**: If you don't have pre-commit installed, you can install it using pip.
+
+   ```sh
+   pip install pre-commit
+   ```
+
+1. **Install the hooks**: Run the following command to install the pre-commit hooks.
+
+   ```sh
+   pre-commit install
+   ```
+
+1. **Use Pre Commit**
+
+   Check all files
+
+   ```sh
+   pre-commit run --all-files
+   ```
+
+   If you want only one of the hooks like `eslint`
+
+   ```sh
+   pre-commit run eslint
+   ```
+
+## Branching und Contributing via Pull Requests
+
+Before creating a pull request, make sure that you have forked the repository and are working on your fork. This ensures that your changes are isolated and do not affect the original repository until they are reviewed and merged.
+
+The `master` branch should always be kept up to date to avoid conflicts. This means that all changes integrated into the `master` branch should be thoroughly reviewed and tested before being merged. Regular updates and synchronizations with the `master` branch help to identify and resolve potential conflicts early.
+
+Before creating a new feature, an issue should always be opened first. This serves to start a discussion about the planned feature and ensure that all team members are informed about the planned changes. Through discussion, potential problems and improvements can be identified and considered early. This promotes a collaborative working approach and contributes to the quality and consistency of the project.

README.md

@@ -12,9 +12,7 @@ EVE Alert - Check every 1-3 seconds if the Local has an Enemy or Neutral in Syst
   - [Features](#features)
   - [Download](#step1)
   - [Detection](#detection)
-  - [Socket System](#socket)
-    - [Server - Main Program](#server)
-    - [Client - Listener](#client)
+  - [Discord Webhook](#webhook)
   - [Showcase](#showcase)
   - [Donation](#donation)
   - [Terms](#terms)
@@ -27,11 +25,7 @@ EVE Alert - Check every 1-3 seconds if the Local has an Enemy or Neutral in Syst
 - Start/Stop System
 - Monitoring Region in real-time (also possible to stream via Discord for friends)
 - Faction Spawn Detection - Now you can set a Faction Spawn Detection and it will play a sound if a faction is in Site (can also used for other thing like active modules or something)
-- The Socket System allows you to have one server and multiple clients that can connect to it to receive alarms.
-
-## Upcoming Features
-
-- Discord Webhook support
+- Webhook System allows to share alarms into Discord Webhook to create a Intel System anonymous.
 
 ### Download Version<a name="step1"></a>
 
@@ -45,30 +39,15 @@ Go to [the releases page](https://github.com/Geuthur/EVE-Alert-Opensource/releas
 If you want more, simply add more images to the "img/" folder with naming image_1, image_2, image_3, etc.\
 Note: If you have different UI Scaling you need to add these images to the img folder like the `image_1_90%`
 
-## Server Usage<a name="server"></a>
-
-> [!NOTE]
-> **This Version is for Single User!**
-
-The server is responsible for sending messages to the connected clients. It can send two types of messages: Normal and Alarm. When an Alarm message is sent, all connected clients will receive it and can take appropriate actions, such as playing a sound.
-
-- Simply launch Server.exe, and a menu will appear. You can configure all your settings there. Afterward, click on "Start."
-- If the Alert doesn't respond to the local chat, you can reduce the detection accuracy or double-check if you've set the region correctly.
-- If both settings are 100% accurate and your interface is not blurred, make a new screenshot from your neutral symbol and try it with your own image
-- You can edit all images & sounds by yourself only the name must be the same
-
-Optional:
-
-- Activate Socket Server for Broadcast Mode
-- Mute Alarm for Just Broadcast
+## Discord Webhook Usage (optinal)<a name="webhook"></a>
 
-## Client Usage<a name="client"></a>
+The webhook is responsible for sending messages to a Discord Server.
 
-> [!NOTE]
-> To Use the Client Version you need at least 1 Active Server!
+- Open The Setting Menu and put a Discord Webhook URL in the Webhook Field
+- Setup a System Name: `Jita 4-4`
+- You can also mute the Alarm sound by checking the Mute Alarm Checkbox
 
-- The client program can be used to connect to a socket server and continuously receives messages. The messages can be in one of two states: Normal or Alarm.
-- When the client receives an Alarm message, it plays a sound.
+If there is a problem with the webhook, the webhook system is automatically deactivated.
 
 ## Showcase<a name="showcase"></a>
 

evealert/__init__.py

@@ -1,4 +1,4 @@
 """Initialize the app"""
 
-__version__ = "0.9.0"
+__version__ = "1.0.0"
 __title__ = "EVE Alert"