Discussion in 'Inactive/Unsupported Plugins' started by Tazzernator, Jan 19, 2011.
okay i'll try that and see if it works. i must have accidentally typed it in or something. okay i'll do that my bad.
EDIT: yup that worked thank you very much for your help!
I am having a problem getting the startup part of Timeshift to stick on our server. Running CB1000. The shift part of it works fine and if we change the time of day it will continue to loop until the server is restarted. I have given myself the timshift.startup permission node and the message confirming the setting appears but when the server restarts so does the loop. Do you have any ideas or do you need more information? Or is this because of the version difference?
Sorry about that, it appears that when I started writing 2.0.2 from the latest source on my github I missed a last-second change that made it into 2.0.1. 2.0.3 is now available. This fixes the issues with setting a persistent action.
- Re-Added orphaned code for persistent settings.- Removed conversion from old file format to DB.
can you put the worldsupportsettings in config.yml
i have 2 world
1. freebuild -> i want only Day
2. survival -> normal
with /shift day i all okay, but after every restart i must connect on the server and write the command.
hmm "no weather-Plugin" have a config.yml support, ->
You can see it:
i get this error at load though the plugin still works
2011-08-16 23:21:57 [INFO] DataSourcePool [TimeShift] autoCommit[false] transIsolation[SERIALIZABLE] min max
2011-08-16 23:21:57 [INFO] SubClassFactory parent ClassLoader [org.bukkit.plugin.java.PluginClassLoader]
at first i thought it might have been config file so i deleted it and same error. also im running cb 1000 and latest version of timeshift as of yesterday night. it was working untill i updated like 15 of my plugins (didnt know about craftbukkituptodate) anyway help is appreciated and thanks in advance.
No. You can use /shift startup __ to set a world to automatically loop a specified setting after restarting. You can put the world name(s) on the end if you want to change a world you are not on.
This is not an error. It's debug output that I have no control over.
ok thanks cjc343 so i shouldnt worry bout it? guess no way to get rid of it lol
Nope, no need to worry, and unfortunately, no way to get rid of it. Any plugin which utilizes Bukkit's built-in persistence will cause a similar message.
AMAZING plugin. Only suggestion (if you don't do so already) use world.getName() instead of world.toString() to remove the  from the name. Unless thats intentional
Wheres the download link to 2.0_3?
The messages can be configured via the config.yml. 2.0.3 is linked in the top post. I control the file at the download link, but I can't update the title.
oh, alright. Thanks!
i see u updated the GitHub to 2.0.2 was wondering if you were going to keep updating this page to support the changes or just the dev.bukkit.org.
so i know i wont have to ceck this one every time
The latest release is 2.0.3 and it is available from here or dev.bukkit.org. (Latest Jar link in the first post)
I forgot to upload 2.0.3 to github. The main change is a single line that was lost in 2.0.2 that saves the persistent settings.
I will continue to update people here by posting when there are new releases as long as these forums are around, but I probably won't be bothering Tazzernator about updating the first post. The dev.bukkit.org page will be kept up to date.
thanks for the info
TimeShift is working with the new RB, CB#1185.
Can you update it to support PermissionsBukkit please?
I do plan to support the new permissions system, but have not had the time to finish implementing it yet. I'm in the process of moving back 750 miles north, so it will be a few days before I can put a bit of time into it again.
Tested a little bit on 1185, no technical problems.
I'm looking for a night-only plugin that lets me keep it pitch-dark night-time full-time on one "space" world.
This looks perfect, except it needs to end the night-time about 15 seconds earlier (to avoid all dawn glow), and it needs to start the night-time about about 25 seconds later (to avoid all sunset glow). I want no glow on the horizon.
An update to TimeShift is now available: 2.1 adds native permissions support and switches to the new configuration methods. As always, it can be downloaded via the link at the top of the first post to the "Latest Jar"
I've been considering adjusting these in the future, but in the meantime, could just manually nudge the values and provide you with a specialized build if you're still interested.
TimeShift 2.2 is a maintenance release due to the Events system changes.
Other changes were planned, but I unfortunately don't have the time to complete them right now.
Long time no see Tazzernator. You will notice that this thread has now been placed into the Inactive Plugin subforum.
If you wish to revive this plugin, please ensure that you update and test compatibility with the latest recommended Bukkit build before reporting your original post, asking for it to be moved back to the release forum.
Thanks for your time.
TimeShift is not inactive.
It is both up-to-date and tested with CB 1.2.5-R5, the latest RB.
I have been the primary maintainer of the project for a short while now. As evidence I submit my post history in this thread.
I have already reported the original post, but have seen no action nor heard any reply. I should probably be happy because it will get more attention lingering on the first few pages of Inactive rather than stuck behind pages upon pages of threads in Releases, but I'd prefer that the users who still exist not be mislead as to the current state of the plugin.
TimeShift 3.0 has been released. It is a major rewrite of many parts of TimeShift, including:
- Complete rewrite of command parsing and handling. Allows for a variable set of user defined commands with customizable settings, and simplifies the addition of new command types in the future.
- Convert from Bukkit's Persistence to storing startup config in user-editable (if you really want to...) yml.
- Allow configurable strings to be colorized with &[0-9a-f] when configuration.colorize-strings is enabled in config.yml.
- Rewrite time looping logic to remove static settings.
- Schedule timers more efficiently.
- Added config.yml option to completely disable listening for '/time [x]' commands and cancel active shifts when used.
- Added German translation of old config + new config options courtesy of RasCas (from forums.bukkit.org and dev.bukkit.org).
Separate names with a comma.