Skip to content

Commit

Permalink
Fixed the ipintel subsystem not initializing (#82936)
Browse files Browse the repository at this point in the history
## About The Pull Request
Subsystem had the SS_INIT_NO_NEED inside of its subsystem flags. This is
not a flag and has a value of 3, which includes the SS_NO_INIT and
SS_NO_FIRE flags, which stopped it from initializing.
The subsystem has things it needs to do in init, so I've replaced this
flag with SS_OK_TO_FAIL_INIT so that it can pass unit tests, but still
be okay to fail.

## Why It's Good For The Game
Fixes the ipintel subsystem not working.

## Changelog
:cl:
fix: Fixed the ipintel subsystem not working.
/:cl:

---------

Co-authored-by: Watermelon914 <3052169-Watermelon914@users.noreply.gitlab.com>
  • Loading branch information
Watermelon914 and Watermelon914 committed May 1, 2024
1 parent 5aae4a3 commit 24bc322
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion code/controllers/subsystem/ipintel.dm
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
SUBSYSTEM_DEF(ipintel)
name = "XKeyScore"
init_order = INIT_ORDER_XKEYSCORE
flags = SS_INIT_NO_NEED|SS_NO_FIRE
flags = SS_OK_TO_FAIL_INIT|SS_NO_FIRE
/// The threshold for probability to be considered a VPN and/or bad IP
var/probability_threshold
/// The email used in conjuction with https://check.getipintel.net/check.php
Expand Down

0 comments on commit 24bc322

Please sign in to comment.