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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug Fix with Starter Icon Sprites along with adjustment for the Starter UI #1134

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

karl-police
Copy link
Contributor

@karl-police karl-police commented May 19, 2024

This took way too long 馃拃

If this Pull Request gets denied, solely because there are //...

That's why it took so long, I had to figure shit it out. And I don't want people to have to figure too much shit out, so I put comments. I'd have put more documentation but, I kept it related to this Pull Request.

So, if you solely deny this Pull Request because there are // comments that explain stuff. Then something is wrong with you and you hate people. 馃憤

Okay, good.

Explanation

Currently, in the game, when you turn a shiny Pokemon to a non-shiny then use the arrow keys to move to a different Pokemon. The Sprite resets back to shiny. (Only if you own a shiny)

With selection I mean this thing:
image
image

So, I changed that, but it wouldn't make sense to solely change the icon not resetting back. If the entire statistics change back.

It's caused by lastSpeciesIcon. Because I have no clue why that existed, I've commented it out incase it was for something. But I doubt.

With that I also had to comment out its checkIconId. I have absolutely no idea, what the hell the purpose of checkIconId is.

Changes

The starter selection will also remember the last value. So if I go back to, it will remain non-shiny.

Currently, it only remembers changes made to Shiny, because I am not sure how many would want the other values to remain when switching back. It shouldn't matter though, because the game, literally selects a Nature based on whatever you have unlocked. So something default doesn't really exist? 馃 Well, maybe for the Nature since all are the same if you have all. But not for the abilities.

However, I can easily add the other properties as well, since they're all stored in a goofy table called customizedProps. Similar to how starter values are stored when you have them added to the party, but all at one place.

But note that if you have a chosen starter right here:
image

Currently the game will actually keep all the modifications you've set, which I think is nice. Like that you don't have to unselect the starter to make modifications. In the other hand, the selected sprite icon never updates. Which is another bug.

Regardless though, I've made it so that it will forget all customized properties if you return to the main menu.

@Icehawk78
Copy link
Contributor

I think if the selected shiny value is remembered (which I agree that it should be) then it would make the most sense to have all of the other selectable props also be remembered.

Additionally, would it be possible to not have the customized properties forgotten by returning to the main menu? This is already how moves work, so it seems better to have all properties that have been changed persist.

@karl-police
Copy link
Contributor Author

I think if the selected shiny value is remembered (which I agree that it should be) then it would make the most sense to have all of the other selectable props also be remembered.

Additionally, would it be possible to not have the customized properties forgotten by returning to the main menu? This is already how moves work, so it seems better to have all properties that have been changed persist.

Alright, will change that.

The way I do it seems goofy, cuz I wanna save unnecessary memory. So only changed stuff goes inside the customized prop, but honestly it's creating an entry for every thing you cycle through. I didn't create a Class or Interface for it, the entire thing is already chaos, but I put comments.

@karl-police
Copy link
Contributor Author

I think if the selected shiny value is remembered (which I agree that it should be) then it would make the most sense to have all of the other selectable props also be remembered.

Additionally, would it be possible to not have the customized properties forgotten by returning to the main menu? This is already how moves work, so it seems better to have all properties that have been changed persist.

Changed, and now the starter that is selected, also visually changes

Since the logic of the starter gui is already accounting any changes made even when you have a starter already selected.

image
image

@karl-police karl-police changed the title Bug Fix with Sprites along with adjustment for the Starter UI Bug Fix with Starter Icon Sprites along with adjustment for the Starter UI May 19, 2024
@Tempo-anon Tempo-anon added the Bug Something isn't working label May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants