It's been a while since I looked at those mods so I don't know if they've been kept alive through updates.įor those following, if you get into it the 2 official addons for Kerbal are pretty good as well and on Steam at least they're often on sale. Kerbal is smaller than Earth and the resulting reduced gravity makes everything significantly easier. Speaking of the realism mods there were a bunch of mods that would change the Kerbin System back into our Solar System which is harder. Realism is generally harder but in some ways MechJeb is more realistic than hand flying to orbit, even if some of the functions are easy to fly by hand. A simple template visitor is .symbol.KSDefaultVisitor.įor sample implementations of the SymbolProcessorProvider and SymbolProcessor interfaces, see the following files in the sample project.Īfter writing your own processor, register your processor provider to the package by including its fully-qualified name in resources/META-INF/services/.processing.SymbolProcessorProvider.Ĭreate another module that contains a workload where you want to try out your processor.The overwhelming number and nature of the mods is the reason I didn't mention CKAN or realism mods. Use resolver.getSymbolsWithAnnotation() to get the symbols you want to process, given the fully-qualified name of an annotation.Ī common use case for KSP is to implement a customized visitor (interface .symbol.KSVisitor) for operating on symbols. Your main logic should be in the SymbolProcessor.process() method.

Pass dependencies that your processor needs (such as CodeGenerator, processor options) through the parameters of SymbolProcessorProvider.create().

Implement SymbolProcessorProvider.create() to create a SymbolProcessor. Your implementation of SymbolProcessorProvider will be loaded as a service to instantiate the SymbolProcessor you implement. You'll need to implement .processing.SymbolProcessor and .processing.SymbolProcessorProvider.

Ksp mac mac demo