Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asset Color Expander: Building color set in ACE are ignored in TMPE CustomGetColor #1063

Closed
klyte45 opened this issue Mar 13, 2021 · 4 comments
Labels
BUG Defect detected COMPATIBILITY Mod (in)compatibility / checker confirmed Represents confirmed issue or bug Overlays Overlays, data vis, etc.
Milestone

Comments

@klyte45
Copy link

klyte45 commented Mar 13, 2021

Describe the problem

Hi Guys! I got back to work in Skylines and I found a incompatibility issue: The color was set in the Asset Color Expander mod is being ignore in a custom GetColor method implemented in TMPE. I pointed the code conflict below.

Steps to reproduce

  1. Subscribe and activate the Asset Color Expander
  2. Load a game
  3. Go to button, select the ACE tab and add a new rule
  4. Type of rule filter = By Service
  5. Allowed service =
  6. Then go to second inner tab (Color settings) and change the coloring mode to Color List
  7. Add a color in the list by clicking "+" button
  8. It should change the color of all buildings of the city to that, but it have no effect

Log files

N/A

Extra appointments

I took a look in the TMPE code and found where possibly is the incompatibility source: at TMPE/TLM/TLM/Custom/AI/CustomBuildingAI

It's applying the code of the default BuildingAI behaviour, instead of call the original method. ACE uses a pre-method patch to apply the color selection: BuildingAIOverrides at ACE repo

If there's a reason for it and I need to change ACE code to add this support, let me know and I will apply it.

Thanks!

@klyte45 klyte45 added BUG Defect detected triage Awaiting issue categorisation labels Mar 13, 2021
@krzychu124
Copy link
Member

Like we've talk on discord, it won't be an issue once #1060 gets merged. I'll add this issue to autoclose on merge 😉

@krzychu124 krzychu124 added COMPATIBILITY Mod (in)compatibility / checker confirmed Represents confirmed issue or bug Overlays Overlays, data vis, etc. and removed triage Awaiting issue categorisation labels Mar 14, 2021
@krzychu124 krzychu124 mentioned this issue Mar 14, 2021
4 tasks
@krzychu124 krzychu124 added this to the 11.6.0 milestone Nov 19, 2021
@kianzarrin
Copy link
Collaborator

@krzychu124 is this fixed?

@krzychu124
Copy link
Member

Weird, I thought I added this issue to autoclose after merge... (PR had closes keyword but didn't work 🤷‍♂️ )

@klyte45
Copy link
Author

klyte45 commented Jan 3, 2022

May you wrote them in list (ex: Closes #00A, #00B, #00C) instead of creating a entry to each?
(ex: Closes #00A; Closes #00B; Closes #00C)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG Defect detected COMPATIBILITY Mod (in)compatibility / checker confirmed Represents confirmed issue or bug Overlays Overlays, data vis, etc.
Projects
None yet
Development

No branches or pull requests

3 participants