User Tools

Site Tools


tutorial:accesswideners

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
tutorial:accesswideners [2021/08/07 22:13] modmuss50tutorial:accesswideners [2021/10/26 12:14] modmuss50
Line 19: Line 19:
 A specific file format is used to define the access changes included in your mod. To aid IDE's you should use the ''.accesswidener'' file extension. A specific file format is used to define the access changes included in your mod. To aid IDE's you should use the ''.accesswidener'' file extension.
  
-The file must start with the following header, ''namespace'' should match the mappings namespace of your mod's source code, this is usually ''named''. Loom will remap the access widener file for you into ''intermediary'' along with your mod. If you use a custom ''RemapJarTask'', set ''remapAccessWidener'' property on it to ''true'' to ensure this happens.+The file must start with the following header, ''namespace'' should usually always be ''named''. Loom will remap the access widener file for you into ''intermediary'' along with your mod. If you use a custom ''RemapJarTask'', set ''remapAccessWidener'' property on it to ''true'' to ensure this happens.
  
 <code [enable_line_numbers="true"]> <code [enable_line_numbers="true"]>
Line 25: Line 25:
 </code> </code>
  
-**Once again, the namespace should match ''named'' when using yarn names and ''intermediary'' when using intermediary names.**+**Once again, the namespace should be ''named'' in most if not all cases**
  
 Access widener files can have blank lines and comments starting with # Access widener files can have blank lines and comments starting with #
tutorial/accesswideners.txt · Last modified: 2024/06/09 05:33 by haykam