7e1fff7105
Release v3.1.1
2024-03-24 11:16:01 +01:00
af4cd8de3e
Bump org.apache.maven.plugins:maven-shade-plugin from 3.5.1 to 3.5.2 ( #39 )
...
Bumps [org.apache.maven.plugins:maven-shade-plugin](https://github.com/apache/maven-shade-plugin ) from 3.5.1 to 3.5.2.
- [Release notes](https://github.com/apache/maven-shade-plugin/releases )
- [Commits](https://github.com/apache/maven-shade-plugin/compare/maven-shade-plugin-3.5.1...maven-shade-plugin-3.5.2 )
---
updated-dependencies:
- dependency-name: org.apache.maven.plugins:maven-shade-plugin
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-03-01 13:28:46 +01:00
ca28ff77ae
Release v3.1.0
2024-01-13 21:16:41 +01:00
e5b48b624f
Upgrade Craftaro Core (+dynamic library loading; +MC 1.20.4 support)
...
Notable changes:
* Spigot 1.20.3/3 compatibility
* dynamic library/dependency loading
* Smaller plugin jar size
2024-01-13 21:16:41 +01:00
829e97e5e2
Release v3.0.0-b3-SNAPSHOT
2024-01-13 17:01:22 +01:00
95b128d73d
fix: Properly migrate the database related code to the new core's API
...
See previously commits for context
tl;dr
The database migration introduced a lot of changed behaviour and breaking changes.
The plugin essentially could never have worked and nobody reported the issue (or tested it).
I've completely redone the code migration, keeping changes for the plugin internals to a minimum.
Hopefully I didn't overlook anything...
2024-01-13 17:01:22 +01:00
f3377b08f9
Revert "Updates to new database system"
...
This reverts commit f3c8778ad2
2024-01-13 17:01:22 +01:00
b4c5282990
Revert "Make database migrations compatible with latest CraftaroCore snapshot"
...
This reverts commit 22c99005dd
2024-01-13 17:01:22 +01:00
fadb84f2a9
Revert "fix: A lot of issues introduced after migrating to the new database API"
...
This reverts commit 2eec844447
2024-01-13 17:01:22 +01:00
2eec844447
fix: A lot of issues introduced after migrating to the new database API
...
The new database API introduced a lot of breaking changes and changed behaviour sadly.
When migrating this plugin to the new API these were not taken into account properly and
essentially broke the whole database/storage layer of the plugin.
* SQL statements that were valid in SQLite but are not in H2, which is now the default
* H2 jdbc driver not being shaded into the final jar
* catching exceptions, logging a message, and then continuing code execution (in the core)
* introducing race conditions
* ...
These fixes sometimes rely on the non-multi-threaded APIs provided now which will most certaintly
come with a performance hit on larger servers.
But at least it works again... tbh I do not really want to spend too much time fixing this stuff...
A potential issue that still exists in the use of `DataManager#getNextId` in `AnchorManagerImpl`.
Right now it returns a value based on the largest ID currently in the database – Completely circumventing
the whole auto_increment characteristic of the table schema...
This is another changed behaviour that gets introduced opening the possibility for conflicting IDs
*outside* of the database table itself. The ID can be used as a reference in other places
2023-10-24 01:44:00 +02:00
9e850c5a49
Release v3.0.0-b2-SNAPSHOT
2023-10-23 17:57:47 +02:00
22c99005dd
Make database migrations compatible with latest CraftaroCore snapshot
2023-10-23 16:49:59 +02:00
ef6f4a8c8c
Bump org.apache.maven.plugins:maven-shade-plugin from 3.5.0 to 3.5.1 ( #31 )
...
Bumps [org.apache.maven.plugins:maven-shade-plugin](https://github.com/apache/maven-shade-plugin ) from 3.5.0 to 3.5.1.
- [Release notes](https://github.com/apache/maven-shade-plugin/releases )
- [Commits](https://github.com/apache/maven-shade-plugin/compare/maven-shade-plugin-3.5.0...maven-shade-plugin-3.5.1 )
---
updated-dependencies:
- dependency-name: org.apache.maven.plugins:maven-shade-plugin
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-10-09 12:34:57 +02:00
330164ae33
Bump maven-shade-plugin from 3.4.1 to 3.5.0
...
Bumps [maven-shade-plugin](https://github.com/apache/maven-shade-plugin ) from 3.4.1 to 3.5.0.
- [Release notes](https://github.com/apache/maven-shade-plugin/releases )
- [Commits](https://github.com/apache/maven-shade-plugin/compare/maven-shade-plugin-3.4.1...maven-shade-plugin-3.5.0 )
---
updated-dependencies:
- dependency-name: org.apache.maven.plugins:maven-shade-plugin
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
2023-08-03 19:59:13 +02:00
9863b93b41
Fixes method names
2023-08-02 17:46:30 +02:00
f3c8778ad2
Updates to new database system
2023-08-02 17:20:52 +02:00
8bcfca0292
Migrate usage of CompatibleSound to XSound in the CraftaroCore-Snapshot
2023-06-24 20:38:29 +02:00
5622e86e0f
Changes Songoda to Craftaro in EpicAnchors command
2023-06-24 11:47:23 +02:00
a2ed4c8656
Fix final plugin jar's name being suffixed with '-Plugin'
...
The suffix comes from the module itself but this is the main artifact of the project.
2023-06-24 11:28:44 +02:00
3967209265
Moved all classes from`com.songoda` package to `com.craftaro` package
2023-06-24 11:27:25 +02:00
f82486aecb
Sets the plugin's version to v3.0.0-SNAPSHOT
2023-06-24 11:00:53 +02:00
da0e877d03
Fixes compatibility with DecentHolograms
2023-06-24 10:59:05 +02:00
dea440732e
Make the plugin compatible with the latest Core-Snapshot build
...
I've replaced CompatibleMaterial with a library adding XMaterial.
2023-06-24 10:57:14 +02:00
bbfd62c1d3
Restructures the code and add classes/interfaces to the API module
...
I tried creating a usable API module containing everything important without introducing
too many changes that cost time and might confuse people when migration to the new module.
We have limited time right now and need to push the 1.20 update... So no additional thoughts on
the API design (so I can regret it in the somewhat near future \o/)
2023-06-24 10:51:11 +02:00
da2e999ef9
Change the project structure to allow a dedicated API module to exist
2023-06-21 15:05:48 +02:00
6ac0814358
Removed Useless API layer and hook handler.
2019-06-08 16:24:44 -04:00
fc132d7c97
Added metrics & updated spawners support.
2019-06-02 20:33:51 -04:00
9c817c07e5
Nice... Work ;-;
2019-05-22 02:18:41 -04:00
9d9af620ef
Nice work.
2019-05-22 02:14:24 -04:00
164e4e995d
Fix for 1.8, worldguard 6 support, fix epicspawners hard dependency
2019-05-11 02:15:40 -06:00
2664203c1a
Version
2019-05-03 21:51:22 -04:00
da929adc0b
Fix for 1.12-
2019-05-03 21:48:52 -04:00
ffa4f86167
Redid GUI system which fixes flickering.
2019-05-03 03:49:50 -04:00
1f6a27a8d0
Fixed particle error.
2019-05-03 02:49:26 -04:00
85d0d8009b
Fixes
2019-05-03 01:46:02 -04:00
4aa38ed965
Added support for 1.14.
...
Optimized code.
Entities are now loaded.
Added Updater.
2019-05-03 01:44:58 -04:00
5d5851c3a0
faster
2019-03-14 18:53:28 -04:00
39a19ee8d4
Version
2019-02-23 08:18:18 -05:00
1c9b2f7a02
Version
2019-02-19 14:21:49 -05:00
838007eb3e
Fixed particles
2019-02-19 14:19:13 -05:00
d88d5ecde1
Ability to make end portals removed.
2019-02-18 20:00:43 -05:00
4a17e1ec82
Version
2019-02-18 10:06:04 -05:00
d99a16ff2f
fix for epicspawners support
2019-02-18 10:05:23 -05:00
c9c33eaba4
Fix for settings editor.
2019-02-03 19:06:09 -05:00
9af60b1391
Version
2019-02-03 18:55:42 -05:00
129127ea87
Fixed a bug where you could create portals using anchors
2019-02-03 18:51:16 -05:00
a5bae8a204
Cleanup/remove arconix.
2019-02-03 18:51:00 -05:00
4c0f76cead
Fixed hook perms for building.
...
null check.
2018-11-23 10:32:33 -05:00
821831b56b
version
2018-11-09 17:25:00 -05:00
5ac773d492
version
2018-11-09 17:24:14 -05:00
Christian Koop
dependabot[bot]
ceze88
Brianna
Esophose
Niels Vergucht