The-Kid-1412

Tout marche à merveille maintenant :D Merci madame :)

Si tu change d'offre tu conserve l'intégralité de tes configurations et ta map. La limite sera simplement augmentée. Tu peux changer d'offre sans soucis!

Bonjour. J'ai installé le plugin [bukkit] Elevators sur mon serveur, mais lorsque je fait /elev createcomme sur la vidéo, une phrase en rouge me répond que je n'ai pas accès à cette commande: Alors que je suis "Op" et que dans Permissions, j'ai comme commandes users: _Kid_: group: Admins permissions: - '*' - 'elevators.operator'Voici mon fichier Configuration.txt au cas où: ! ELEVATOR PLUGIN CONFIGURATION * WaitTime = 5 # Time in seconds, how long the elevator stays at a single floor. # Use values like '5' or '3' or '4.5' (without inverted commas) * ButtonPressTime = 900 # Time in milliseconds, how long the plugin waits for pressing a up- or down-button several times. # The counter will restart after every button press. # Use values like 900 or 600 or 1200. * ReachMessage = Elevator reached %F # Message when the elevator reached a floor. # Use %F as floorname variable. * ReachNoNameMessage = Elevator reached new floor. # Message when the elevator reached a floor without a specific name. * ReachWaitMessage = (holding for %T seconds) # Message appended to the ReachMessage, when the elevator waits before moving to the next floor. # Use %T as time variable. Value is in seconds. * DoorBlockedMessage = Something blocks the door! # Message when the glass doors cannot close because an entity is between. * NoHighFloorMessage = There is not such a high floor. # Message when the the elevator is called to a non-existing upper floor. * NoLowFloorMessage = There is not such a low floor. # Message when the the elevator is called to a non-existing lower floor. * ElevatorNotFoundMessage = Can't find the Elevator! Maybe it is destroyed. # Message when the the elevator ground blocks are undetectable. * ElevatorDamagedMessage = The elevator is broken! You have to repair it before usage. # Message when some of the elevator ground blocks were found, but the basic shape is not complete. * StuckAboveMessage = Oh no, the elevator is stuck above! You have to clear the shaft and restart manually. # Message when the elevator got stuck above. * StuckBelowMessage = Oh no, the elevator is stuck below! You have to clear the shaft and restart manually. # Message when the elevator got stuck below. * UserNotAllowedMessage = You are not allowed to use the elevator. Contact %O. # Message when a user tries to use the elevator who is not allowed to do. # Use %O as variable for the name of the elevator's owner. * UserNotAllowedMessageNoOwner = You are not allowed to use the elevator. # Message when a user tries to use the elevator who is not allowed to do and the elevator has no owner. * ElevatorPasswordRequiredMessage = Elevator's password required. Just write the password in the chat. # Message when a password is required to use the elevator. * FloorPasswordRequiredMessage = Password for floor %F required. Just write the password in the chat. # Message when a password is required to get to a floor. # Use %F as floorname variable. * WrongPasswordMessage = Wrong password. Action will be aborted. # Message when an entered password is wrong. * owner-restriction = true # If this option is set to true, only the elevator's owner can modify it. * ignore-passwords = false # If this option is set to true, password protection is disabled. * ignore-users = false # If this option is set to true, user whitelist restriction is disabled. * MaximumGroundBlocks = 25 # Maximum amount of ground blocks an elevator can have. Limits the size. # BE CAREFUL, large values can cause performance problems. * AuthenticationRange = 8 # All players within this range are checked for authentication when requesting a move. # Every player will be asked for password, if required. # If one of the players has an authentication, the elevator will move, undependant from the status of the other players within the range. * Debugging-Log = false # If this option is set to true, elevators debugging messages will be shown in console and saved to file plugins\Elevators\DebuggingLog.log. # Debugging Messages provide information about function steps and storage coordinates.

C'est faux, j'ai quelques plugins et je n'ai aucun lags (merci VeryGames ;D) et rien ne bug...

Les commandes sont disponibles sur le VeryWiki. Pour ajouter une personne depuis le jeu tu dois utiliser cette commande: /group Pseudo GroupePar xemple si je veux ajouter la joueuse "lith" aux modérateurs et que le groupe des modérateurs s’appelle "Modos" je tape: /group lith Modos

Cette commande apparait si tu as fait une erreur dans ton fichier de configuration.

Je crois qu'il peut y avoir une astuce. Hm, sans être sûr de ce que j'avance, étant donné que "//" commente une ligne en Java, place en suffixe aux joueurs par Défaut: prefix: '//'en ayant un /iChat/config.yml ressemblant à ceci: message-format: '+prefix +name &f: +suffix+message'De cette façon le "//" devrait commenter la ligne et ne rien afficher mais ce n'est pas testé et je ne te promet rien. Si ça ne marche pas tu peux essayer de remplace "//" par "#". Mais si ça ça ne marche pas, je ne pourrais plus t'aider :p

Ha, merci de l'info, je pensais que réparer ne faisait que réparer les fichiers corrompus ;)

Réinstalle ton serveur et la version sera mise à jour. Pense à faire une sauvegarde avant quand même ;)

Vers la fin de ton fichier de configuration, j'ai mis: users: _Kid_: group: Admins info: prefix: '' suffix: '' permissions: - '*' TenK_: group: Moderator info: prefix: '' suffix: '' permissions: - '' Lyasonor: group: Moderator info: prefix: '' suffix: '' permissions: - '' Il te suffit de remplacer "_Kid_" par ton pseudo pour avoir toutes les commandes. Ensuite, si tu souhaite que tout le monde puisse construire sans être dans le fichier world.yml, remplace build: falsepar build: truedans le groupe "Default", ce qui donne: # System is no longer used, but may become used in the future # Copies is for multiple-world support # Put the name of the world you wish for it to be a clone of, otherwise leave it empty. # Does not work for the default world. # Example: copies: Derp - This will clone the permissions of the world Derp # # Make sure to rename this file to the name of the world that is in sever.properties under # level-name. So if it is level-name: world then this should be world.yml and in the # plugins/Permissions directory (ie. plugins/Permissions/world.yml) # # NOTE: Do not use tabs while editing this document. Use only spaces. A good way to avoid # doing this is to use Notepad++ and replace the tab with 4 spaces. plugin: permissions: system: default copies: ## # AntiBuild is included with this. To disable a group from being able to build then # set the build: flag to false (build: false). If you want a group to be able to build # then set it to true. ## # Groups can contain inheritance. # To make a group inherit the permissions from another # group simply place the groups name in the "inheritance:" like so: # # Example: # inheritance: # - Default ## # All permissions including the asterisks must be placed in single quotes. # like so: # # - 'general.spawn' # # Otherwise errors will happen! ## # Globalized Permission settings: # # If a permission contains periods (.) you can denote a globalized parameter: # # - 'general.*' # # This will allow you to use all general commands. # ## # Single Asterisk denotes all commands: # # - '*' # If you give a group this permissions, do not have the group inherit any permissions # from other groups. Any users assigned to this group should NOT be given any additional # permissions either. ## # To exempt a node use the - prefix like so: # - '-general.time' ## # prefix: and suffix: do not do anything on their own. You need another outside plugin # such as iChat or HeroChat in order for these to do anything. groups: Default: default: true info: prefix: '' suffix: '' build: true inheritance: permissions: - '' Moderator: default: false info: prefix: '' suffix: '' build: true inheritance: - Default permissions: - '' Admins: default: false info: prefix: '' suffix: '' build: true inheritance: permissions: - '*' ## # Users denote which users are included in which group. # TheNo1Yeti is in the Admin group # Herpina is a member of the Moderator group but also has access # to the herp.derp permissions # Derpina is a member of the admin group but does not have access # to the derp.derp permission node # Users can also have a prefix and suffix as seen with Herpina ## users: _Kid_: group: Admins info: prefix: '' suffix: '' permissions: - '*' TenK_: group: Moderator info: prefix: '' suffix: '' permissions: - '' Lyasonor: group: Moderator info: prefix: '' suffix: '' permissions: - '' Et pour finir, si tu souhaite ajouter certaines commandes à certaines personnes ou à certains groupes, il te suffit de rajouter le nom de la commandes (qui ressemble à "essentials.help" ou d'autres trucs dans le genre) dans la partie "permissions" d"un groupe ou d'une personne. Par exemple si je veut rajouter les commandes de check AFK et d'affichage des règles avec Bukkit à Lyasonor, je remplace: Lyasonor: group: Moderator info: prefix: '' suffix: '' permissions: - '' par Lyasonor: group: Moderator info: prefix: '' suffix: '' permissions: - 'essentials.afk' - 'essentials.rules' En espérant t'avoir aidé ;)

C'est vrai ^^

Mets ton fichier entre les balises code parce que là c'est illisible sans l'indentation...

Il faut que tu edit la white list, en modifiant le fichier white-list.txt et en y inscrivant le pseudo exact des personnes que tu souhaite avoir sur le serveur. Ensuite tu reboot et ça devrai marcher (ça marche chez moi en tout cas). Sinon tu peux, comme l'a dit PetitSnickers, aller dans "Mes Jeux" depuis ton panel VG et cliquer sur le "MAINTENANT" à la droite de "Minecraft CraftBukkit" ;)

Envoie tes fichiers /Permssions/world.yml et /iChat/config.yml

Envoie tes fichiers /Permissions/world.yml et /iChat/config.yml