Bukkit

HUZZAH! I am in fact not dead and still care about Minecraft at least a little bit. As a not-being-dead present, I have released SecureLogin v1.8.5! It doesn't live up to three years of hype, in fact it only took one day to code, but hey it's something.

Happy server owning!

Best,

~ Pooks

The download marker is at 3,999. Post it here if you're the 4,000th downloader!

Edit: Well darn. 4,000 downloads and no comment. Oh well, I'll take this moment to celebrate. *rejoices for SecureLogin receiving its 4,000th download!*

@latestduo

Thanks, man. I actually look up to a plugin like AuthMe, and that you're switching from that to this is a compliment to me. Anyway, even though I've made this plugin with the same general function, I've never actually used AuthMe before; in fact, I originally thought I was only in competition with SafeLogin.

Since I've never used it, I'm not entirely sure how it works. I just downloaded it and started the server to generate the files, but from what I'm seeing, there's the option to use a MySQL database, or use the "auths.db" file as storage. AuthMe was meant for a server with thousands of players, while SecureLogin, using one file, works very well for a large amount of players, but it's not as solid for several thousands if you compare it to using databases.

There's also a "players.yml", though, and I'm not sure what the function of that would be if the plugin can use two other databases. If the players file is used similarly to SecureLogin's player file, I may be able to pull it off with converting the file, so long as: a. you're not using either of the databases, or b. you are using either database and AuthMe has a converter to transfer it from one storage type to the other (in this case, database to .yml file). But if the player file does not have a similar function to SecureLogin, I'd probably have to learn to use databases, and I don't really have much time to do so at the moment (although I've been looking forward to it; a convenient opportunity never arose).

To sum it up, the best and easiest way for everyone (except lazy players) is just for you to set up SecureLogin like any other new user, then have your players re-register their information.

Thanks for your feedback. ;)

@DebenOldert

Thank you for reporting this. This bug occurs if more than one player is in the players.yml file. The reason I didn't find it is because I test my own plugins, and I am the only one who tests them. I only had one player available, so I didn't think to try it with more players in the file.

Although I'll have to recode the entire UUID switch process, it seems straight-forward enough to fix. I'll see if I can't get it done today.

Again, thank you for bringing this to my attention.

Edit: This bug only affects servers that already had previous SecureLogin version 1.8.3. If you delete all traces of SecureLogin on your server, then install the new version, it should work just fine. If you don't mind having all of your players re-register, you can go ahead and do that. Otherwise, if you want to wait for the new file - which may not come till next week - then I'll be here, working on it.

@raton023

I did think about learning MySQL for it, but I didn't feel that it was necessary. I don't believe hugely popular servers would use SecureLogin, as they would have their own plugin for it. And unless your server is very popular - like, at least three hundred players online at once - the players.yml file is all you should need. In Version 1.8.3 I added the /get<password, sq, sa> commands for this very reason: so that you can view players' passwords without having to put much effort into searching.

So unless you can provide a reason for using MySQL, such as your server being amazingly populated, there's no real need for it.

@Winterfellhard

Fortunately, yes there is! :) If you just toy around with permissions, you can set it up for certain groups and worlds. I do believe that if you give players "securelogin.nofreeze", it will allow them not to have to register their passwords and SQ/A's.

Thanks a lot for the feedback.

Edit: Hah, I just realized I know your name from the Forums.

@ThisUsernameIsMine

Yeah, good point. Wasn't until later after that post that I read a post that BukkitDev would still be online but wouldn't be as thorough with the files. In fact, v1.8.3 was available the instant I uploaded it, so I'm guessing that they've put it up on an automatic system now.

Fixed. The file is currently awaiting approval. I hope there's at least someone left in BukkitDev to approve it.

Update: Yay, BukkitDev had a very quick response with it. Thanks, guys.

@Blocksolot

TL;DR: I'll get to it when I get the chance. :)

Well to start with, I had no idea Bukkit plugins were compatible with Tekkit in the first place. Also, I'm not entirely sure that a future-version plugin would work with a past-version server. I know it works the other way around, but it's possible that the codestuffs and such get changed throughout the versions in such a way that mismatching versions only work if the plugins are what's outdated.

Anyway, I may or may not look into this... Believe me, I would really like to. However, I just don't have the time and energy to devote as much time as I used to for plugins and Java in general - not with school started and having a busy schedule with sports and homework and that stuff.

So yeah, I will take a look at this if I can, however it's a little unlikely that I will be able to. Thanks for the feedback.

Also a side note: As in my current signature, and of course the many Bukkit blog posts, Bukkit has pretty much died, along with the future of all Bukkit plugins and most Minecraft servers, maybe even Minecraft itself. I prefer not to invest so much time into something that has no chance of future survival, but rest assured that in this case, SecureLogin is not included in one of those dying things - every time I look at this page, I am very happy and thankful to see that the downloads number never stops increasing, slowly but surely.

(Edit) An additional side note: Hahah, yeah, um... I think I deserve to feel a little guilty that I never actually tested the teleport-back feature. The code seemed simple enough, so I decided not to run it through experimentation. The Security Questions/Answers really chewed me up and spat me out - MAN those were a pain to debug. When I finished them, I was so excited to have the hard part out of the way and as far as I know, all other features work perfectly, and I got pretty excited that I was finally able to release the SL 1.8.0, which I had promised to release but then abandoned for so long. So, my bad for leaving that untested. Sorry about that. ;)

Hey guys, feel free to give your feedback on the plugin! It doesn't matter if it's positive or negative; positive feedback tells me that the plugin's working fine, negative feedback gives me something to improve upon.

Reply to this comment or send me a private message to give your opinion on SecureLogin. Thanks! :)

@SniperBoss17

Oh! I know exactly what's wrong, and my mistake! I forgot to input /createSA in the default "allowedCommands" config setting! To fix this, go to your SecureLogin config file, and find the allowedCommands section, then add ",/createsecurityanswer,/createsa,/changesecurityanswer,/changesa" to the existing list.

So sorry, I'll upload a fixed config immediately!

Edit: A couple days after this post, a new file was uploaded with a fixed config.

Lol, forget the "not soon" part of the previous post. SecureLogin v1.8.0 is here! All changes will be made official when the new file gets approved.

Thanks for your patience everyone.