When sculk blocks replace soul sand in ancient cities, any soul fire on top of them is not extinguished

When an ancient city generates, there's a chance for soul sand to be replaced by a sculk blocks. When this happens, any soul fire on top of the soul sand remains lit even though soul fire cannot normally be ignited on sculk blocks. This bug occurs in Java Edition Deep Dark Experimental Snapshot 1, and from 22w13a to the present (1.21.7 rc2).

This bug can occur in four structures, it occurs in "ancient_city/city_center/city_center_1"; "ancient_city/city_center/city_center_2"; "ancient_city/city_center/city_center_3"; "ancient_city/structures/barracks". This bug cannot be recreated by feeding a sculk block to replace a soul block, it only occurs in ancient cities (Sorry if it takes me a while to update versions, sometimes it is very difficult for me to use my computer to do the tests).

Steps to reproduce the issue

1. Go to seed 0, coordinates 799 -42 1262 (It's an example, the error is quite common).

2. Look at the block below the soul fire (Without upgrading the soul fire block).

3. Look, the block is not soul sand.

Expected result

There may be several possible solutions, some of which I propose:

• Soul sand should not be replaced (Quick and easy solution).

• Fire should not be started (Complicated and unnecessary).

• Let the normal fire appear, and also not disappear over time (Personal favorite).

• Make it a feature and pretend it was always planned and not fix anything (Simplest).

Actual result

Soul fire appears on a sculk block, something that should be impossible.

If the fire is upgraded, the fire will disappear