Residence 3
Planned feature list of Residence 3:
- Essentially a rewrite - the Bukkit API has changed over time and Residence has been "fixed" as necessary. It's time for a clean-up.
- Vault will be required and direct support of the various permission and economy plugins will be removed.
- Spout support will be stripped away, but if someone wants to make an add-on to provide Spout support, an API will be provided.
- The new code will be modular in design, and the modules will use the API provided to developers, providing a reference example.
- As hinted at, a new API for Residence will be provided though as much backwards compatibility as possible will be provided for the existing developers. It will also include JavaDocs, for an easy breakdown. This will be updated whenever a new jar is made.
- SQL support.
- Better permissions control.
- A full in-game command rewrite, that will overhaul the current configuration process.
Leave a post if you think something should be added. We continue to read these comments, but please try not to repeat posts.
Residence 3 has been scrapped, instead T00thpick1 has spent countless hours cleaning up the 2.x code and adapting a seperate version of Residence that will support mySQL solely, from then on we will continue to update both versions, Although the SQL version will have new features implemented in the future while the flatfile version will merely just be maintained as is.
A cool feature might be when players right click on their rented sign, it renews their time period to maximum. This could replace the autorenew feature and the right click to unrent feature.
ex. My rented plot only has 1 day left, I right click the sign and my plot now has 7 days left.
Is this page being monitored? :-)
This idea came from the residencelimits plugin - Add restrictions for 1 or more residences that can have subzones bought from. (IE You have a large residence set as the main residence and you want to restrict the amount of subzones purchased / owned to a set amount)
Would love to have that in residence.
How long wait Rasidence 3.0?
server is updating aug 17th.... please update! didnt think res would take so long to update to 1.3
@bluehasia
Use the dev build of 2.x series. Its all good and working.
@toothpick ok thanks and are you referring to the old Residence page that supports the current RB release or theres a dev build of res 3 some where?
dev 2.6.5 :(
Would you be able to make a new residence type for shops...this would have its own separate subzone sort of thing but would count differently to residences...e.g.
I can have 7 residences but can only have 2 shops...the shops are a separate setting...kind of like a subzone?
It would be great if there were something like 'moderator' mode, for example you type
/res use SomePlayer
and you have the same and only that player flags,
/res use
you have back your flags, and you don't have access to other player residences
The goal is to be able to have in log what moderators do :) (hmm, now that i write, i think it could be possible to do with mod even now in residence 2)
Ability to run /res commands in console would be awesome!
Maybe some spout addons ?
Any other plugin cant see /res commands. I can't set cost of "/res tp" in essentials and i can't disable it in antipvplogger. So please fix this.
"be or not to be...?"
Google Translate English Hello, I have a question. If I set that is not on a map in the config.cfg can be protectet but I as an admin and in a zone protecte these players may protecten. Does that work? Deutsch Hallo, ich habe eine frage. Wenn ich einstelle, dass auf einer Karte in der config.cfg nicht protectet werden kann aber ich als Admin eine Zone Protecte und in dieser dürfen die Spieler protecten. Geht das ?
@centriux
There is a ResidenceCommandEvent which can be used to tell when commands are issued
@kolorafa
You can currently toggle resadmin mode on or off whenever you want
This plugin could use SQL, but please make a way to convert the current flatfiles. Residence signs is an essential addon, please try and help that stay compatable to
I have a question: How is detecting moving into/out residence? is it comparing players posittion with every residence on the server every time when player move? because it seems so, and it is very bad for performance.
i think, the better way is separatly store areas of residences for every chunk (if res is in more chunks, that mean more areas for one res - areas share flags), and if player moved, check only within the same chunks areas.
sorry for bad english, but i hope you got an idea.
Please, for when will the version with SQL?