Skip to content

Port AI Shunting From Starlight#3523

Closed
EckoAurum wants to merge 2 commits intoMonolith-Station:mainfrom
EckoAurum:starlight-ai-port
Closed

Port AI Shunting From Starlight#3523
EckoAurum wants to merge 2 commits intoMonolith-Station:mainfrom
EckoAurum:starlight-ai-port

Conversation

@EckoAurum
Copy link
Copy Markdown
Contributor

To Do

  • Port initial shunt PR 1064
  • Get 1064 working with mono
  • pull in bug fixes: 1260, 1330, 1410?, 1829, 2001, 2342, 3039, 3130

About the PR

Why / Balance

Media

Requirements

  • I have read relevant guidelines/documentation to this PR found on our devwiki.
  • I have added media to this PR or it does not require an ingame showcase.
  • I can confirm this PR contains either no AI-generated content, or AI-generated content that meets our guidelines.

How to test

Breaking changes

Changelog

@monolith8319 monolith8319 changed the title Port AI Shunting from Starlight Port AI Shunting From Starlight Mar 22, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Mar 22, 2026

RSI Diff Bot; head commit 32f6a94 merging into eb44dee
This PR makes changes to 1 or more RSIs. Here is a summary of all changes:

Resources/Textures/_Starlight/Interface/Actions/actions_shunt.rsi

State Old New Status
icon-on Added
icon-unshunt Added
icon Added

Edit: diff updated after 32f6a94

@EckoAurum
Copy link
Copy Markdown
Contributor Author

I really don't want to port an entire actions refactor, porting the other one in a new PR

@EckoAurum EckoAurum closed this Mar 30, 2026
@Ilya246
Copy link
Copy Markdown
Contributor

Ilya246 commented Mar 30, 2026

we do need upstream's action refactor however if we don't have it

@EckoAurum
Copy link
Copy Markdown
Contributor Author

we do need upstream's action refactor however if we don't have it

If we do need it i can look specifically into that then come back to this after. I just didnt want to port such a large refactor just for a single ability

@Ilya246
Copy link
Copy Markdown
Contributor

Ilya246 commented Mar 30, 2026

we want upstream refactors because they generally make code easier to work with

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants