New bounty logic by NetsuNegi · Pull Request #2118 · Phobos-developers/Phobos

NetsuNegi · 2026-02-23T08:43:23Z

Similar to Ares' bounty logic, but with more configurable options and easier to use.
Bounty.Enable is the master switch for the new bounty logic; it must be turned on first to utilize the new bounty system.
Bounty.Enablers specifies the TechnoTypes that grant the bounty capability, not limited to buildings.
- If this list is empty, the bounty logic is enabled without requiring any prerequisite TechnoTypes.
Bounty.Multiplier is the multiplier applied to the bounty a hunter receives when a victim is killed. This is defined on the victim.
Bounty.Value is the fixed amount of funds a hunter receives when a victim is killed. This is also defined on the victim.
- If Bounty.Value is not 0, the base value is the amount set by Bounty.Value; otherwise, the base bounty value is the victim's actual cost multiplied by Bounty.Multiplier.
Bounty.KillerMultiplier is the multiplier applied to the bounty received when killing a target. This is defined on the hunter.
Bounty.Display controls whether the bounty amount is shown, displayed on the hunter.

In rulesmd.ini:

[General]
Bounty.Enable=false                 ; boolean
Bounty.Enablers=                    ; list of TechnoTypes
Bounty.Default=false                ; boolean
Bounty.Multiplier=1.0               ; double
Bounty.KillerMultiplier=1.0         ; double

[AudioVisual]
Bounty.Display=false                ; boolean
Bounty.Display.Houses=all           ; List of Affected House Enumeration (none|owner/self|allies/ally|team|enemies/enemy|all)

[SOMETECHNO]                        ; TechnoType
Bounty=                             ; boolean, default to [General] -> Bounty.Default
Bounty.Multiplier=                  ; double, default to [General] -> Bounty.Multiplier
Bounty.Multiplier.Veteran=          ; double, default to [TechnoType] -> Bounty.Multiplier
Bounty.Multiplier.Elite=            ; double, default to [TechnoType] -> Bounty.Multiplier
Bounty.Value=0                      ; integer
Bounty.Value.Veteran=               ; integer, default to [TechnoType] -> Bounty.Value
Bounty.Value.Elite=                 ; integer, default to [TechnoType] -> Bounty.Value
Bounty.KillerMultiplier=            ; double, default to [General] -> Bounty.KillerMultiplier
Bounty.KillerMultiplier.Veteran=    ; double, default to [TechnoType] -> Bounty.KillerMultiplier
Bounty.KillerMultiplier.Elite=      ; double, default to [TechnoType] -> Bounty.KillerMultiplier
Bounty.Display=                     ; boolean, default to [AudioVisual] -> Bounty.Display
Bounty.Display.Houses=              ; List of Affected House Enumeration (none|owner/self|allies/ally|team|enemies/enemy|all), default to [AudioVisual] -> Bounty.Display.Houses
Bounty.Display.Offset=0,0           ; X,Y, pixels relative to default

Do not use this alongside Ares' bounty logic; although it will not cause a crash, the hunter will receive a bounty from each logic.

github-actions · 2026-02-23T08:50:26Z

Nightly build for this pull request:

compiled-dll-1faa5f02e9d5355100d2ab63cfcc52ee0baa2b88.zip
These artifacts will expire in 90 days and will not be available for download after that time.

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.

phoboscn-bot · 2026-02-23T08:56:15Z

To Chinese users:
This pull request has been mentioned on Phobos CN. There might be relevant details there:

致中文用户：
此拉取请求已在 Phobos CN 上被提及。那里可能有相关详细信息：

https://www.phoboscn.top/t/topic/172/1

TaranDahl

Several non-essential suggestions.

TaranDahl · 2026-02-23T15:58:45Z

src/Ext/Techno/Body.cpp

+	if (pKillerTypeExt->Bounty_Display.Get(RulesExt::Global()->Bounty_Display))
+	{
+		const auto displayTo = pKillerTypeExt->Bounty_Display_Houses.Get(RulesExt::Global()->Bounty_Display_Houses);
+		FlyingStrings::AddMoneyString(value, pKiller, pKiller->Owner, displayTo, pKiller->Location, pKillerTypeExt->Bounty_Display_Offset);


I think our Helper needs to be updated. This number should allow for custom colors.

TaranDahl · 2026-02-23T15:58:53Z

docs/New-or-Enhanced-Logics.md

+- `Bounty.Value` is the fixed amount of funds a hunter receives when a victim is killed. This is also defined on the victim.
+  - If `Bounty.Multiplier` is not 0, the base bounty value is the victim's actual cost multiplied by this multiplier; otherwise, the base value is the amount set by `Bounty.Value`.
+- `Bounty.KillerMultiplier` is the multiplier applied to the bounty received when killing a target. This is defined on the hunter.
+- `Bounty.Display` controls whether the bounty amount is shown, displayed on the hunter.


I think it should be allowed to be displayed on the head of the prey.

TaranDahl · 2026-02-23T16:10:09Z

docs/New-or-Enhanced-Logics.md

  - `DisableWeapons` can be used to disable ability to fire any and all weapons.
    - On TechnoTypes with `OpenTopped=true`, `OpenTopped.CheckTransportDisableWeapons` can be set to true to make passengers not be able to fire out if transport's weapons are disabled by `DisableWeapons`.
  - `Unkillable` can be used to prevent the techno from being killed by taken damage (minimum health will be 1).
+  - `Bounty` can be used to override the option with the same name in TechnoTypes, enabling it for TechnoTypes that originally did not have the Bounty Hunter ability, or conversely, disabling it.


It would be best if the value of the holder's bounty could also be adjusted through AE.

TaranDahl · 2026-02-23T16:26:11Z

src/Ext/Techno/Hooks.cpp

+
+DEFINE_HOOK(0x702E64, TechnoClass_RegisterDestruction_Bounty, 0x6)
+{
+	GET(TechnoClass*, pKiller, EDI);


It would be best to allow the acceptance of the Killer of HouseClass.

mevitar · 2026-02-24T11:56:45Z

If Phobos' bounty logic uses Bounty=yes/no on techno just like the Ares' one, doesn't that mean activating it on a specific techno automatically activates both? Not only that, both are also using Bounty.Value=, from which i assume i would get duplicated values by default.

How is someone supposed to use only Phobos bounty when both are using same tags?
This isn't like Phobos' AttachEffect, which required the modder to specify a separate AttachEffectType the object uses, so the modder could easily tell which one is being used and where.

Either disable Ares' bounty completely when Phobos one is enabled, or make a better way for the modder to choose which one is being used (like changing it to a separate type like Phobos' AttachEffect, or change name to something else, like Pillager or NewBounty).

And i think Bounty.Default= needs to be renamed. I understand it is the default value for all techno types, but the name is too generic and surely there has to be a better name for it (something like Bounty.EnableForAll= ?).

init

e8dcf29

NetsuNegi added Needs testing ⚙️T1 T1 maintainer review is sufficient labels Feb 23, 2026

DeathFishAtEase and others added 6 commits February 23, 2026 17:03

Update New-or-Enhanced-Logics.md

8765b46

Update docs

859efe5

Bounty.Display.House→Bounty.Display.Houses

2860cc8

[doc] Bounty.Display.House→Bounty.Display.Houses

46436bd

Update New-or-Enhanced-Logics.md

1d32ec8

Resolve the alignment issue introduced by batch replacement

912d03c

TaranDahl approved these changes Feb 23, 2026

View reviewed changes

NetsuNegi and others added 4 commits February 24, 2026 07:30

update

b6fbe52

Update New-or-Enhanced-Logics.md

c5da8ab

Update New-or-Enhanced-Logics.po

bee2f2c

Update New-or-Enhanced-Logics.po

19d27ec

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Comments

New bounty logic#2118

New bounty logic#2118
NetsuNegi wants to merge 11 commits intoPhobos-developers:developfrom
NetsuNegi:feature/bounty

NetsuNegi commented Feb 23, 2026 •

edited

Loading

Uh oh!

github-actions bot commented Feb 23, 2026 •

edited

Loading

Uh oh!

phoboscn-bot commented Feb 23, 2026

Uh oh!

TaranDahl left a comment

Uh oh!

TaranDahl Feb 23, 2026

Uh oh!

TaranDahl Feb 23, 2026

Uh oh!

TaranDahl Feb 23, 2026

Uh oh!

TaranDahl Feb 23, 2026

Uh oh!

mevitar commented Feb 24, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Comments

Conversation

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

Uh oh!

Uh oh!

github-actions bot commented Feb 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

phoboscn-bot commented Feb 23, 2026

Uh oh!

TaranDahl left a comment

Choose a reason for hiding this comment

Uh oh!

TaranDahl Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

TaranDahl Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

TaranDahl Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

TaranDahl Feb 23, 2026

Choose a reason for hiding this comment

Uh oh!

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

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

NetsuNegi commented Feb 23, 2026 •

edited

Loading

github-actions bot commented Feb 23, 2026 •

edited

Loading

mevitar commented Feb 24, 2026 •

edited

Loading