[SEC/MECH/FUN] PreciousStones 7.0.2 - Block Area Proteciton System [1337]

I want to make a stone, that when placed will protect chests - but i don't want all of my stones to protect chests(furnances, etc)

If that's not already possible and i am missing something(explain), can you make this possible?

When creating a cuboid field, I can visualise it but my players can't. Is there a permission node to allow that?

Nope, only the person creating the field can see it. The blocks exist only on his client. They are never really changed on the server. That's why its called a visualization.

That's cool. He claimed he couldn't see it. I'll blame derp.

Second question: I have a bouncer field (as per default config) and when someone enters it they get returned to spawn. Is this the expected behaviour? I'd rather they were just moved back to where they came from...

That looks an awful lot like the Zombe path tracker. Can PS even make lines like that?

Running into a similar issue. Blocks set-up just fine, work great.
Steps to Replicate:
a) Proximity
b) grifer revert
c) city protection
All blocks worked fine.
did a /save-all on server
/stop
Restarted Server
Only C remains, A,B are no longer precious stones, the blocks are still there.
-- bonus round---
Broke down the blocks A, B. Replaced them in same identical spot. They work again AND (A) reported past log events + (B) was able to rollback griefing.
/reload
Only C remains, A,B again do not work.
Broke A,B,C - ONLY placed B this time.
/reload
B no longer works.

Seems like some sort of memory->database caching issue. I hope this helps track it down REALLY want this plugin to work, i honestly just want self serve anti griefing.

Started DB from scratch, same problem. Using essentials.
Update 1:
http://forums.bukkit.org/threads/se...ion-v1-6-5-1-anti-x-ray-xray-1060-1185.26043/

Could a server-client ore obfuscator plugin cause this? (Anti Xray)
Update 2:
Nope, removed obfuscater - replicated the results above, this time with 4 city Protect blocks, only the last block was saved after a reload.

Keep in mind I reported a bug already where if you try to place a block down in an identical spot there's a database conflict because the first field hasn't been swept out of the database yet. You end up placing the identical block down and then the old field gets deleted from the database, meaning when you restart it won't be there since it exists only in memory.

Refer to this post for the details on this particular problem: http://forums.bukkit.org/threads/se...oteciton-system-1185.1034/page-50#post-702378

The same could be true for your first example. The plugin may write SQL entries in bursts to prevent excessive i/o access lag, if you restarted the server before the 15 or so seconds that it seems to take for database entries to be written then that would have caused that behavior.

Thnx, i'll look into that

Retried with blocks in different locations same issue.
Also did this on a brand new server, nothing but precious stones installed, out of the box config etc. (no essentials loaded) Same results. (not using MySQL database, just the SQL lite one).

This would make sense except that the final block should not be written as well.
On a blank db, new server I just placed 4 PS's in a row. All worked. Waited a minute, verified the db file was written to, /reload, only the final block was working, the first 3 no longer were registered as precious stones. (Blocks showed up fine on the server of course)

Any ideas? Seems like an easily replicable bug...

I couldn't replicate it with SQL, but I did notice with an earlier version (6.2) that I was getting async warnings about PreciousStones while using the /reload command.

Which four pstones are you placing? I've tried placing multiple combinations and veried that they are written to the database. All survive on /reload.

Aight, did the most vanilla install of bukkit possible Latest recommended build 1185, precious stones 6.3, default config file, absolutely nothing else changed. New world seed generated, PS database had not yet been created. Using SQLlite file system.
Identical results, only the last block is saved. Server loaded up fine, no errors whatsoever.

Sounds like the only difference between your environment is SQL vs SQLLite. I'll give that a go next and see if i can narrow it down. Very excited about this plugin, hoping this testing helps the developer a fair bit

Tried it with Town Protect(Diamond_block), and Griefer Rollback (Gold_block) seperatly. Doesn't matter which stones i use, all the same result

MySQL installing right now.. stay tuned.

When I use /ps visualize I can break the glass blocks and even stand on top of them. Interacting with the blocks in any way via right-click causes them to disappear. This isn't just happening client-side either, other connected players can see you running around in the air.

The glass blocks are now stuck as "visualize" mode won't turn off. Using "/ps visualize" in this state tells me that I have insufficient permissions (this is as on op and administrator privs) or it is an invalid command.

Reconnecting makes the visualization disappear and the 4 pstones I placed are no longer in the database (they were city protection blocks arranged in a 2x2 patter). The weird thing is that the blocks somehow got deleted from the database with no /reload or server restart.

Tried to reproduce the problem by standing on top of the four City Protection blocks and using /ps visualize. It caused the server to hang and I had to do a forced restart. Restarted the server, confirmed the four fields, tried visualize again and the server hung a second time forcing another restart.

Alright! Found the source of the problem - the mysqlLite portion is what's messed up. Works PERFECTLY with a MYSQL server connection. Hopefully they can fix asap

Noticed this too, it's not a big problem for Op's however non ops will get booted for "flying" when the client walks on the glass blocks.

Ohh perfect. Thanks for narrowing this down for me.

I found the "problem" with the visualization and the server hanging. One block is fine, but for every precious stone you put on top of that it's a performance issue. Putting four of the blocks together seems to cause a massive CPU hit that lags out the entire server when you perform the visualization.

I might have to turn off visualizations because of this. It's very speedy for just one block but if a player put down 5-6 blocks together it could easily crash the server.

Example, I placed 9 City Protection blocks in a 3x3 array. Doing /ps visualize I did not notice any appreciable spike in CPU usage (26%) but then all players get disconnected with timeout notices and one of my cores spikes pretty hard.

The server never really "crashes", it just hangs waiting for the process to finish out. After the visualization is done players can reconnect again. If you don't have placement limits on field blocks it seems like a way to easily grief a server if you got enough pstones blocks together.

This was also the issue with the visualization not disappearing. It was four city protection fields and the server was hung during the visualization routine, so my client could run around and walk on the blocks without them disappearing.

Watching the resource monitor, CPU usage is fine but during the attempt disk usage spikes a bit and network usage spikes to the maximum and stays there for about 20-30 seconds. I imagine it's trying to send 9 visualizations to the client at the same time?

I tried a MySQL connection instead, and it seems to work after reloads and restarts of the server.

Had to turn off noflying protection because when I was testing out the launchpad block setting it to maximum and having it launch a non-op player was causing him to get disconnected for "flying".

Yes you have to allow flying in your server.properties.

I'll can add a config variable to only visualize one field at a time.

Hello! I'm using mySQL. When i save a custom cuboid shape region with the draw mode, the region revert to is initial shape after a reload (or start/stop) on the server. In addition, the region initial shape is not correct : the command "/ps visualize" and left clicking on the ground != the actual region shape region.

Preciousstones Version: 6.3
CB: 1185

Great plugin be the way

Preciousstones Version: 6.3
CB: 1185
Economy: iConomy v5

Code:

2011-10-02 16:12:45 [INFO] [PreciousStones] Version 6.3 loaded
2011-10-02 16:12:45 [INFO] [PreciousStones] MySQL Connection successful
2011-10-02 16:12:46 [INFO] [PreciousStones] (world) fields: 3,766
2011-10-02 16:12:46 [INFO] [PreciousStones] (world_nether) fields: 5
2011-10-02 16:12:46 [INFO] [PreciousStones] Payment method: iConomy v5

No errors.
On creation of making a field I have the "Price: 1000" flag to charge 1000$

Code:

-   title: City Protection
    block: 57
    radius: 20
    custom-height: 15
    prevent-use:
    - 58
    - 61
    prevent-fire: true
    prevent-place: true
    prevent-destroy: true
    prevent-explosions: true
    prevent-unprotectable: true
    prevent-flow: true
    welcome-message: true
    farewell-message: true
    cuboid: false
    price: 1000

It doesnt charge the $, and on deletion of the field it refunds the money. Allowing users to "make" money by creating fields and removing them.

So players could make a sort of 'secret invisible bridge' and then use visualize to activate it?

You can use the "visualization.end-on-player-move" config setting to end the visualization once the player moves.

Anything on this?

Please notify when there's a patch. I've also had a problem where every reload/restart would wipe all the fields of the server...causing extreme player hate toward me

Im using MYSQL server connection, and anyone can destroy the actual field stone even if theyre not the owner of it. The fields are protecting the wrong size and leaving randon áreas unprotected. My config is:

Code:

bypass-blocks:
- 39
- 40
- 51
- 59
unbreakable-blocks: []
unprotectable-blocks:
- 54
- 58
- 61
- 62
tool-items:
- 269
force-field-blocks:
-   title: Legendary_Protection
    block: 73
    radius: 10
    custom-height: 128
    breakable: false
    prevent-place: true
    prevent-destroy: true
    prevent-explosions: true
    prevent-pvp: false
    prevent-use: true
    welcome-message: true
    farewell-message: true
    cuboid: true
log:
    entry: false
    fire: true
    pvp: false
    place: false
    use: true
    destroy: false
    destroy-area: false
    unprotectable: true
    bypass-pvp: true
    bypass-delete: true
    bypass-place: false
    bypass-destroy: true
    bypass-unprotectable: true
    conflict-place: true
notify:
    place: true
    destroy: true
    bypass-pvp: true
    bypass-unprotectable: true
    bypass-destroy: true
    bypass-place: true
warn:
    entry: true
    fire: true
    pvp: true
    place: true
    use: true
    destroy: true
    destroy-area: true
    unprotectable: true
    instant-heal: true
    slow-heal: true
    slow-damage: true
    fast-damage: true
    give-air: true
    launch: true
    cannon: true
    mine: true
    slow-feeding: true
    slow-repair: true
forester:
    forester-trees: 60
    interval-seconds: 1
    fertile-blocks:
    - 2
    - 3
    - 13
    - 87
    trees: 60
grief-undo:
    interval-seconds: 300
    black-list:
    - 8
    - 9
    - 10
    - 11
    - 92
visualization:
    block-type: 20
    seconds: 30
    end-on-player-move: true
    admin-chunk-radius: 10
    mark-block-type: 20
    mark-chunk-radius: 10
    frame-block-type: 20
    spread-divisor: 130
settings:
    public-block-details: true
    allowed-can-break-pstones: false
    sneaking-bypasses-damage: true
    drop-on-delete: true
    disable-alerts-for-admins: true
    disable-bypass-alerts-for-admins: true
    off-by-default: false
    lines-per-page: 12
    inactivity-purge-days: 45
    blacklisted-worlds: []
    log-to-hawkeye: true
    debug-on: false
saving:
    frequency-seconds: 15
    max-records-per-snitch: 50
cleanup:
    player-inactivity-purge-days: 45
    snitch-unused-purge-days: 30
mysql:
    enable: true
    username: *******
    host: *******
    password: *******
    database: ******
cuboid:
    visualization-blocktype: 20
    defining-blocktype: 49
repairable-items: []

I have web as a creature repeller and have set "cuboid: true" but sneak-left click doesn't work.

is this something specific to web?

Probably

can you look at my older post?

Is that happening with every stone or is it random? And to confirm this is with the latest build of SC?