Ticks don't affect blocks changing states in 1.16.210.57 Beta (eg Crops and Saplings won't grow)

Same goes for Nether Warts. They simply won't grow, like sugar cane. 

Same goes for Nether Warts. They simply won't grow, like sugar cane. 

and how do we solve it? that answer does not appear to help me with our problem

and how do we solve it? that answer does not appear to help me with our problem

At the top right of this thread, there is a section to vote. Please vote for this issue. Then 'follow' it and you will get updates as the situation progresses :)Unfortunately this is not the only bug in Minecraft. Many people are accepted by different bugs across all platforms and versions. Patients and voting for the issue helps. 

At the top right of this thread, there is a section to vote. Please vote for this issue. Then 'follow' it and you will get updates as the situation progresses :)Unfortunately this is not the only bug in Minecraft. Many people are accepted by different bugs across all platforms and versions. Patients and voting for the issue helps. 

The bug tracker is for helping you craft bug reports to send to Mojang. An outline of the bug reporting process follows:

1. A community member reports a suspected bug. Additional community members may upvote and/or add comments with additional information about the bug.

2. The bug tracker staff, who are volunteers from the community, filter out reports that are not about bugs or do not follow basic rules for writing a report. We combine duplicate reports and verify that the problem is reproducible (because the developers can't fix what they can't see). When we can, we reproduce it ourselves to try and obtain more details that will help the developers.

3. We then pass the enhanced report to Mojang for them to enter into their internal bug management system.

4. We continue to monitor the delivered bug reports for additional comments from the community. If new information becomes available that we think would be substantially helpful to the developers, we have a mechanism for drawing their attention to it.

5. Otherwise, we wait until they report a fix for the bug in a changelog. We capture the fix version on the bug tracker report. When in our judgment the problem has been fixed for everybody, we resolve the original bug report.

Note that the focus here on the bug tracker is on reporting, not fixing, the bug. We do not have access to the code, the developer team, or Mojang's internal systems, so we can neither debug the problem ourselves nor answer questions about Mojang's progress toward a fix.

In the case of this bug, it was first reported in a Beta release and has not been reported in a regular release of the game, so it's most likely been introduced in code for new features being worked on for 1.17. That code is in active development right now and is being tested frequently, so I would expect it to be fixed in the next Beta release or the one after that (but there can be no guarantee).

The bug tracker is for helping you craft bug reports to send to Mojang. An outline of the bug reporting process follows:

1. A community member reports a suspected bug. Additional community members may upvote and/or add comments with additional information about the bug.

2. The bug tracker staff, who are volunteers from the community, filter out reports that are not about bugs or do not follow basic rules for writing a report. We combine duplicate reports and verify that the problem is reproducible (because the developers can't fix what they can't see). When we can, we reproduce it ourselves to try and obtain more details that will help the developers.

3. We then pass the enhanced report to Mojang for them to enter into their internal bug management system.

4. We continue to monitor the delivered bug reports for additional comments from the community. If new information becomes available that we think would be substantially helpful to the developers, we have a mechanism for drawing their attention to it.

5. Otherwise, we wait until they report a fix for the bug in a changelog. We capture the fix version on the bug tracker report. When in our judgment the problem has been fixed for everybody, we resolve the original bug report.

Note that the focus here on the bug tracker is on reporting, not fixing, the bug. We do not have access to the code, the developer team, or Mojang's internal systems, so we can neither debug the problem ourselves nor answer questions about Mojang's progress toward a fix.

In the case of this bug, it was first reported in a Beta release and has not been reported in a regular release of the game, so it's most likely been introduced in code for new features being worked on for 1.17. That code is in active development right now and is being tested frequently, so I would expect it to be fixed in the next Beta release or the one after that (but there can be no guarantee).