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

[GENERAL] vore belly turned out to be united for everyone #170

Closed
AzzyDreemurr13 opened this issue Mar 12, 2024 · 5 comments
Closed

[GENERAL] vore belly turned out to be united for everyone #170

AzzyDreemurr13 opened this issue Mar 12, 2024 · 5 comments

Comments

@AzzyDreemurr13
Copy link
Contributor

AzzyDreemurr13 commented Mar 12, 2024

Brief description of the bug

Vore bellies have for some reason combined for all characters, regardless of the new or old character

What you expected to happen

Each character has different settings of vore belly

What actually happened

vore belly turned out to be united for everyone

Steps to reproduce

Code Revision

Server revision: B:release D:
Commit: bdbfcb8d9c5488e0473a1fefabef762e1420936a

Anything else you may wish to add:

  • (Location if it's a mapping issue, screenshots, sprites, etc.)
@lm40
Copy link
Collaborator

lm40 commented Apr 17, 2024

Well as far as I can tell across three of your four characters your vore bellies are actually the same, how did this come to pass? It never happened to me so I will need steps to reproduce.

@AzzyDreemurr13
Copy link
Contributor Author

I have no idea how this happened, I noticed it when I started playing Merry and Lori on server, and the bellies are all set for Astel ._ .

@AzzyDreemurr13
Copy link
Contributor Author

Perhaps a stupid hypothesis, but maybe something with SQL Tables happened for my CCkay and characters, what caused this

@lm40
Copy link
Collaborator

lm40 commented Apr 18, 2024

If you make new characters they do copy bellies of existing characters, I will need steps to reproduce in order to prove that this is actually unintended behavior

@AzzyDreemurr13
Copy link
Contributor Author

The problem is no longer relevant

@AzzyDreemurr13 AzzyDreemurr13 closed this as not planned Won't fix, can't repro, duplicate, stale May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants