aboutsummaryrefslogtreecommitdiff
path: root/sql
diff options
context:
space:
mode:
authortreeston <treeston.mmoc@gmail.com>2017-06-12 13:08:07 +0200
committertreeston <treeston.mmoc@gmail.com>2017-06-12 13:08:07 +0200
commitca0262995053e0e5baef7e97211fec8f81664ea7 (patch)
tree1791cfaa3d1c604b3ca1f4f10838e68c1c1a9553 /sql
parentd455f972f2b5f27bcb1498b53056d23de633d479 (diff)
Make some adjustments to .summon and .group summon behavior to make them more permissive:
- Now only requires the either target's group leader or target itself to be on your map - Now summons all applicable group members even if one member fails checks - No longer has some truly weird edge case instance unbind code that could cause exploit behavior (Really, I have no idea why this existed, because it certainly didn't do what it might've been meant to do.)
Diffstat (limited to 'sql')
-rw-r--r--sql/updates/world/3.3.5/2017_06_12_00_world.sql5
1 files changed, 5 insertions, 0 deletions
diff --git a/sql/updates/world/3.3.5/2017_06_12_00_world.sql b/sql/updates/world/3.3.5/2017_06_12_00_world.sql
new file mode 100644
index 00000000000..56d15d9775a
--- /dev/null
+++ b/sql/updates/world/3.3.5/2017_06_12_00_world.sql
@@ -0,0 +1,5 @@
+--
+UPDATE `trinity_string` SET `content_default`="You can only summon a player to your instance if either that player or his group leader is in your instance, too." WHERE `entry`=103;
+DELETE FROM `trinity_string` WHERE `entry`=187;
+INSERT INTO `trinity_string` (`entry`,`content_default`) VALUES
+ (187, "The group's leader is not in your instance - summoning only members that are already in your map.");