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

Parties Not Syncing #553

Closed
NielsPilgaard opened this issue Feb 18, 2019 · 6 comments
Closed

Parties Not Syncing #553

NielsPilgaard opened this issue Feb 18, 2019 · 6 comments

Comments

@NielsPilgaard
Copy link

Hey o/

I'm getting reports that quest progress for players in teams is not shared, for some.
I'm unsure what additional info to supply, but I'd be happy to (try to) dig up whatever you need.
Original issue: EnigmaticaModpacks/Enigmatica2#343 (comment)

Versions

  • BetterQuesting-3.5.291
  • StandardExpansion-3.4.151
@Funwayguy
Copy link
Owner

Funwayguy commented Feb 20, 2019

Some of this behaviour might be intentional.

  • Shared loot is a quest side config and not party enforced to better support adventure packs and allows players to leave their parties without losing access to the shared item (especially if it's a key quest item).
  • Party progress sharing is getting changed to disallow "sling-shotting" progress of players joining a party. This means that existing party members will be able to assist new members but they won't inherit progression without an OP forcing such a sync.

Something does appear to be broken here but I'm going to need more information about it to test.

@NielsPilgaard
Copy link
Author

Neither of those intentional behaviours fit the issue: They both started from scratch with no quests completed, and it's the completation of quest tasks that's not shared, AFAIK anyway - We'll see what OP says :)

@Yakaita
Copy link

Yakaita commented Feb 21, 2019

Neither of those intentional behaviours fit the issue: They both started from scratch with no quests completed, and it's the completation of quest tasks that's not shared, AFAIK anyway - We'll see what OP says :)

he is op

@NielsPilgaard
Copy link
Author

OP as in original poster.

@Yakaita
Copy link

Yakaita commented Feb 22, 2019

then are you not op?

@NielsPilgaard
Copy link
Author

I linked to an original issue in the description of this issue, I was refering to the poster of that issue. Either way, it looks like the issue has been resolved, I'll reopen if it starts acting up again - Thanks :)

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

3 participants