Minecraft Forums

Oh, good to hear. Which plugin?

What errors do you get? If this is a small server, SQLite is fine, but if you plan on trying to get a decent player base, MySQL would be a much better choice.

It's using SQLite by default. The developer of the plugin likely has documentation on how to change this, and considering you paid for the plugin, you should really be asking the developer about this. If he hasn't added documentation about how to change this, I'm honestly impressed. The page below should answer your question.

https://dev.mysql.com/doc/connector-j/en/connector-j-reference-configuration-properties.html

Quote from LordSkout»

So all the [secured] hosting companies will obviously love this. The rest... not so much. forum should be a lot less utilized though. There won't be any place on MCF to request or offer hosting sponsorships, then? Your suggestion of finding a server that needs room to grow... leaves nowhere for that to actually happen. Not on MCF, anyway.

I'll be sad to see the Hosting Requests section disappear. I've met some interesting people there and learned a lot. It's the only section of MCF outside of the main news page that I read on a regular basis.

The error is self-explanatory. Essentials is not installed (EssentialsProtect can't run on its own) or Essentials failed to load (broken config, mismatched versions, etc.). Ensure you have Protect and the base Essentials plugin on the same version/branch of Essentials and that Essentials itself is able to load.

Delete usercache.json. Should fix it.

Using a system like BanManagement is the only way to do this without making something yourself (BM has a separate web interface, you can customize it to appear to be a part of your main site).

Yes, portfowarding is reasonably safe, especially in this usage scenario. It becomes unsafe when you fail to take security precautions when running large public servers on a dedicated machine or even from home, like using an administrator/root account for running the server, opening wide ranges of ports unnecessarily, etc. Considering this is only for you and a friend, there is basically no risk involved.

Quote from radioshack4500»

I throttle mine to 60. thats all it needs, anything more is just but hurt to my mac specially with a server in the background.

Quote from ItsDaPopo»

A nvidia titan can reach up to 7000 FPS, But i doubt he uses one.

It is easier to do this through Essentials, it's not complicated whatsoever. Your config would look like this, you're just replacing 'Moderator' and 'Admin' with whatever the name of the actual groups are. Of course, you can also add more by simply copying and pasting those lines and changing appropriately.

# This section requires the EssentialsChat.jar to work.

 

chat:



  # If EssentialsChat is installed, this will define how far a player's voice travels, in blocks.  Set to 0 to make all chat global.

  # Note that users with the "essentials.chat.spy" permission will hear everything, regardless of this setting.

  # Users with essentials.chat.shout can override this by prefixing text with an exclamation mark (!)

  # Users with essentials.chat.question can override this by prefixing text with a question mark (?)

  # You can add command costs for shout/question by adding chat-shout and chat-question to the command costs section."

  radius: 0

 

  # Chat formatting can be done in two ways, you can either define a standard format for all chat.

  # Or you can give a group specific chat format, to give some extra variation.

  # For more information of chat formatting, check out the wiki: http://wiki.ess3.net/wiki/Chat_Formatting

 

  format: '<{DISPLAYNAME}> {MESSAGE}'

  #format: '&7[{GROUP}]&r {DISPLAYNAME}&7:&r {MESSAGE}'

 

  group-formats:

  Moderators: '{DISPLAYNAME}&7:&f {MESSAGE}'

  Admins: '{DISPLAYNAME}&7:&f {MESSAGE}'

 

  # If you are using group formats make sure to remove the '#' to allow the setting to be read.

Quote from itsMites»

As far as I am aware, we had logblock and playtime plugins that use MySQL.

And when you said "shouldn't happen even if it fails to write", since the server still crashes could this be a problem on the side of the host or the server?

Also, we've removed some of the plugins (including log block and playtime) and haven't encountered any crashes so far. Will update if something comes up.

Join dates go by the server time, and it's 11/20 where the servers are located. It really shouldn't be this way and is inconsistent, so I'll put in a bug report.

Quote from EldurBlomm»

StealthBravo, thank you. Whilst you are correct that posting about such a thing on a Whitelist thread will derail the topic, that was not what was being posted. We were discussing the server, and the Owner posted frequent updates, regarding things within the server itself, such as an addition to Spawn. Other people (like myself) post about their Builds, and attempt to have discussions related to our server. Is this not okay? Because this is what the Owner was warned for.

Appears I misunderstood that part, whoops.

Rules regarding what can be posted in server threads have been bolstered compared to a couple years ago due to people trying to get around our no bumping rule. In order to get around the no bumping rule, people just redirected members to discuss all server matters in a server thread in order to bump it up constantly. This is no longer allowed, and has been the case for about a year or so. The discussions in there rarely are anything of significance, are there to bump the thread up most of the time, and cloud the thread up with unnecessary posts. Casual conversation should be handled via the server's forum or by other means, but the thread should not be the general discussion place for a server. For updates, you may post them, but they must be more than "added some things to spawn", "squashed a few bugs", etc. When you make an update, it should be cumulative, a collection of updates over a period of time, small or large. It should not be daily, but if it's something urgent, you may make a new update post. Whether your updates are bumping/update spam or not is at the discretion of a staff member, but it is pretty obvious what is bumping and what isn't.

The post in this section was deleted by someone browsing through topics, it was never reported, so it's not like we took down your post via a report and left the other. Again, I don't really see anything wrong with the posts you made, so it's being looked into.

Since the post in question was in my section, I've deleted it and taken appropriate action.

Keep in mind that we can't be everywhere all the time. We all have lives, we may catch some posts in a thread, and others may slip past us. If we miss them, we rely on you to report them to us so that we can take appropriate action. In either case, we have no bias here, and it is as simple as just missing the post in question.

Posts in the report queue can take a few hours to be solved, or a few minutes, it just depends who's here. If it's been days without anything, then yes, you should contact us through other means, but a few hours is not really a very long time, and shouldn't be really alarming.

Regarding the removal of that post, specifically, the one with the chat conversation, if it is a whitelist thread, then yes, that post is in violation of the rules, and you should technically receive an off-topic warning. Discussing post removals and other forum-related things in a server thread (especially when you're bashing the staff team pretty blatantly) is not the right way to address any concerns you have, and just serves to derail the topic. Concerns? Talk to a staff member or submit a ticket.

As for accusing administrators of abusing powers, that is quite a length to go to without even getting proper explanation from anyone. I have no idea why it was deleted, but it will be looked into, and undeleted if found to be in error, but in any case, throwing accusations around isn't the right approach to this situation.

These logs are very inconclusive, but the errors on here appear to show that when a player joins, there is a plugin is trying to write to a flatfile SQL file, and is failing to do so, and in turn, crashing the server (shouldn't happen even if it fails to write). In either case, we'll definitely need more logs than what you currently have. A list of plugins would be useful too.