CloverberryClose
- CloverberryClose
- JIRAUSER604789
- Europe/Stockholm
- Yes
- No
MC-233228
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post (https://walshy.dev/blog/21_03_16-mc-new-text-filtering), I found a way to use this feature to filter chat on my 1.17.1 server:
(Server.properties) text-filtering-config=
{"apiServer": "http://localhost:8000","apiKey": "aaaaaaaa","ruleId": 1,"serverId": "test","hashesToDrop": 2,"maxConcurrentRequests": 4}NodeJS Script: https://pastebin.com/TjvzgYae
(Both from Walshy's blog post)
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post (https://walshy.dev/blog/21_03_16-mc-new-text-filtering), I found a way to use this feature to filter chat on my 1.17.1 server:
(Server.properties) text-filtering-config=
{ "apiServer": "http://localhost:8000", "apiKey": "aaaaaaaa", "ruleId": 1, "serverId": "test", "hashesToDrop": 2, "maxConcurrentRequests": 4 }NodeJS Script: https://pastebin.com/TjvzgYae
(Both from Walshy's blog post)
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his
blog post (https://walshy.dev/blog/21_03_16-mc-new-text-filtering),I found a way to use this feature to filter chat on my 1.17.1 server:
{ "apiServer": "http://localhost:8000", "apiKey": "aaaaaaaa", "ruleId": 1, "serverId": "test", "hashesToDrop": 2, "maxConcurrentRequests": 4 }
(Server.properties)text-filtering-config=NodeJS Script: https://pastebin.com/TjvzgYae
(Both from Walshy's blog post)
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post[,|https://walshy.dev/blog/21_03_16-mc-new-text-filtering),] I found a way to use this feature to filter chat on my 1.17.1 server:
In the server.properties file, text-filtering-config=
{ "apiServer": "http://localhost:8000", "apiKey": "aaaaaaaa", "ruleId": 1, "serverid": "test", "hashesToDrop": 2, "maxConcurrentRequests": 4 }And, NodeJS Script listening at port 8000: https://pastebin.com/TjvzgYae**
(Both from Walshy's blog post)
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post[,|https://walshy.dev/blog/21_03_16-mc-new-text-filtering),] I found a way to use this feature to filter chat on my 1.17.1 server
:
In the server.properties file, text-filtering-config=
{ "apiServer": "http://localhost:8000", "apiKey": "aaaaaaaa", "ruleId": 1, "serverid": "test", "hashesToDrop": 2, "maxConcurrentRequests": 4 }And, NodeJS Script listening at port 8000: https://pastebin.com/TjvzgYae**
(Both from Walshy's blog post)
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post[,|https://walshy.dev/blog/21_03_16-mc-new-text-filtering),] I found a way to use this feature to filter chat on my 1.17.1 server.
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post[,|https://walshy.dev/blog/21_03_16-mc-new-text-filtering),] I found a way to use this feature to filter chat on my 1.17.1 server.
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
Setup:
1. In the server.properties file, text-filtering-config=
{ "apiServer": "http://localhost:8000", "apiKey": "aaaaaaaa", "ruleId": 1, "serverid": "test", "hashesToDrop": 2, "maxConcurrentRequests": 4 }2. And, NodeJS Script listening at port 8000: https://pastebin.com/TjvzgYae (Both from Walshy's blog post)
3. Start the server, and put a message in chat that would be filtered by the script (for example, in this case, the word 'herobrine').
What should happen:
The chat message should be filtered according to the script, and then appear accordingly for all other players (in this case, the word 'herobrine' should appear as '*********').
What happens:
In versions 21w20a and above, the messages pass unfiltered. Everyone, including the sender and receiver(s), can see the original message irrespective of whether it was supposed to be filtered or not.
I have attached the client logs of the sender and receiver in both, 21w19a and 21w20a. Both the servers had identical setups (including server.properties and node.js scipt) and were newly generated servers.
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post[,|https://walshy.dev/blog/21_03_16-mc-new-text-filtering),] I found a way to use this feature to filter chat on my 1.17.1 server.
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
Setup:
1. In the server.properties file, text-filtering-config=
{ "apiServer": "http://localhost:8000", "apiKey": "aaaaaaaa", "ruleId": 1, "serverid": "test", "hashesToDrop": 2, "maxConcurrentRequests": 4 }2. And, NodeJS Script listening at port 8000: https://pastebin.com/TjvzgYae (Both, 1. and 2. are from Walshy's blog post)
3. Start the server, and put a message in chat that would be filtered by the script (for example, in this case, the word 'herobrine').
What should happen:
The chat message should be filtered according to the script, and then appear accordingly for all other players (in this case, the word 'herobrine' should appear as '*********').
What happens:
In versions 21w20a and above, the messages pass unfiltered. Everyone, including the sender and receiver(s), can see the original message irrespective of whether it was supposed to be filtered or not.
I have attached the client logs of the sender and receiver in both, 21w19a and 21w20a. Both the servers had identical setups (including server.properties and node.js scipt) and were newly generated servers.
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post
[,|https://walshy.dev/blog/21_03_16-mc-new-text-filtering),]I found a way to use this feature to filter chat on my 1.17.1 server.But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
Setup:
1. In the server.properties file, text-filtering-config=
{ "apiServer": "http://localhost:8000", "apiKey": "aaaaaaaa", "ruleId": 1, "serverid": "test", "hashesToDrop": 2, "maxConcurrentRequests": 4 }2. And, NodeJS Script listening at port 8000: https://pastebin.com/TjvzgYae
(Both, 1. and 2. are from Walshy's blog post)3. Start the server, and put a message in chat that would be filtered by the script (for example, in this case, the word 'herobrine').
What should happen:
The chat message should be filtered according to the script, and then appear accordingly for all other players (in this case, the word 'herobrine' should appear as '*********').
What happens:
In versions 21w20a and above, the messages pass unfiltered. Everyone, including the sender and receiver(s), can see the original message irrespective of whether it was supposed to be filtered or not.
I have attached the client logs of the sender and receiver in both, 21w19a and 21w20a. Both the servers had identical setups (including server.properties and node.js scipt) and were newly generated servers.
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post, I found a way to use this feature to filter chat on my 1.17.1 server.
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
Setup:
1. In the server.properties file, text-filtering-config=
{ "apiServer": "http://localhost:8000", "apiKey": "aaaaaaaa", "ruleId": 1, "serverid": "test", "hashesToDrop": 2, "maxConcurrentRequests": 4 }2. And, NodeJS Script listening at port 8000: https://pastebin.com/TjvzgYae (Both, 1. and 2. are from Walshy's blog post)
3. Start the server, and put a message in chat that would be filtered by the script (for example, in this case, the word 'herobrine').
What should happen:
The chat message should be filtered according to the script, and then appear accordingly for all other players (in this case, the word 'herobrine' should appear as '*********').
What happens:
In versions 21w20a and above, the messages pass unfiltered. Everyone, including the sender and receiver(s), can see the original message irrespective of whether it was supposed to be filtered or not.
I have attached the client logs of the sender and receiver in both, 21w19a and 21w20a. Both the servers had identical setups (including server.properties and node.js scipt) and were newly generated servers.
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post, I found a way to use this feature to filter chat on my 1.17.1 server.
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
Setup:
1. In the server.properties file, text-filtering-config=
{ "apiServer": "http://localhost:8000", "apiKey": "aaaaaaaa", "ruleId": 1, "serverid": "test", "hashesToDrop": 2, "maxConcurrentRequests": 4 }2. And, NodeJS Script listening at port 8000: https://pastebin.com/TjvzgYae (Both, 1. and 2. are from Walshy's blog post)
3. Start the server, and put a message in chat that would be filtered by the script (for example, in this case, the word 'herobrine').
What should happen:
The chat message should be filtered according to the script, and then appear accordingly for all other players (in this case, the word 'herobrine' should appear as '*********').
What happens:
In versions 21w20a and above, the messages pass unfiltered. Everyone, including the sender and receiver(s), can see the original message irrespective of whether it was supposed to be filtered or not.
I have attached the client logs of the sender and receiver in both, 21w19a and 21w20a. Both the servers had identical setups (including server.properties and node.js scipt) and were newly generated
servers.1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post, I found a way to use this feature to filter chat on my 1.17.1 server.
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
Setup:
1. In the server.properties file, text-filtering-config=
{ "apiServer": "http://localhost:8000", "apiKey": "aaaaaaaa", "ruleId": 1, "serverid": "test", "hashesToDrop": 2, "maxConcurrentRequests": 4 }2. And, NodeJS Script listening at port 8000: https://pastebin.com/TjvzgYae (Both, 1. and 2. are from Walshy's blog post)
3. Start the server, and put a message in chat that would be filtered by the script (for example, in this case, the word 'herobrine').
What should happen:
The chat message should be filtered according to the script, and then appear accordingly for all other players (in this case, the word 'herobrine' should appear as '*********').
What happens:
In versions 21w20a and above, the messages pass unfiltered. Everyone, including the sender and receiver(s), can see the original message irrespective of whether it was supposed to be filtered or not.
I have attached the client logs of the sender and receiver in both, 21w19a and 21w20a. Both the servers had identical setups (including server.properties and node.js scipt) and were newly generated worlds.
1.16.4 Pre-release 1 added a feature called "text-filtering-config" to server.properties which allowed the server to filter text written by players in chat and in written books.
This was an unfinished feature, but with the help of Walshy and his blog post, I found a way to use this feature to filter chat on my 1.17.1 server.
But the filter refused to work in 1.17.1, so I started testing it in various versions, and eventually found out that it was working perfectly till Snapshot 21w19a, but suddenly broke in 21w20a (around about when the switch to Java 16 was made).
Setup:
1. In the server.properties file, text-filtering-config=
{ "apiServer": "http://localhost:8000", "apiKey": "aaaaaaaa", "ruleId": 1, "serverid": "test", "hashesToDrop": 2, "maxConcurrentRequests": 4 }2. And, NodeJS Script listening at port 8000: https://pastebin.com/TjvzgYae (Both, 1. and 2. are from Walshy's blog post)
3. Start the server, and put a message in chat that would be filtered by the script (for example, in this case, the word 'herobrine').
What should happen:
The chat message should be filtered according to the script, and then appear accordingly for all other players (in this case, the word 'herobrine' should appear as '*********').
What happens:
In versions 21w20a and above, the messages pass unfiltered. Everyone, including the sender and receiver(s), can see the original message irrespective of whether it was supposed to be filtered or not.
I have attached the client logs of the sender and receiver in both, 21w19a and 21w20a. Both the servers had identical setups (including server.properties and node.js scipt) and were newly generated worlds.
Well, the thing is that on my ssp, I have a trading hall with villagers in minecarts who quickly take trades and stuff, but on my smp with 2-3 players, villagers in minecarts are refusing to take any trades. They were earlier taking trades, but now they’re not. I suspect this could be because of lag, since about half an hour earlier, I had set random tick speed to 1000 for 5-10 minutes and there was some lag at the time, but then the server stabilised. That possibly messed with the villagers.