[1.16.3] Custom Villager Point of Interest and professions not working

[link1213]

I am trying to create a custom villager profession "drug_dealer" but I can't get any villagers to become this profession. I believe that I set up and registered the profession and point of interest correctly so I really can't figure out what the case of the issue is

 

This is my class that set up the point of interest

public class PointsOfInterestInit
{
    public static DeferredRegister<PointOfInterestType> POI_TYPES = DeferredRegister.create(ForgeRegistries.POI_TYPES, FunWithDrugs.MOD_ID);
    
    public static Set<BlockState> getAllStates(Block block) {
        return ImmutableSet.copyOf(block.getStateContainer().getValidStates());
    }
    
    public static final RegistryObject<PointOfInterestType> DRUG_DEALER_TYPE = POI_TYPES.register("drug_dealer_type",
            () -> new PointOfInterestType("drug_dealer_type", getAllStates(Blocks.GOLD_BLOCK), 1, 1));
    

}

I used the gold block as a testing block since my own mod blocks don't work either

 

this is my class that sets up the villager profession

public class VillagerInit 
{
	public static DeferredRegister<VillagerProfession> PROFESSIONS = DeferredRegister.create(ForgeRegistries.PROFESSIONS, FunWithDrugs.MOD_ID);
	
	 
	public static final RegistryObject<VillagerProfession> DRUG_DEALER = PROFESSIONS.register("drug_dealer",
			() -> new VillagerProfession("drug_dealer", PointsOfInterestInit.DRUG_DEALER_TYPE.get(), ImmutableSet.of(), ImmutableSet.of(), SoundEvents.ENTITY_VILLAGER_WORK_BUTCHER));
	

}

 

I don't see what the issue is with the way i set it up but still no villagers will become this profession

 

[link1213]

I have checked the log, everything is indeed being registered so I can safely say that that is not the issue

[vemerion]

  On 10/11/2020 at 8:21 PM, link1213 said:

I have checked the log, everything is indeed being registered so I can safely say that that is not the issue

Expand  

As far as I know, the Point of Interest system is broken, see this github issue for a workaround.