97
Veteran Member
RIP Telnet
Posts: 889
| Likes: 679
|
Post by 97 on Dec 20, 2019 19:52:17 GMT
Object I don't think I would find the notification that helpful. As others have said, online admins can see if someone does load in a shematic with command spy. What if I say this happens even if you have cmdspy off? |
|
?Robin
Club 4000 Member
caleb get off of tf
Posts: 8,027
| Likes: 8,604
|
Post by ?Robin on Dec 20, 2019 20:06:13 GMT
Object I don't think I would find the notification that helpful. As others have said, online admins can see if someone does load in a shematic with command spy. What if I say this happens even if you have cmdspy off? What if I say this happens even if you have cmdspy off? then they shouldn't have it off if they're administrating |
|
zeseryu
Veteran Member
Admin Officer
ops rights activist
Posts: 1,181
|
Post by zeseryu on Dec 20, 2019 20:24:55 GMT
this is creating a solution to a problem that doesn't exist.
|
|
97
Veteran Member
RIP Telnet
Posts: 889
| Likes: 679
|
Post by 97 on Dec 20, 2019 21:15:19 GMT
this is creating a solution to a problem that doesn't exist. Apologies for me not mentioning this but once I logged on to the server and there was sand and anvil grief everywhere. I thought they did that through some sort of schematic and I do not know if an admin was online. Sometimes though it has happened when staff was online. This isn't a "problem" but those schematics torrent the server |
|
zeseryu
Veteran Member
Admin Officer
ops rights activist
Posts: 1,181
|
Post by zeseryu on Dec 20, 2019 21:32:28 GMT
this is creating a solution to a problem that doesn't exist. Apologies for me not mentioning this but once I logged on to the server and there was sand and anvil grief everywhere. I thought they did that through some sort of schematic and I do not know if an admin was online. Sometimes though it has happened when staff was online. This isn't a "problem" but those schematics torrent the server those aren't through schematics. those are through //sphere or //set |
|
97
Veteran Member
RIP Telnet
Posts: 889
| Likes: 679
|
Post by 97 on Dec 20, 2019 21:35:54 GMT
those are through //sphere or //set Let me elaborate. Sand and anvils are blocked through those actions. So they manually made those (or they used another command like //stack) and saved it as a schematic. Something like that sounds like sense to me. How I got this was the discussion from Panther about the uselessness of blocking stuff in W/E "Any OP can just place the blocks themselves, and if they want to use WorldEdit with the blocks, they just use //copy and //paste to duplicate or move those blocks around. You end up with the same problems you started with that caused the blocks to be banned from WorldEdit in the first place." |
|
zeseryu
Veteran Member
Admin Officer
ops rights activist
Posts: 1,181
|
Post by zeseryu on Dec 20, 2019 21:47:00 GMT
those are through //sphere or //set Let me elaborate. Sand and anvils are blocked through those actions. So they manually made those (or they used another command like //stack) and saved it as a schematic. Something like that sounds like sense to me. How I got this was the discussion from Panther about the uselessness of blocking stuff in W/E "Any OP can just place the blocks themselves, and if they want to use WorldEdit with the blocks, they just use //copy and //paste to duplicate or move those blocks around. You end up with the same problems you started with that caused the blocks to be banned from WorldEdit in the first place." panthers original post was also creating a solution to a problem that doesn't exist. that sand and anvil problem is from falling blocks not being tracked properly by coreprotect. solution? disable falling blocks or literally just build a tower up and manually go through each level until you see "xxxx" placed sand/anvil. it takes maybe 30 seconds. |
|
Panther
Veteran Member
Posts: 721
| Likes: 604
|
Post by Panther on Dec 20, 2019 22:29:26 GMT
Let me elaborate. Sand and anvils are blocked through those actions. So they manually made those (or they used another command like //stack) and saved it as a schematic. Something like that sounds like sense to me. How I got this was the discussion from Panther about the uselessness of blocking stuff in W/E "Any OP can just place the blocks themselves, and if they want to use WorldEdit with the blocks, they just use //copy and //paste to duplicate or move those blocks around. You end up with the same problems you started with that caused the blocks to be banned from WorldEdit in the first place." panthers original post was also creating a solution to a problem that doesn't exist. that sand and anvil problem is from falling blocks not being tracked properly by coreprotect. solution? disable falling blocks or literally just build a tower up and manually go through each level until you see "xxxx" placed sand/anvil. it takes maybe 30 seconds. The problem isn't balls of sand or anvils. What I'm talking about would be, for example, a saved jukebox exploit schematic. It would bypass inventory patches and patches that wipe the jukebox upon its placement because instead of being placed by a player it is pasted in with W/E. In addition to this, there are blocks that can't be logged because of problems with CoreProtect and also can't be logged by placing a tower of blocks above the grief (diamond/iron blocks) and being able to save those blocks in schematics or simply being able to //copy and //paste them is currently causing issues. |
|
zeseryu
Veteran Member
Admin Officer
ops rights activist
Posts: 1,181
|
Post by zeseryu on Dec 20, 2019 22:35:04 GMT
panthers original post was also creating a solution to a problem that doesn't exist. that sand and anvil problem is from falling blocks not being tracked properly by coreprotect. solution? disable falling blocks or literally just build a tower up and manually go through each level until you see "xxxx" placed sand/anvil. it takes maybe 30 seconds. The problem isn't balls of sand or anvils. What I'm talking about would be, for example, a saved jukebox exploit schematic. It would bypass inventory patches and patches that wipe the jukebox upon its placement because instead of being placed by a player it is pasted in with W/E. In addition to this, there are blocks that can't be logged because of problems with CoreProtect and also can't be logged by placing a tower of blocks above the grief (diamond/iron blocks) and being able to save those blocks in schematics or simply being able to //copy and //paste them is currently causing issues. you mean the saved juke box exploit that you exclusively used? |
|
falceso
Veteran Member
Back to being quiet on the forums.
Posts: 350
| Likes: 118
|
Post by falceso on Dec 20, 2019 22:53:05 GMT
The problem with that is that we don't actually go through the logs on a daily basis. Even if we did, we'd have to go through possibly hundreds of log files just to find people loading in or saving schematics and that is just flat out impractical. We do. Vouch. Well, fine.. Make a separate logfile for it... As for " we may fail to notice it", that's going back to we may not have time to check it. We can see it in the logs, that is correct, but to act on it may take some time. |
|
Panther
Veteran Member
Posts: 721
| Likes: 604
|
Post by Panther on Dec 21, 2019 0:22:48 GMT
The problem isn't balls of sand or anvils. What I'm talking about would be, for example, a saved jukebox exploit schematic. It would bypass inventory patches and patches that wipe the jukebox upon its placement because instead of being placed by a player it is pasted in with W/E. In addition to this, there are blocks that can't be logged because of problems with CoreProtect and also can't be logged by placing a tower of blocks above the grief (diamond/iron blocks) and being able to save those blocks in schematics or simply being able to //copy and //paste them is currently causing issues. you mean the saved juke box exploit that you exclusively used? For one, that wasn't exclusively me. For two, that's simply an example, and the process could be duplicated for a different exploit. |
|
