diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md
index d26b1b1c..d9ef2ced 100644
--- a/PULL_REQUEST_TEMPLATE.md
+++ b/PULL_REQUEST_TEMPLATE.md
@@ -1,124 +1,103 @@
-# Pull Request
+<!--
+Thank you for contributing to mod-playerbots, please make sure that you...
+1. Submit your PR to the test-staging branch, not master.
+2. Read the guidelines below before submitting.
+3. Don't delete parts of this template.
 
-Describe what this change does and why it is needed...
+DESIGN PHILOSOPHY: We prioritize STABILITY, PERFORMANCE, AND PREDICTABILITY over behavioral realism.
 
----
+Every action and decision executes PER BOT AND PER TRIGGER. Small increases in logic complexity scale
+poorly across thousands of bots and negatively affect all. We prioritize a stable system over a smarter
+one. Bots don't need to behave perfectly; believable behavior is the goal, not human simulation.
+Default behavior must be cheap in processing; expensive behavior must be opt-in.
 
-## Design Philosophy
+Before submitting, make sure your changes aligns with these principles.
+-->
 
-We prioritize **stability, performance, and predictability** over behavioral realism.  
-Complex player-mimicking logic is intentionally limited due to its negative impact on scalability, maintainability, and
-long-term robustness.
+## Pull Request Description
+<!-- Describe what this change does and why it is needed -->
 
-Excessive processing overhead can lead to server hiccups, increased CPU usage, and degraded performance for all
-participants. Because every action and
-decision tree is executed **per bot and per trigger**, even small increases in logic complexity can scale poorly and
-negatively affect both players and
-world (random) bots. Bots are not expected to behave perfectly, and perfect simulation of human decision-making is not a
-project goal. Increased behavioral
-realism often introduces disproportionate cost, reduced predictability, and significantly higher maintenance overhead.
 
-Every additional branch of logic increases long-term responsibility. All decision paths must be tested, validated, and
-maintained continuously as the system evolves.
-If advanced or AI-intensive behavior is introduced, the **default configuration must remain the lightweight decision
-model**. More complex behavior should only be
-available as an **explicit opt-in option**, clearly documented as having a measurable performance cost.
-
-Principles:
-
-- **Stability before intelligence**  
-  A stable system is always preferred over a smarter one.
-
-- **Performance is a shared resource**  
-  Any increase in bot cost affects all players and all bots.
-
-- **Simple logic scales better than smart logic**  
-  Predictable behavior under load is more valuable than perfect decisions.
-
-- **Complexity must justify itself**  
-  If a feature cannot clearly explain its cost, it should not exist.
-
-- **Defaults must be cheap**  
-  Expensive behavior must always be optional and clearly communicated.
-
-- **Bots should look reasonable, not perfect**  
-  The goal is believable behavior, not human simulation.
-
-Before submitting, confirm that this change aligns with those principles.
-
----
 
 ## Feature Evaluation
+<!--
+If your PR is very minimal (comment typo, wrong ID reference, etc), and it is very obvious it will not have
+any impact on performance, you may skip these question. If necessary, a maintainer may ask you for them later.
+-->
 
-Please answer the following:
+<!-- Please answer the following: -->
+- Describe the **minimum logic** required to achieve the intended behavior.
+- Describe the **processing cost** when this logic executes across many bots.
 
-- Describe the **minimum logic** required to achieve the intended behavior?
-- Describe the **cheapest implementation** that produces an acceptable result?
-- Describe the **runtime cost** when this logic executes across many bots?
 
----
 
 ## How to Test the Changes
+<!--
+- Step-by-step instructions to test the change.
+- Any required setup (e.g. multiple players, number of bots, specific configuration).
+- Expected behavior and how to verify it.
+-->
 
-- Step-by-step instructions to test the change
-- Any required setup (e.g. multiple players, bots, specific configuration)
-- Expected behavior and how to verify it
 
-## Complexity & Impact
 
-Does this change add new decision branches?
-- - [ ] No
-- - [ ] Yes (**explain below**)
+## Impact Assessment
+<!-- As a generic test, before and after measure of pmon (playerbot pmon tick) can help you here. -->
+- Does this change increase per-bot/per-tick processing or risk scaling poorly with thousands of bots?
+    - [ ] No, not at all
+    - [ ] Minimal impact (**explain below**)
+    - [ ] Moderate impact (**explain below**)
 
-Does this change increase per-bot or per-tick processing?
-- - [ ] No
-- - [ ] Yes (**describe and justify impact**)
 
-Could this logic scale poorly under load?
-- - [ ] No
-- - [ ] Yes (**explain why**)
----
 
-## Defaults & Configuration
+- Does this change modify default bot behavior?
+    - [ ] No
+    - [ ] Yes (**explain why**)
 
-Does this change modify default bot behavior?
-- - [ ] No
-- - [ ] Yes (**explain why**)
 
-If this introduces more advanced or AI-heavy logic:
-- - [ ] Lightweight mode remains the default
-- - [ ] More complex behavior is optional and thereby configurable
----
+
+- Does this change add new decision branches or increase maintenance complexity?
+    - [ ] No
+    - [ ] Yes (**explain below**)
+
+
+
+## Messages to Translate
+<!--
+Bot messages have to be translatable, but you don't need to do the translations here. You only need to make sure
+the message is in a translatable format, and list in the table the message_key and the default English message.
+Search for GetBotTextOrDefault in the codebase for examples.
+-->
+Does this change add bot messages to translate?
+- [ ] No
+- [ ] Yes (**list messages in the table**)
+
+| Message key  | Default message |
+| --------------- | ------------------ |
+|			 |			      |
+|			 |			      |
 
 ## AI Assistance
-
-Was AI assistance (e.g. ChatGPT or similar tools) used while working on this change?
-- - [ ] No
-- - [ ] Yes (**explain below**)
-
-If yes, please specify:
-
-- AI tool or model used (e.g. ChatGPT, GPT-4, Claude, etc.)
-- Purpose of usage (e.g. brainstorming, refactoring, documentation, code generation)
-- Which parts of the change were influenced or generated
-- Whether the result was manually reviewed and adapted
-
+<!--
 AI assistance is allowed, but all submitted code must be fully understood, reviewed, and owned by the contributor.
-Any AI-influenced changes must be verified against existing CORE and PB logic. We expect contributors to be honest
-about what they do and do not understand.
+We expect contributors to be honest about what they do and do not understand.
+-->
+Was AI assistance used while working on this change?
+- [ ] No
+- [ ] Yes (**explain below**)
+<!--
+If yes, please specify:
+- Purpose of usage (e.g. brainstorming, refactoring, documentation, code generation).
+- Which parts of the change were influenced or generated, and whether it was thoroughly reviewed.
+-->
+
 
----
 
 ## Final Checklist
 
-- - [ ] Stability is not compromised
-- - [ ] Performance impact is understood, tested, and acceptable
-- - [ ] Added logic complexity is justified and explained
-- - [ ] Documentation updated if needed
-
----
+- [ ] Stability is not compromised.
+- [ ] Performance impact is understood, tested, and acceptable.
+- [ ] Added logic complexity is justified and explained.
+- [ ] Documentation updated if needed (Conf comments, WiKi commands).
 
 ## Notes for Reviewers
-
-Anything that significantly improves realism at the cost of stability or performance should be carefully discussed
-before merging.
+<!-- Anything else that's helpful to review or test your pull request. -->