Fragen über Chat (Nickname und "!")

[BlueCrafter]

Hallo,

ich habe ein paar fragen über den Chat...

1. Irgendwie werden die Nicknames nicht angezeigt; ich erstelle zum beispiel einen für mich auf meinem Nittrado Server und da steht auch das das mein Nickname ist, aber wenn ich jetzt was in den Chat schreibe wird der net angezeigt sondern nur mein Minecraft-Name, wie kann ich das ändern?

2. Irgendwie bekommt nicht jeder auf meinem Server die Nachrichten aus dem chat,, daswegen wurde ich heute drauf hingewiesen, dass ich ein "!" vor meinem Satz machen muss, aber ich will nicht immer ein ! davor machen, wie ändere ich das?

danke im vorraus MinecraftChar

 

[BlueCrafter]

Wie gesagt, ich mach ja auch meinen Nickname, der wird auch bestätigt, aber im Chat is er net zu sehn

 

[BlueCrafter]

AntiCreeper
ChatManager
ChestShop
Essentials
EssentialsGrupBridge
EssentialsSpawn
iConomy
Jobs
LogBlock
LogBlockQuestioner
LWC
Modifyworld
NochatPlus
Permission***
ShowCaseStandalone
Spectate
Vault
WorldEdit
WorldGuard
ZavautiMessager

Das sind die

 

[BlueCrafter]

Kann mir niemand helfen? Sry, das ich das Frage, aber ich komme garnicht mehr weiter mit meinem Server -.-

 

[Kaldori]

Gibt es irgendeine Fehlermeldung in der Konsole?

 

[BlueCrafter]

Das hier, aber damit konnt ich nix anfangen...

Fehlermeldungen im server.logEs wurden verschiedene Fehler im “server.log” gefunden. In der folgende Liste werden die Fehler angezeigt. Bekannte Fehlermeldungen werden genauer beschrieben und so weit möglich mit einem Lösungshinweis versehen. Falls diese Erklärung nicht weiter hilft, besteht die Möglichkeit einen Thread im Support-Forum zu erstellen, oder den Nitrado-Support per Ticket oder Telefon zu kontaktieren.
Zeile 1361: 2012-07-10 14:17:41 [SEVERE] [Jobs] Job None has an invalid Player Kill type property. Skipping!
Zeile 1360: 2012-07-10 14:17:41 [SEVERE] [Jobs] Job Fisherman has an invalid Player Kill type property. Skipping!
Zeile 1359: 2012-07-10 14:17:41 [SEVERE] [Jobs] Job Hunter has an invalid Player Kill type property. Skipping!
Zeile 1358: 2012-07-10 14:17:41 [SEVERE] [Jobs] Job Farmer has an invalid Player Kill type property. Skipping!
Zeile 1357: 2012-07-10 14:17:41 [SEVERE] [Jobs] Job Digger has an invalid Player Kill type property. Skipping!
Zeile 1356: 2012-07-10 14:17:41 [SEVERE] [Jobs] Job Builder has an invalid Player Kill type property. Skipping!
Zeile 1355: 2012-07-10 14:17:41 [SEVERE] [Jobs] Job Miner has an invalid Player Kill type property. Skipping!
Zeile 1354: 2012-07-10 14:17:41 [SEVERE] [Jobs] Job Woodcutter has an invalid Player Kill type property. Skipping!
Zeile 1223: 2012-07-10 14:179 [SEVERE] Nag author: '' of 'WorldGuard' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1222: 2012-07-10 14:179 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1221: 2012-07-10 14:179 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1220: 2012-07-10 14:179 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1219: 2012-07-10 14:179 [SEVERE] Nag author: '' of 'WorldGuard' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1218: 2012-07-10 14:179 [SEVERE] Nag author: '' of 'WorldGuard' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1217: 2012-07-10 14:179 [SEVERE] Nag author: '' of 'WorldGuard' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1216: 2012-07-10 14:179 [SEVERE] Nag author: '' of 'WorldGuard' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1215: 2012-07-10 14:179 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1214: 2012-07-10 14:179 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1213: 2012-07-10 14:179 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1212: 2012-07-10 14:179 [SEVERE] Nag author: 'DiddiZ' of 'LogBlock' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1211: 2012-07-10 14:179 [SEVERE] Nag author: '' of 'WorldGuard' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded. This may cause conflicts with the newly loaded version of the plugin
Zeile 1017: 2012-07-10 04:00:53 [SEVERE] [Jobs] Job None has an invalid Player Kill type property. Skipping!
Zeile 1016: 2012-07-10 04:00:53 [SEVERE] [Jobs] Job Fisherman has an invalid Player Kill type property. Skipping!
Zeile 1015: 2012-07-10 04:00:53 [SEVERE] [Jobs] Job Hunter has an invalid Player Kill type property. Skipping!
Zeile 1014: 2012-07-10 04:00:53 [SEVERE] [Jobs] Job Farmer has an invalid Player Kill type property. Skipping!
Zeile 1013: 2012-07-10 04:00:53 [SEVERE] [Jobs] Job Digger has an invalid Player Kill type property. Skipping!
Zeile 1012: 2012-07-10 04:00:53 [SEVERE] [Jobs] Job Builder has an invalid Player Kill type property. Skipping!
Zeile 1011: 2012-07-10 04:00:53 [SEVERE] [Jobs] Job Miner has an invalid Player Kill type property. Skipping!
Zeile 1010: 2012-07-10 04:00:53 [SEVERE] [Jobs] Job Woodcutter has an invalid Player Kill type property. Skipping!

Zu folgenden Fehlern konnt keine Aussage getätigt werden. Es besteht die Möglichkeit einen Thread im Support-Forum zu erstellen, oder den Nitrado-Support per Ticket oder Telefon zu kontaktieren.



Zeile 1256: 2012-07-10 14:179 [SEVERE] it is highly suggested to use SQL with iCo6 or to use an alternative economy plugin!
Zeile 1255: 2012-07-10 14:179 [SEVERE] if you're using Votifier, or any other plugin which handles economy data in a threaded manner your server is at risk!
Zeile 1254: 2012-07-10 14:179 [SEVERE] iConomy6 - If you are using Flatfile storage be aware that iCo6 has a CRITICAL bug which can wipe ALL iconomy data.
Zeile 909: 2012-07-10 04:00:45 [SEVERE] it is highly suggested to use SQL with iCo6 or to use an alternative economy plugin!
Zeile 908: 2012-07-10 04:00:45 [SEVERE] if you're using Votifier, or any other plugin which handles economy data in a threaded manner your server is at risk!
Zeile 907: 2012-07-10 04:00:45 [SEVERE] iConomy6 - If you are using Flatfile storage be aware that iCo6 has a CRITICAL bug which can wipe ALL iconomy data.

Mit der derzeitig verwendeten iConomy Version gibt es einen Fehler. Der Fehler kann zur Löschung der Daten von iConomy (InGame-Konten, etc.) führen, wenn das Plugin "Votifier" oder ein ähnliches Plugin verwendet wird.

Lösungsvorschlag:
Der Umstieg von iConomy-Flat auf iConomy-MySQL oder die Verwendung einer anderen Version von iConomy.



Zeile 1124: 2012-07-10 11:55:41 [INFO] Read timed out

Die Meldung "Read timed out" bedeutet, dass der Server nicht mehr reagiert. Dies kann durch ein fehlerhaftes Plugin, oder durch eine Überlastung hervorgerufen werden. Eine Überprüfung der server.log ist nötig, um so den Fehler zu finden. Folgender Nitradopedia-Artikel (Wiki) kann zur Hilfe verwendet werden: Fehlersuche bei Minecraft Gameserver.

 

[BlueCrafter]

Kann damit jemand was anfangen, bin am verzweifeln