Fabric Wiki

User Tools

Site Tools

Trace:
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 revision		Previous revision
Next revisionBoth sides next revision
tutorial:accesswideners [2020/04/27 06:51] – fix typo upcraftlptutorial:accesswideners [2020/05/18 05:01] – [File format] typos glitch
Line 1: Line 1:
 ====== Access Wideners ====== ====== Access Wideners ======
  
-Access wideners provide a way to loosen the access limits of classes, methods or fields. Access wideners similar to the commonly known Access Transformers.+Access wideners provide a way to loosen the access limits of classes, methods or fields. Access wideners are similar to the commonly known Access Transformers.
  
-Access wideners should only be used where mixin does not currenly provide a means to do so.+Access wideners should only be used where mixin does not currently provide a means to do so.
  
 ===== Requirements ===== ===== Requirements =====
Line 11: Line 11:
 ===== File format ===== ===== File format =====
  
-A specific file format is used to define the access changes included in your mod. To aid IDE's a 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. 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.
Line 25: Line 25:
 </code> </code>
  
-Any whitespace can be used to sperate in the access widner file, tab is recommended.+Any whitespace can be used to separate in the access widener file, tab is recommended.
  
 Class names are separated with a / and not . Class names are separated with a / and not .
Line 41: Line 41:
 == Methods == == Methods ==
  
-Method access can be changed by specifying the access, class name, method name and method descriptior as named the mappings namespace defined in the header.+Method access can be changed by specifying the access, class name, method name and method descriptor as named the mappings namespace defined in the header.
  
 <code [enable_line_numbers="true"]> <code [enable_line_numbers="true"]>
Line 54: Line 54:
 == Fields == == Fields ==
  
-Field access can be changed by specifying the access, class name, field name and field descriptior as named the mappings namespace defined in the header.+Field access can be changed by specifying the access, class name, field name and field descriptor as named the mappings namespace defined in the header.
  
 <code [enable_line_numbers="true"]> <code [enable_line_numbers="true"]>
Line 63: Line 63:
   - className is the owner class   - className is the owner class
   - fieldName is the field name   - fieldName is the field name
-  - fieldDesc is the field descriptior+  - fieldDesc is the field descriptor
  
 ===== Access Changes ===== ===== Access Changes =====
tutorial/accesswideners.txt · Last modified: 2024/04/01 19:23 by matjojo