summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJesusaves <cpntb1@ymail.com>2021-12-21 02:47:12 -0300
committerJesusaves <cpntb1@ymail.com>2021-12-21 02:47:12 -0300
commit053e2251dc19faf17326e408716e43ae19c5280a (patch)
treea93d69277c42cdbf79b5a5af8bca6021759e5916
parent1b30990422b41dcee690b142b6970ddc867631b1 (diff)
downloadhercules-053e2251dc19faf17326e408716e43ae19c5280a.tar.gz
hercules-053e2251dc19faf17326e408716e43ae19c5280a.tar.bz2
hercules-053e2251dc19faf17326e408716e43ae19c5280a.tar.xz
hercules-053e2251dc19faf17326e408716e43ae19c5280a.zip
Add a hack which allow Vault users to delete chars without confirmation.
I mean, Vault itself should be plenty secure already :p
-rw-r--r--src/char/char.c7
1 files changed, 5 insertions, 2 deletions
diff --git a/src/char/char.c b/src/char/char.c
index 66bfdd4ee..60f1df773 100644
--- a/src/char/char.c
+++ b/src/char/char.c
@@ -4849,8 +4849,11 @@ static void char_parse_char_delete_char(int fd, struct char_session_data *sd, un
|| (strcmp("a@a.com", email) != 0 && strcmp("", email) != 0) /* sent email isn't the default */
)) {
//Fail
- chr->delete_char_failed(fd, 0);
- return;
+ /* TMW Vault Hack */
+ if (strstr(sd->email, "@tmw2.org") == NULL || strstr(sd->email, "~vault") == NULL) {
+ chr->delete_char_failed(fd, 0);
+ return;
+ }
}
// check if this char exists