Obfuscater isn't workin right on engine mode 1

Discussion in 'Spigot Discussion' started by tschagg, Apr 4, 2013.

  1. hi guys.

    when i use engine mode 1, theres no difference to see with xray.
    engine mode 2 works good, but its buggy with flickering stones n stuff.

    why does engine mode 1 not work?

    Build number: #735

    config:
    # This is the main configuration file for Bukkit.
    # As you can see, there's actually not that much to configure without any plugins.
    # For a reference for any variable inside this file, check out the bukkit wiki at
    # http://wiki.bukkit.org/Bukkit.yml
    settings:
    allow-end: true
    warn-on-overload: false
    permissions-file: permissions.yml
    update-folder: update
    ping-packet-limit: 100
    use-exact-login-location: false
    plugin-profiling: true
    connection-throttle: 4000
    query-plugins: true
    deprecated-verbose: default
    shutdown-message: Server restart
    filter-unsafe-ips: false
    whitelist-message: You are not white-listed on this server!
    log-commands: true
    command-complete: true
    spam-exclusions:
    - /skill
    tab-ping: true
    timeout-time: 60
    restart-on-crash: true
    restart-script-location: /MineResort/mc/script.sh
    bungee-proxies:
    - 127.0.0.1
    texture-resolution: 16
    snapshot-protocol: false
    world-settings:
    default:
    growth-chunks-per-tick: 650
    mob-spawn-range: 4
    random-light-updates: false
    aggregate-chunkticks: 4
    item-merge-radius: 3.5
    exp-merge-radius: 3.5
    wheat-growth-modifier: 100
    cactus-growth-modifier: 100
    melon-growth-modifier: 100
    pumpkin-growth-modifier: 100
    sugar-growth-modifier: 100
    tree-growth-modifier: 100
    mushroom-growth-modifier: 100
    entity-activation-range-animals: 32
    entity-activation-range-monsters: 32
    entity-activation-range-misc: 16
    entity-tracking-range-players: 48
    entity-tracking-range-animals: 48
    entity-tracking-range-monsters: 48
    entity-tracking-range-misc: 32
    entity-tracking-range-max: 64
    info: true
    world:
    growth-chunks-per-tick: 1000
    world_nether:
    view-distance: 5
    growth-chunks-per-tick: 0
    random-light-updates: true
    water-creatures-per-chunk: 0
    spawn-limits:
    monsters: 70
    animals: 15
    water-animals: 5
    ambient: 15
    chunk-gc:
    period-in-ticks: 600
    load-threshold: 0
    ticks-per:
    animal-spawns: 400
    monster-spawns: 1
    autosave: 0
    auto-updater:
    enabled: false
    on-broken:
    - warn-console
    - warn-ops
    on-update:
    - warn-console
    - warn-ops
    preferred-channel: rb
    host: dl.bukkit.org
    suggest-channels: true
    orebfuscator:
    enable: true
    engine-mode: 1
    update-radius: 2
    disabled-worlds:
    - world_the_end
    blocks:
    - 1
    - 5
    - 14
    - 15
    - 16
    - 21
    - 48
    - 49
    - 54
    - 56
    - 73
    - 74
    - 82
    - 129
    - 130
    config-version: 2
     
  2. SuperSpyTX

    Supporter

    Pictures?

    EDIT: If you meant ores change as soon as you break blocks (with XRay on, if you break the blocks, some of the ores surrounding the chunk/area changes). That's normal.
     
  3. wait i upload a pic

    thats with engine mode 1: doesn't work ;([​IMG]
     
    #3 tschagg, Apr 4, 2013
    Last edited: Apr 4, 2013
  4. SuperSpyTX

    Supporter

    Picture for the second problem listed?
     
  5. on engine mode 2?
     
  6. no, the users telling me, they see fake blocks poppin in all the time, but for me , i never saw it...
    are they using xray?
    why isnt enginemode 1 workin?

    thanks!
     
  7. SuperSpyTX

    Supporter

    I'll investigate into Engine mode 1. This may be a problem related to my last patch.

    EDIT: If it helps, Engine Mode 1 is only meant to reduce visibility of ores from really close distance. This probably is useful for those who want to reduce lag on other users. In my opinion, I don't think it works well.

    I didn't see any problems related to what you shown me on the picture

    That is when after they break a block, they see fake ore behind it then it vanishes. To fix this, grab the latest spigot build (Builds 755 or newer) and change update-radius in orebfuscator to something higher (4). This will reduce the occurrence of fake ores showing right behind stone blocks.

    EDIT: Woops, my response was in the quote >.>
     
    #7 SuperSpyTX, Apr 4, 2013
    Last edited: Apr 4, 2013
  8. aaah nice, thank you so much!

    EDIT: yeah i saw it now myself , sometimes i see a fakeblocks for maybe 0.1 sec poppin up. i hope the radius will fix it :)