Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4 Bugs report. #234

Closed
Ecilpse opened this issue Mar 11, 2017 · 1 comment
Closed

4 Bugs report. #234

Ecilpse opened this issue Mar 11, 2017 · 1 comment

Comments

@Ecilpse
Copy link

Ecilpse commented Mar 11, 2017

  1. using the 'breakWhiteList' in the new Floor Configuratioin
    'breakWhiteList' is not working properly. I tried to use the recently updated Floor Configuration. Whenever I tried to load the plugin it says it is not compatible with the faction plugin (which I don't use in my server). I did not see any other noticable error messages.

  2. {[teleoprt] // x,y,z // // W 0.5, D 3 } sign was not working properly. I had about 60 regular mobs on the regular field and 1 boss in a boss zone(all in a same world but seperated) and I wanted to connect two seperate rooms with the teleport sign and be active only when over half of the mobs are killed. But for some reason it was not activating properly even though I killed all regular mobs on the field. please review this matter.

  3. [lobby], [start] signs were not recognizing the pitch and yaw (the angle and the location of the player when he/she was placing the sign), At all cases, both signs were heading south.
    same issue occured on the ./dxl portal.
    I could not make these portals face East. I can manually changed it with worldedit, but it resets and faces south everytime I relaunch the server so its no use. Could you modify these signs and portals so they can respect the pitch and yaw?

  4. For some reason, all players in my server could read the player death, dungeon failure messages from any dungeon. Is it possible to change this so only players within the dungeon can red these notice messages?

@Sataniel98
Copy link
Member

  1. The breakWhiteList is not supposed to be working ATM and already marked as "CURRENTLY UNUSED".

  2. Duplicate of Wave trigger doesn't work #163

  3. I don't really consider this a high priority thing, but eventually yes.

  4. I'll fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants