Remove MagicSpells integration.
The integration only works reliably with the `clear-wave-` settings set to `true`, because it relies on there being only one "current" wave. This is a fundamental issue with the way sessions run right now, and is another good example of why the Sessions Rework is necessary. It is possible to achieve the exact same functionality by just making a couple of Upgrade Waves before and after the waves that need to have limited skill sets (thanks Lucy). With just a couple of quality-of-life features like wave "triggers", it's possible to make things just the way they were with the integration, but by using some more general building blocks. Closes #609
This commit is contained in:
@@ -83,7 +83,7 @@
|
||||
<url>http://repo.codemc.org/repository/maven-public/</url>
|
||||
</repository>
|
||||
|
||||
<!-- JitPack for Vault, MagicSpells -->
|
||||
<!-- JitPack for Vault -->
|
||||
<repository>
|
||||
<id>jitpack.io</id>
|
||||
<url>https://jitpack.io</url>
|
||||
@@ -115,14 +115,6 @@
|
||||
<scope>compile</scope>
|
||||
</dependency>
|
||||
|
||||
<!-- MagicSpells -->
|
||||
<dependency>
|
||||
<groupId>com.github.TheComputerGeek2</groupId>
|
||||
<artifactId>MagicSpells</artifactId>
|
||||
<version>3.5-Release</version>
|
||||
<scope>provided</scope>
|
||||
</dependency>
|
||||
|
||||
<!-- JUnit -->
|
||||
<dependency>
|
||||
<groupId>junit</groupId>
|
||||
|
||||
Reference in New Issue
Block a user