Inactive [ADMN/DEV] PermissionsEx (PEX) v1.19.5 - Tomorrow is Today! [1.4.6-R0.1]

Discussion in 'Inactive/Unsupported Plugins' started by t3hk0d3, May 21, 2011.

  1. Offline

    t3hk0d3

    [​IMG]
    Version: 1.19.5

    PLEASE USE BUKKIT-DEV FORUM FOR DISCUSSION/HELP
    http://dev.bukkit.org/server-mods/permissionsex/
    THANKS IN ADVANCE.

    PermissionsEx (PEX) is a new permissions plugin, based on Permissions ideas and supports all of its features. But PEX is more! It offers different backends, powerful ingame management, fine grained restrictions for world modification.

    [​IMG]

    Current features
    1. Bukkit Permissions (SuperPerms) compatible.
    2. Several backend support. Currently bundled backends is File (YAML) and SQL (MySQL, SQLite). Also it's possible to add your own.
    3. YAML backend, with new, fully rethinked, config schema. Now all user, groups and their permissions are stored in one file - permission.yml. BTW file name is adjustable too.
    4. SQL backend, most delicious. Currently MySQL and SQLite supported, but other DB (like Postgre) are possible too. PEX deploys the DB scheme (tables and initial data) automatically. This means, that you only need to provide data on how to connect to the db, everything else PEX will handle by itself.
    5. Flexible architecture and API - you can change a lot programmatically.
    6. Compatibility layer with TheYeti's Permissions (2.7.4) (as a separate part of the plugin). In most cases plugins, which use Permissions, will alsowork with PEX also.
    7. Rich chat/console command interface. You can do almost everything ingame. Command list below.
    8. Modifyworld - Embedded restrictions mechanism (we call it "modifyworld"), which provides the possibility to control players abilities, such as destroying/placing blocks, riding carts/boats or even getting spotted by mobs and much more. Disabled by default.
    9. Multigroup inheritance. User, as well as Group, can be member of several groups. And inherit their permissions, options and prefix/suffix.
    10. Permissions based upon Regular Expressions. This mean you can use regular expressions. Example: modifyworld.blocks.(destroy|place).(3|12) - this permission allow place or destroy only sand (12) or dirt (3) blocks. There is still limitation on dot usage in your regexps - dots are escaped by default.
    11. Multiworld permissions. Just don't specify world and permission would work in any world.
    12. Multiworld inheritance. You can inherit different groups in different worlds.
    13. Easy migration from Permissions 2.x. Converter for both YAML and SQL are embedded into PermissionsCompat. Just use simple instruction.
    14. Perfomance friendly. Low-level caching helps alot when you have 100+ online users :)
    15. Promotional/Demotional system. You can assign ranks to groups and promote/demote users to higher/lower ranked group.
    16. World-inheritance - permissions/option of one world can be inherited by another world.
    17. Timed Permissions - you can give user permission only for some amount of time.
    18. Chat Manager - small chat plugin, bundled with PEX. With prefixes/suffiex and colors. Check wiki for more details.


    Documentation
    Wiki

    Basic setup tutorial (Thanks to lycano)

    Nice tutorial made by Bennetman


    Download
    Stable version

    Development version (mostly stable) - always lastest dev build.

    Sources
    https://github.com/PEXPlugins

    Builds
    http://webbukkit.org:8080/

    Maven Repository
    http://repo.tehkode.ru/browse/ru.tehkode

    IRC
    Join us on #permissionsex, irc.esper.net. Feel free to ask any related questions.

    Tools !NEW!
    Pex Auto-Setup Tool - MySQL and FlatFile !


    Changelog
    Show Changelog (open)
    v1.19.5
    Proper intervals for timed commands (both group/permissions management), without pesky seconds calculations (like /pex user t3hk0d3 timed add cool.permission 10days)
    Bugfixes.
    1.4.6 compatibility.


    v1.19.4
    Built for Bukkit 1.4.2-R0.1
    Added inventory permissions (modifyworld.items.put/take.<item>.of.<chest>)
    Added item hold permission (modifyworld.items.hold.<item>)
    Sdded monster egg spawn permission (modifyworld.spawn.<creature>)
    Few other minor fixes
    v.1.19.3
    Modifyworld improvements (configurable messages, now independent from PEX)
    /pex help command
    Minor improvements and bugfixes
    v.1.19.2
    New modifyworld permissions
    Some bugfixes
    v.1.19.1
    Bugfix release
    v1.19
    Bukkit R6 compatible.
    Several bugfixes!
    Permissions now case-insensetive.
    v1.18
    Users logging and cleanup feature.
    Non-inheriting nodes feature.
    Several Bugfixes.
    PermissionsCompat is finally remove from default bundle.
    v1.17
    User/group specific management permissions (permissions.manage.group.Admin)
    Fixed some superperms compatibility issues
    Fixed several bugs
    v1.16
    SuperPerms compatbility bridge were rewritten - no lags anymore and now with debug output (now you can view superperms checks).
    Numerous of bugs were fixed (Thanks you guys for reporting them)
    Modifyworld were improved (modifyworld.item.use)
    v1.15
    Compatiblity for 1317+
    Fixed perfomance issues with SuperPerms (if you still experience they try to disable "raw-permissions" in config.yml)
    Fixed issue with prefix inheritance
    v1.14
    Improved Options mechanism.
    Auto saving new users feature, disabled by default.
    SuperPerms bridge improved - more permissions supported by wildcards.
    File backend dumping now fully functional. SQL dumping is still bogus (do not dump world-specific inheritance and prefixes), will be fixed soon.
    Many bugfixes and minor improvements.
    v1.13
    Superperms (BukkitPerms) support
    Multiworld inheritance and prefixes/suffixes
    Groups weighting
    ChatManager, chat plugin which bundled with PEX.
    Modifyworld now separate plugin, but still bundled with PEX.
    API changed slightly, CustomEvents (PermissionsEntityEvent, PermissionsSystemEvent) introduced.
    Many lesser improvements and tons of bugfixes.
    v1.12
    API get slightly improved
    Ranking ladders.
    User/group name case-insensetivity.
    World-inheritance.
    Timed permissions.
    Modifyworld rules are get improved.
    Tons of minor improvements and bugfixes.
    v1.11
    Many bugfixes and improvements.
    MySQL connection stability improved - reconnection mechanism.
    v1.10
    Promotional/Demotional system.
    Perfomance improvement, with new low-level caching system (thx Joy)
    Modifyworld improved.
    Many lesser improvements and bugfixes.
    v1.06
    New p2compat backend, for easy migration from Permissions 2.x to PEX.
    v1.05
    Users/Groups dumping (pex dump <backend> <file>).
    New commands pex promote/demote. Actually this is just aliases for "pex user group set/remove"
    Few bugfixes.
    v1.04
    Players now can be informed about changes (has been added to group, changed permission/option). Disabled by default - set "permissions.informplayers.changes" to "true"
    Config node "permissions.verbose", which responsible for player informing about modifyworld restrictions has been renamed to "permissions.infromplayers.modifyworld".
    Autocomplete has been improved.
    New command "pex config <node> [value]". This command help to manipulate configuration file (config.yml) from console/chat interface.
    Many bugfixes.
    v1.03
    Autocomplete for users (taken from registred users and online users) and groups names.
    New command for user removing (pex user <user> delete)
    Fixed several nasty bugs. Thanks for bugreports!
    v1.02
    Compatibility layer loading order issue fixed. Now most of plugins should work.
    Tested with new CB 803 build.
    v1.01
    Regular expression permissions support.
    Newer permissions now added above (bugfix).
    Several bugfixes.
    v1.00
    Initial public release.
     
    BRampersad, grid21, MrRazull and 71 others like this.
  2. Offline

    DrDewman

    Hey there Randomfish!

    I borrowed your PEX format here and edited it so that the titles are showing nicely. Here's the permissions.yml:
    Code:
    groups:
        Default:
            default: true
            permissions:
            - modifyworld.*
            options:
                rank: '1000'
        Admin:
            permissions:
            - '*'
            options:
                rank: '10'
            prefix: '&5Admin &f'
        Member:
            options:
                rank: '900'
        VIP:
            inheritance:
            - member
            options:
                rank: '800'
            prefix: '&6VIP &f'
        Moderator:
            options:
                rank: '100'
            prefix: '&4Mod &f'
    users:
        Randomfish132:
            group:
            - Member
        superseth45:
            group:
            - Moderator
    
    A picture of it is also attached. Enjoy :D

    PermissionsEx.png
     
  3. Right, the 4 in that line is the damage value.

    I believe that currently it's based on which group is checked first (location). I did see something about a weight entry when looking at the tickets on github, but there isn't any documentation on it (yet), and I have not had time to go experimenting with it.

    I'm sorry, but I don't understand the question. What are you trying to do exactly?

    Take away their access to the gamemode command. I don't recall the node, but if you search using google, yahoo, or just about any search engine for bukkit default commands, usually the first hit has the node listings.

    If you are taking about permissions for a specific user that is different from the group they are a member of, they are part of the entry for that user under the users: section.

    Quickest way to see it:
    1. Look at your current permissions file
    2. Add a bogus permission to one user
    3. Look at the file again
    Simple. :)

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Sep 9, 2018
  4. Offline

    Jäsef

    *facepalm* it makes the name(minecraft username that comes after the prefix) red. and if he's using chatmanager it should automatically go back to white(&f) because chatmanager has a &f in the config after "name"

    yes

    yes, for tools. but for wool and other blocks that have different textures but still has the same value, the seperation is applied: 1:3, would be stone and then a coulor, or a specific stone block(if there were others than the normal stone block)
    this may sound confusing, im rambling, sorry :)

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Sep 9, 2018
  5. No, I understand what you are saying, but you are apparently misunderstanding me.:) That secondary number for items is also referred to as the damage value.

    http://www.minecraftwiki.net/wiki/Wool_Dyes#Data_Values
     
  6. Offline

    Jäsef

    hmm i didn't know that, interesting. well, for potions this would still work, right? You were just pointing out that :4 applies for tools as well, weren't you? :D

    hmm, interesting, i didn't know that :) But the :4 etc would work for wool and other blocks, not just tools. you were just pointing that out, weren't you? :D

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Oct 10, 2018
  7. Offline

    Obliviator

    Does any plugin with nicknames support PEX? - Chatmanager
     
  8. Offline

    AlphaTech1

    Do i have to add ranks?
    Btw heres my permissions-
    users:
    xdawhite_chapelx:
    group:
    - Owner

    coconutz69:
    group:
    - Co-Owner

    55NavyBadboy:
    group:
    - HeadAdmin

    milo1027:
    group:
    - Admin

    legolego61:
    group:
    - Admin

    pokeash654:
    group:
    - HeadModerator

    rrrrrrrr133:
    group:
    - Moderator

    groups:
    Member:
    default: true
    permissions:
    - modifyworld.*
    - factions.kit.halfplayer
    - factions.create
    - HomeX.*
    - iConomy.user
    - permissions.build
    - multiverse.core.tp.self
    - multiverse.access.WORLDNAME
    - warpy.list
    - warpy.warp
    - modifyworld.*
    prefix: '[Member]'
    suffix: ''

    Builder:
    inheritance:
    - Default
    default: false
    permissions:
    - warpplugin.warp
    - econplugin.basic.*
    prefix: '&0[&1Builder&1]&0'
    suffix: '&f'
    Moderator:
    inheritance:
    - Builder
    default: false
    permissions:
    - enable.permissions
    - modplugin.ban
    - modplugin.kick
    - modplugin.unban
    - bColoredChat.chatColor
    - bColoredChat.signColor
    - bColoredChat.useColor
    - bColoredChat.setColor
    - bColoredChat.randomColor
    - bColoredChat.rainbowColor
    - creaturespawn.spawnmob
    - creaturespawn.moblist
    - creaturespawn.butcher
    - creaturespawn.commandlist
    - demigods.admin
    - god.all
    - factions.*
    - factions.money.kit.standard
    - HomeX.*
    - iConomy.user
    - iConomy.plus
    - enable.messages.*
    - broadcast.*.target
    - explosion.protection.all
    - allow.admin.bypass
    - allow.admin.snoop
    - enable.protection.doors
    - default.door.timer
    - multiverse.core.list
    - permissions.*
    - multiverse.portal.access.*
    - multiverse.access.world
    - multiverse.portal.access.PORTALNAME
    - multiverse.access.WORLDNAME
    - multiverse.portal.access.*
    - shop.create.player
    - shop.create.server
    - simplechestlock.*
    - simplechestlock.command.*
    - superlog.config
    - superlog.superwand
    - superlog.notify.flintandsteel
    - superlog.notify.tnt.ignition
    - superlog.notify.tnt.placement
    - warpy.warp
    - warpy.add
    - warpy.remove
    - warpy.list

    prefix: '&1[&0Mod&0]&1'
    suffix: '&f'
    HeadModerator:
    inheritance:
    - Moderator
    default: false
    permissions:
    - warpy.*
    prefix: '&f[&dHeadMod&d]&f'
    suffix: '&f'
    Admin:
    inheritance:
    - HeadModerator
    default: false
    permissions:
    - antixray.axr.on
    - antixray.axr.off
    - antixray.axr.worlds
    - antixray.axr.chunk
    - antixray.axr.chunk.regen
    - antixray.axr.chunk.regen.ore
    - antixray.axr.map
    - antixray.axr.show
    - antixray.axr.hide
    - antixray.axr.dump
    - antixray.axr.diff
    - antixray.axr.gen
    - antixray.axr.gen.copy
    - antixray.axr.test
    - antixray.axr.pack
    - antixray.axr.backup
    - antixray.axr.mirrorworld
    - banhammer.pardon
    - banhammer.ban
    - banhammer.check
    - banhammer.history
    - banhammer.kick
    - banhammer.recent
    - banhammer.weight.heavy
    - godPowers.godmode
    - godPowers.godmodeOnLogin
    - godPowers.die
    - godPowers.slay
    - godPowers.jesus
    - godPowers.heal
    - godPowers.maim
    - godPowers.inferno
    - godPowers.superjump
    - godPowers.zeus
    - godPowers.gaia
    - godPowers.vulcan
    - godPowers.demigod
    - godPowers.commands
    - godPowers.godtools
    - godPowers.hades
    - HomeX.*
    - iConomy.*
    - multiverse.world.create
    prefix: '&f[&4Admin&4]&f'
    suffix: '&f'
    HeadAdmin:
    inheritance:
    - Admin
    default: false
    permissions:
    prefix: '&0[&4HeadAdmin&4]&0'
    suffix: '&f'

    Co-Owner:
    inheritance:
    default: false
    permissions:
    - '*'
    prefix: '&0[&bCo-Owner&b]&0'
    suffix: '&f'

    Owner:
    inheritance:
    default: false
    permissions:
    - '*'
    prefix: '&0[&5Owner&5]&0'
    suffix: '&f'
     
  9. Offline

    Jäsef

    CommandBin

    https://github.com/t3hk0d3/PermissionsEx/wiki/Basic-Permissions-Setup
    scroll down to Set rankorder

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Oct 10, 2018
  10. Offline

    Leenert

    I've a problem....i want to disallow some commands, so i did it like this:
    HTML:
            - modifyworld.chat.*
            - modifyworld.*
            - modifyworld.blocks.destroy.*
            - modifyworld.blocks.place.*
            - modifyworld.blocks.interact.*
            - -modifyworld.vehicle.collide
            - -modifyworld.vehicle.destroy
    But the user is able to use the command....how can i do this?
     
  11. Offline

    petko

    We try to add premissions and create grups via database but the premission does not work when i added from database.
     
  12. Offline

    nicolaasge

    I always vas plugin worked but now when something transcript so it stops working
    2011-12-09 20:47:26 [SEVERE] Error occurred while disabling PermissionsEx v1.16 (Is it up to date?): while parsing a block mapping; expected <block end>, but found BlockMappingStart
    while parsing a block mapping
    in "<reader>", line 2, column 5:
    hrac:
    ^
    expected <block end>, but found BlockMappingStart
    in "<reader>", line 50, column 7:
    VIP:
    ^


    .
    2011-12-09 20:47:28 [INFO] [PermissionsEx] sql backend registered!
    2011-12-09 20:47:28 [INFO] [PermissionsEx] file backend registered!
    2011-12-09 20:47:28 [INFO] [PermissionsEx] PermissionEx plugin initialized.
    2011-12-09 20:47:28 [INFO] Starting FakaHedaMinequery server on 93.91.240.158:28228
    2011-12-09 20:47:28 [INFO] [PermissionsEx] p2compat backend registered!
    2011-12-09 20:47:28 [INFO] [PermissionsCompat] Compatibility Layer Initalized!

    2011-12-09 20:47:28 [INFO] [PermissionsEx] Initializing file backend
    2011-12-09 20:47:29 [SEVERE] while parsing a block mapping; expected <block end>, but found BlockMappingStart initializing PermissionsEx v1.16 (Is it up to date?)
    while parsing a block mapping
    in "<reader>", line 2, column 5:
    hrac:
    ^
    expected <block end>, but found BlockMappingStart
    in "<reader>", line 50, column 7:
    VIP:
    ^

    2011-12-09 20:47:29 [WARNING] [PermissionsCompat] PermissionsEx plugin not found. Some plugins may not work.
     
  13. Offline

    Newah

    Thank you so much for making this amazing permissions system. It will always and ever be my one and only favorite permissions plugin. :D
     
  14. Thank you for including your permissions file, but next time, please put your permissions into patebin and link here or use the code tags. YAML is sensitive to the spacing in a file, and not doing either of the things I listed removes all the spaces, making a post with a permissions file useless for troubleshooting.:)

    As for the question, you don't have to add ranks if you are not going to be using the promote/demote feature in PEX, otherwise what Jäsef posted applies.

    https://github.com/t3hk0d3/PermissionsEx/wiki/Plugin-Configuration

    Per the File backend configuration section:


    Thank you for posting the error (and only the relevant portions of the error:)). Next time, can you please use code tags? It makes it easier to read.

    As for the problem, you have a typo in your permissions file. There is a YAML parser linked in the first post that may help figuring out your spacing problem.

    OK, I will assume that PEX is able to successfully connect to the database, but you need to post the exact command you are running and the exact error you get in response.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Sep 9, 2018
  15. Offline

    Valiant

    for whatever reason, modify world is not letting me do what I want to do. Period. Basically my users can either A: Not destroy anything or B: destroy everything
    Here are my config files.

    PexConfig

    Code:
    permissions:
        backends:
            file:
                file: permissions.yml
        modifyworld:
            enable: true
            itemRestrictions: false
        informplayers:
            modifyworld: true
            changes: true
        backend: file
        superperms:
            parent-nodes: true
            enable: true
            strict-mode: false
        createUserRecords: false
        allowOps: true
        debug: false
        basedir: plugins\PermissionsEx
    ModifyWorld Config
    Code:
    informPlayers: true
    enable: true
    itemRestrictions: true
    messages:
        prohibitedItem: You have prohibited item "%s".
        whitelistMessage: You are not allowed to join this server. Goodbye!
        permissionDenied: Sorry, you must register to do that!
        whitelist: You are not allowed to join this server. Goodbye!
    whitelist: false
    use-material-names: true
    check-metadata: true
    item-use-check: false
    drop-restricted-item: false
    
    Permissions File
    Code:
    users:
        Valiantiam:
            group:
            - admins
            permissions:
        A1Steaksauce:
            group:
            - mods
            permissions:
        Terra187:
            group:
            - mods
            permissions:
        Maha5643:
            group:
            - mods
            permissions:
    groups:
        admins:
            inheritance:
            permissions:
            - '*'
            options:
        mods:
            inheritance:
            permissions:
            - bukkit.command.gamemode
            options:
        pioneers:
            inheritance:
            permissions:
            options:
        default:
            default: true
            permissions:
            - modifyworld.blocks.interact.20
            - modifyworld.blocks.destroy.20
            options:
    

    Ignore the fact that I have users entered. I simply want to set up the config for default users. Glass is simply an example piece I am using to solve it on my own. Now I am here.
     
  16. Perfect, thank you for using the code tags for everything. Things would be easier of everyone did this.:)

    Now, your question:
    Code:
        default:
            default: true
            permissions:
            - modifyworld.blocks.interact.20
            - modifyworld.blocks.destroy.20
            options:
    
    This would allow users to 'use' (as in, place a block on) and destroy item 20 (glass blocks). If you are wanting to allow the default group to place only certain blocks, you want to look at the modify.world.place node. Interact is used for opening doors, using switches, and so on.

    This is a portion of the server log with the PEX debug turned on.

    Modifyworld had item restriction turned on, had dirt blocks and was placing them on grass blocks:
    Code:
    20:53:05 [INFO] User $USER checked for "modifyworld.items.have.dirt", "*" found
    20:53:05 [INFO] User $USER checked for "modifyworld.blocks.interact.grass", "*" found
    20:53:05 [INFO] User $USER checked for "modifyworld.blocks.place.dirt","*" found
    Notice the three checks made:
    1. Can the user have dirt? ("modifyworld.items.have.dirt")
    2. Can the user interact (place a block) on the block they are 'aiming at'? ("modifyworld.blocks.interact.grass")
    3. Can the user place the block they are holding? ("modifyworld.blocks.place.dirt")
     
  17. Offline

    Valiant

    I'm guessing the with "modify.world.place node" you meant "modifyworld.place node"

    Also, yes thank you for explaining the debugging steps, and how it check for the permissions. That is extremely useful.

    I'm going to try to adjust how I have everything set up a little, and see if I can get it to work. I most likely will have more questions to this incredibly amazingly complex tool.
     
  18. Oops, yes, that is what I meant.:)

    It's complex, yes, but it's also incredibly amazingly flexible and powerful.

    I have a guest group that is unable to hold or place blocks and unable to open chests or furnaces (lit or unlit since they are considered two different items by minecraft), but can use/open doors and switches. They also do not get hungry.

    This is possible due to modifyworld. When I was looking at other permission managers for replacement of the old permissions 2/3 series, nothing else offered this level of control or customization (they were either all or nothing affairs).
     
  19. Offline

    Valiant

    I am running in debug myself now, and this is what Im dealing with.

    I have this
    Code:
    permissions:
    - modifyworld.blocks.destroy.glass
    - modifyworld.blocks.interact.*
    but upon the user trying to delete the block, it is telling me it can find that it can has permissions to use the glass (interact with it)
    but then it can't find the permission for destroying it....?

    *EDIT*
    had to put the permission as
    - modifyworld.blocks.destroy.glass.0
    SECOND eDIT
    thats weird. its making me do that for everything...
     
  20. Define everything.:)

    If you have a smallish number of things that you want users to be able to place, you can specify them on a single line per point # 10 in the first post:
    Can you list exactly what you want the users to be able to do (or not do)?

    EDIT: I say smallish not because of any limitation of PEX, but because if it's a large number of items, it might be easier to change the process from a allow->deny to a deny->allow point of view.
     
  21. Offline

    Valiant

    Alright leme set the stage ;)

    I want to create a place where new users can log into the server, and have instant build rights. BUT only be able to use wooden tools and their hand to collect items until they register. (I have ways to prevent them from greifing using protected zones, walkable areas and other things so don't worry there)

    Users should be able to collect everything in the world but not be able to use anything above wooden tools, leather armor, and not be able to collect iron(or above) and not be able to use buckets and that usual protection setup.
     
  22. Hmm... This one isn't the easiest due to the sheer number of items (and the fact that minecraft doesn't seem to have any specific number scheme)...

    What I would do is something like this. I've not tested it myself, but I'm pretty sure this will, at the very least, get you going in the right direction:):
    • Assuming that the modifyworld config has use-material-names to false, use "modifyworld.items.have." and pickup to set the items that they are allowed to have/pickup using the regex style listing method. Example, (1-6|268-271) should allow for items 1 through 6 and 268-271. This also has the side effect of making it impossible for them to use anything that they are not supposed to have (such as buckets) as once PEX detects that they have a prohibited item, it immediately takes it away (it can either simply dissappear or be dropped depending on the drop-restricted-item setting)
    • Using "modifyworld.blocks.destroy", I would take away their ability to mine blocks that would not drop anything using wooden tools (14/gold is a good example), but follow it up with a wildcard node
      Code:
      - -modifyworld.blocks.destroy.14
      - modifyworld.blocks.destroy.*
    • "modifyworld.blocks.place" and interact could them be set to a wildcard to let them use and build with what they are allowed to have.
    This is one that I would be setting up a test server on my own machine and using it as the test bed due to the complexity of the setup for fine tuning and such. I hope this helps and gives you some ideas on how to approach it.
     
  23. Offline

    Valiant

    That's already what I'm doing :) (referring to the test machine)
    You have been an awesome help and I hope to work with you on issues and things again in the future! Thanks very much!
     
    Justin The Cynical likes this.
  24. Offline

    Leenert

    Okey - Now I did it like this:
    HTML:
            - -modifyworld.vehicle.collide
            - -modifyworld.vehicle.destroy
            - essentials.home
            - essentials.sethome
            - modifyworld.chat.*
            - modifyworld.*
            - modifyworld.blocks.destroy.*
            - modifyworld.blocks.place.*
            - modifyworld.blocks.interact.*
    But the user is also able du collide with a minecart....

    & I've got an other problem with the chatmnanger...
    I made the config like this:

    HTML:
    chat-range: 20.0
    display-name-format: '%prefix %player%suffix'
    global-message-format: %prefix %player%suffix: &4%message
    enable: true
    message-format: %prefix %player%suffix: %message
    ranged-mode: true
    
    Now i start the server and get theese errors:

    HTML:
    2011-12-09 22:12:42 [SEVERE] Error occurred while enabling ChatManager v1.15 (Is it up to date?): while scanning for the next token; found character %'%' that cannot start any token
    while scanning for the next token
    found character %'%' that cannot start any token
     in "<reader>", line 3, column 24:
        global-message-format: %prefix%player%suffix: %message
                               ^
    
        at org.yaml.snakeyaml.scanner.ScannerImpl.fetchMoreTokens(ScannerImpl.java:358)
        at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:179)
        at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingValue.produce(ParserImpl.java:591)
        at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:161)
        at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:146)
        at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:133)
        at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:237)
        at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160)
        at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:123)
        at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:106)
        at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:121)
        at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:480)
        at org.yaml.snakeyaml.Yaml.load(Yaml.java:423)
        at org.bukkit.util.config.Configuration.load(Configuration.java:89)
        at org.bukkit.plugin.java.JavaPlugin.getConfiguration(JavaPlugin.java:118)
        at ru.tehkode.chatmanager.bukkit.ChatManager.onEnable(ChatManager.java:52)
        at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:188)
        at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:957)
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:280)
        at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:184)
        at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:167)
        at org.bukkit.craftbukkit.CraftServer.reload(CraftServer.java:430)
        at org.bukkit.Bukkit.reload(Bukkit.java:187)
        at org.bukkit.command.defaults.ReloadCommand.execute(ReloadCommand.java:22)
        at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:165)
        at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:372)
        at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:756)
        at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:721)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:714)
        at net.minecraft.server.Packet3Chat.a(Packet3Chat.java:33)
        at net.minecraft.server.NetworkManager.b(NetworkManager.java:226)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:92)
        at net.minecraft.server.NetworkListenThread.a(SourceFile:108)
        at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:516)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:414)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:457)]/html]
    
    Pls Help
    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Sep 9, 2018
  25. Offline

    Jäsef

    something is wrong with your config(you've used an invalid symbol etc.)
     
  26. Offline

    Leenert

    i know - but which symbol is wron? cause i don't know :D
     
  27. Offline

    Jäsef

    Code:
    found character %'%' that cannot start any token
     in "<reader>", line 3, column 24:
        global-message-format: %prefix%player%suffix: %message                   ^
                               
    see that ^ ? it points at the error, so i suppose it has something to do with the way your golbal-message-format is formatted

    EDIT:
    Lol, the ^is supposed to be pointing at the % in "%prefix" xD
     
  28. Offline

    Yoogoo

    THX! so much!
     
  29. Offline

    joudar11

    How can i set that the group jailed can't use this permission?
    HomeX.*
     
  30. Offline

    SmileyB

    We normally used bpermissions, and we are transferring over to PEX, we did it on our test server, then had it working, and transferred it to SQL made sure it was working fine, then we tried to transfer it to our player server. Most of the permissions work fine, but for some reason suffixes/prefixes don't work. Our test server and build server are the same, they both use herochat, and the same plugins. Any ideas on what we shoudl do?
     
  31. Offline

    benthamanowns

    How exactly do you edit permissions? I opened with notepad like the rest and it looks wierd. is there a certain program i should use?
     

Share This Page