Update NationsGloryJava.yml by baba33mrt · Pull Request #1 · NationsTools/Log-Analyzer-Patterns

baba33mrt · 2026-01-19T14:54:55Z

Type de modification

Coche au moins une case

Ajout de pattern
Correction de pattern existant
Amélioration / clarification
Autre (à préciser)

Description

Explique clairement :

le ou les logs concernés
Ajout des logs suivantes :
- Actions / enchères
  - New
  - Bid
  - End
  - Refund
  - Cancelled
- ChestShop
  - Transaction
- AdminShop
  - Transactions
  - Catalog
- Wars
  - Add
  - start
  - surrender
  - status change
  - won
  - warzone add
- Economy & countries
  - country buy
  - country action buy
  - country found
  - country new leader
  - colony request
- Powerboost
  - PowerBoost player
  - PowerBoost country
- Meteor
  - spawn
- Access P
  - Set
  - Remove
- Divers
  - duel win
  - restricted item
  - missile launch
- Session
  - Déconnexion

Ajouts basé sur le script python d'akael V.2023 , des modifications de logs ont du avoir lieu je vous laisses me le faire remonter

Impact potentiel

Aucun impact sur les patterns existants
Impact rétro-compatible
Risque de rupture de compatibilité (à justifier)

Justification (si nécessaire) : /

Checklist

Le fichier YAML est valide
Aucune clé dupliquée
Le pattern est dans la bonne catégorie
Le nom du pattern est explicite et en snake_case
Les variables utilisées sont cohérentes et explicites
La modification est justifiée (si pattern existant)

Informations complémentaires

Toute information utile à la revue : Ajouts basé sur le script python d'akael V.2023 , des modifications de logs ont du avoir lieu je vous laisses me le faire remonter

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 70b6c3be72

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-01-19T14:57:27Z

patterns/NationsGloryJava.yml

+# ChestShop
+# ===========================
+chestshop_transaction:
+  pattern: "{timestamp} [ChestShop] {player} {action} {qty} {item} for {price} {direction} {target} at [world] {x}, {y}, {z}"


Capture ChestShop world name instead of literal

This pattern hard-codes at [world], so it only matches transactions that occur in a world literally named “world”. ChestShop logs include the world name in brackets (e.g., at [world_nether] …), and those entries will not parse with this pattern, causing missed transactions whenever servers use non-default world names. Consider capturing the world token (e.g., [{world}]) so multi-world logs still match.

Useful? React with 👍 / 👎.

Copilot

Pull request overview

This PR adds 30 new log patterns to the NationsGloryJava.yml file for parsing additional server logs from the NationsGlory Minecraft server plugin. The patterns are based on a Python script from akael V.2023 and cover various game mechanics including auctions, shops, wars, economy, and player sessions.

Changes:

Added patterns for auction system events (new, bid, end, refund, cancelled)
Added patterns for shop transactions (ChestShop, AdminShop, Catalog)
Added patterns for war-related events (add, start, surrender, status changes, warzone)
Added patterns for economy and country management (purchases, founding, leadership changes, colonies)
Added patterns for miscellaneous events (powerboosts, meteors, access control, duels, missiles, player sessions)

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

patterns/NationsGloryJava.yml

Copilot · 2026-01-19T14:59:25Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} [Auction] New Player auction {details}"
+
+auction_bid:
+  pattern: "{timestamp} [Auction] New Player bid {details}"
+
+auction_end:
+  pattern: "{timestamp} [Auction] End of auction {details}"
+
+auction_refund:
+  pattern: "{timestamp} [Auction] Refund {details}"
+
+auction_cancelled:
+  pattern: "{timestamp} [Auction] CANCELLED {details}"


Consider providing more specific variable names instead of the generic {details} placeholder. Other patterns in the file use explicit variables (e.g., {player}, {country}, {amount}) which makes log parsing more structured and useful. For example, this could be parsed into specific fields like {auction_id}, {item}, {price}, {player}, etc.

Les enchères n'existe plus, plus aucune log sur ce système

Copilot · 2026-01-19T14:59:25Z

patterns/NationsGloryJava.yml

+
+# ===========================
+# ChestShop
+# ===========================


The pattern variable {direction} is ambiguous. Consider using a more descriptive name like {transaction_type} or clarifying in documentation what values this field represents (e.g., "to"/"from", "bought"/"sold", etc.).

Suggested change

# ===========================

# ===========================

# {direction}: direction of the transaction, e.g. "to"/"from" the target player or shop.

Copilot · 2026-01-19T14:59:25Z

patterns/NationsGloryJava.yml

+adminshop_transaction:
+  pattern: "{timestamp} {player} {details} from Adminshop"
+
+adminshop_transaction_lower:
+  pattern: "{timestamp} {player} {details} from adminshop"


Inconsistent capitalization between patterns. Line 209 uses "Adminshop" while line 212 uses "adminshop" in the pattern text. If these represent the same log source, they should use consistent capitalization. If they represent different log formats from the server, consider using more distinct pattern names to clarify the difference.

Update depuis le catalogue :
{timestamp} [INFO] [NationsGUI] [Catalog] Player {player} bought the item {id} {quantity} for {price}$ (including delivery {tax}$) to player Bank:

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AirrOne · 2026-02-01T02:34:28Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} {player} {details} from adminshop"
+
+catalog_transaction:
+  pattern: "{timestamp} [Catalog] {details}"


Même chose que pour l'adminshop puisque tout est catalogue :
{timestamp} [INFO] [NationsGUI] [Catalog] Player {player} bought the item {id} {quantity} for {price}$ (including delivery {tax}$) to player Bank:

AirrOne · 2026-02-01T02:39:25Z

patterns/NationsGloryJava.yml

+# War / Warzone
+# ===========================
+war_add:
+  pattern: "{timestamp} Add war {details}"


Update :
{timestamp} [INFO] [NationsUtils] Add war event {war_reason} between {country_a} and {country_b}

AirrOne · 2026-02-01T02:51:20Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} Add war {details}"
+
+war_start:
+  pattern: "{timestamp} START WAR {details}"


Détails :
{timestamp} [INFO] [NationsGUI] START WAR between {country_a} and {country_b} for reason {reason}

AirrOne · 2026-02-01T02:53:06Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} START WAR {details}"
+
+war_surrender:
+  pattern: "{timestamp} SURREND WAR {details}"


Détails :
{timestamp} [INFO] [NationsGUI] {country_a} SURREND WAR AGAINST {country_b} APPLY REWARDS : {reward_type}#{amount}

AirrOne · 2026-02-01T03:13:13Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} SURREND WAR {details}"
+
+war_status_change:
+  pattern: "{timestamp} Change status of war request between {country_a} and {country_b} to {status}"


Update :
{timestamp} Change status of war request between {country_a} and {country_b} by {player} to {status}

AirrOne · 2026-02-01T03:14:55Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} Change status of war request between {country_a} and {country_b} to {status}"
+
+war_won:
+  pattern: "{timestamp} War won {details}"


Détails :
{timestamp} [INFO] [NationsUtils] War won by {country_a} against {country_b}

AirrOne · 2026-02-01T03:17:02Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} War won {details}"
+
+warzone_add:
+  pattern: "{timestamp} [WarZone] Add {details}"


3 formes différentes :
{timestamp} [INFO] [WarZone] Add 0.25 skill multiplier to {country}
{timestamp} [INFO] [WarZone] Add 1.0 power to {country}
{timestamp} [INFO] [WarZone] Le pays {country} vient de recevoir un powerboost de 1.0 de la warzone.

AirrOne · 2026-02-01T03:33:46Z

patterns/NationsGloryJava.yml

+# Economie / Pays
+# ===========================
+country_buy:
+  pattern: "{timestamp} ACHAT PAYS {details}"


Détails :
{timestamp} [INFO] ACHAT PAYS {country} PAR {pseudo} POUR {amount}$

AirrOne · 2026-02-01T03:40:53Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} ACHAT PAYS {details}"
+
+country_action_buy:
+  pattern: "{timestamp} ACHAT ACTION : {details}"


Détails :
{timetamp} [INFO] [NationsGUI] ACHAT ACTION : {country_a} ({player}) buy action of {country_b }for {price}$

AirrOne · 2026-02-01T03:47:51Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} {player} est le nouveau dirigeant du pays {country}"
+
+colony_request:
+  pattern: "{timestamp} {player} vient de faire une demande de colonie sur {country}"


Update :
N'existe plus, car les colonies ont disparues

AirrOne · 2026-02-01T03:51:53Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} POWERBOOST DE {player} {details}"
+
+powerboost_country:
+  pattern: "{timestamp} Powerboost to {country} {details}"


Détails :
Je n'ai trouvé aucune logs concernant les powerboost joueur/pays hors warzone

AirrOne · 2026-02-01T04:12:27Z

patterns/NationsGloryJava.yml

+# Meteore
+# ===========================
+meteor_spawn:
+  pattern: "{timestamp} METEOR SPAWNED IN {details}"


Détails :
{timestamp} [INFO] METEOR SPAWNED IN {planet} on player {player} at {x}, {y}, {z}

AirrOne · 2026-02-01T04:13:15Z

patterns/NationsGloryJava.yml

+# Access / Permissions
+# ===========================
+access_set:
+  pattern: "{timestamp} {player} set access to player {target} {details}"


Détails :
{timestamp} [INFO] [Factions] Player {player} set access to player {player} in chunk {x}, {z} to true

AirrOne · 2026-02-01T04:13:30Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} {player} set access to player {target} {details}"
+
+access_remove:
+  pattern: "{timestamp} {player} remove access to player {target} {details}"


Détails :
{timestamp} [INFO] [Factions] Player {player} remove access to player {player} in chunk {x}, {z} to false

AirrOne · 2026-02-01T04:15:48Z

patterns/NationsGloryJava.yml

+# Divers
+# ===========================
+duel_win:
+  pattern: "{timestamp} AFTER WIN DUEL {details}"


Update :
Les logs duel ne sont plus qu'au lancement et non à la fin
{timestamp} [INFO] START DUEL {player_a} vs {player_b} BET {amount}

AirrOne · 2026-02-01T04:27:16Z

patterns/NationsGloryJava.yml

+  pattern: "{timestamp} AFTER WIN DUEL {details}"
+
+restricted_item_interaction:
+  pattern: "{timestamp} {player} interacts with restricted item {details}"


Détails :
{timestamp} [INFO] [NationsUtils] Player {player} interacts with restricted item {id}

AirrOne · 2026-02-01T04:31:46Z

patterns/NationsGloryJava.yml

+# Player session
+# ===========================
+player_left:
+  pattern: "{timestamp} [INFO] {player} left the game."


Détails :
deconnection : "{timestamp} [INFO] §7[*banner id="minus"]§7 {player} ({number}/300)

AirrOne

Quelques logs nécessite une mise à jour et certaines ne sont plus existantes

Update NationsGloryJava.yml

70b6c3b

baba33mrt requested a review from Copilot January 19, 2026 14:55

Copilot started reviewing on behalf of baba33mrt January 19, 2026 14:55 View session

chatgpt-codex-connector bot reviewed Jan 19, 2026

View reviewed changes

Copilot AI reviewed Jan 19, 2026

View reviewed changes

Update patterns/NationsGloryJava.yml

3180e5e

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

AirrOne reviewed Feb 1, 2026

View reviewed changes

AirrOne suggested changes Feb 1, 2026

View reviewed changes

	# ===========================
	# ===========================
	# {direction}: direction of the transaction, e.g. "to"/"from" the target player or shop.

Conversation

baba33mrt commented Jan 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Type de modification

Description

Impact potentiel

Checklist

Informations complémentaires

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Jan 19, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Copilot AI Jan 19, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 19, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 19, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AirrOne Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AirrOne Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AirrOne Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AirrOne Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AirrOne left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

baba33mrt commented Jan 19, 2026 •

edited

Loading

AirrOne Feb 1, 2026 •

edited

Loading

AirrOne Feb 1, 2026 •

edited

Loading

AirrOne Feb 1, 2026 •

edited

Loading

AirrOne Feb 1, 2026 •

edited

Loading