-
Notifications
You must be signed in to change notification settings - Fork 109
Contributing to IITC‐CE
Third-party patches are absolutely essential in IITC "Community Edition". However, they're not the only way to get involved with IITC development. You can help the project tremendously by discovering and reporting bugs; helping others on Reddit, Telegram IITC Group chat, and GitHub issues; and spreading the word about IITC-CE among your teammates and friends.
Everyone is invited to participate in the IITC-CE community and related projects: we want to create a welcoming and friendly environment. Harassment of participants or other unethical and unprofessional behavior will not be tolerated in our spaces. The Contributor Covenant applies to all projects under the IITC-CE organization.
IITC uses GitHub Actions to build and deploy. By default, you already have the ability to get IITC and IITC Mobile builds in your PRs (if you create a PR with a target as your fork or original repository) and publishing artifacts in your GitHub releases.
You can also set up publishing beta and release builds if you wish. To do this, first replace the encrypted keystore at mobile/keystore/android.jks with your own. Then open your repository fork » Settings » Secrets » Actions and specify the following values:
-
KEYSTORE_PASS
- secure password for your keystore. -
ALIAS_NAME
- identifying name for your key. -
ALIAS_PASS
- secure password for your key. -
WEBSITE_REPO
- full name of repository with your website (as your_name/repository_name) -
API_TOKEN_GITHUB
- used if you specified the website repository name. You can retrieve theAPI_TOKEN_GITHUB
here (set therepo
permissions). -
TG_BOT_TOKEN
- specify a Telegram bot token to send IITC Mobile (release and beta) builds to Telegram -
TG_CHAT_ID
- used if you specified TG_BOT_TOKEN. Unique identifier for target chat. How to get unique identifier from telegram api:curl https://api.telegram.org/bot<token>/getUpdates
Not only does your contribution to IITC and its community earn our gratitude, but it also makes you AWESOME.
Join this approved list of awesome people and help us push the limits of what's possible with community efforts!
For IITC users
-
Guide on how to migrate data from an legacy version of IITC Mobile
-
(click to expand )
Cache (Data caching to prevent reloading)
Controls (Map controls/widgets)
Draw (Allow drawing things onto the current map so you may plan your next move)
Highlighter (Portal highlighters)
- Hide portal ownership
- Highlight portals by level color
- Highlight inactive portals
- Highlight portal weakness
- Highlight high level portals
- Highlight portals by my level
- Highlight portals with ornaments
- Highlight portals that need recharging
- Highlight portals with ornaments
- Highlight portals that need recharging
- Highlight portals missing resonators
- Highlight portals with infrastructure problems
Info (Display additional information)
- Available AP statistics
- Portal count
- Portals list
- Player level guess
- Localized scoreboard
- Missions
- Scoring cycle / checkpoint times
- Layer count
Layer (Additional map layers)
- Find farms on map
- Portal Level Numbers
- Overlay KML / GPX / GeoJSON
- Ingress scoring regions
- Zaprange
- Player activity tracker
- Portal Names
- Keys on map
Map Tiles (Alternative map layers)
- Stamen.com map layers
- Blank map
- Gray Google map
- Bing maps
- OpenStreetMap.org map
- Gaode (高德地图) / AutoNavi map
- Kartverket.no maps (Norway)
- Yandex maps
Portal Info (Enhanced information on the selected portal)
Tweaks (Adjust IITC settings)
Misc (Unclassified plugins)
For plugin developers
For IITC developers