보고 • Board Game Arena

모든 보고

데우스 보고

#51805: "At almost endgame, after choosing undo game became unstable"

fixed: 버그가 수정되었습니다

무엇에 대한 보고입니까?

데우스 #212905995

무슨 일이 발생했나요? 아래에서 선택하세요

어느 순간, 게임 인터페이스를 사용할 수 없었습니다

무슨 일이 발생했나요? 아래에서 선택하세요

어느 순간, 게임 인터페이스를 사용할 수 없었습니다

같은 내용에 대하여 이미 등록된 보고가 있는지 확인해주세요

그렇다면, 이 보고를 추천해주세요. 추천을 가장 많이 받은 보고부터 우선적으로 처리됩니다!

#	Status	Votes	Game	Type	Title	Last update

상세한 설명

보고 이력

2021년 Oct 30일 23:39 • Catsbane • 개발자가 아직 버그를 재현하지 않았습니다:

No, nothing solved the problem.

2021년 Oct 30일 23:55 • robinzig • 개발자가 아직 버그를 재현하지 않았습니다:

Thanks for reporting this, and apologies that you are unable to finish your game!

I can follow the link and see the error message reported - that's an error message that exists in the code but should basically never come up in practice. Unfortunately the error page means that I can't easily look at the gamestate to start figuring out what has caused the error here. I do have ways to try to take a look on the development site though, so I will do this - not right now but I will definitely try within the next 24 hours. Apologies again, as soon as I know what's going on I will update you.

2021년 Oct 30일 23:56 • robinzig • 개발자가 버그를 확인했습니다:

forgot to update status

2021년 Oct 31일 01:35 • King Hrothbeort • 개발자가 버그를 확인했습니다:

The bug appeared once and crashed the game. It happened when I hit the "redo turn" button. Game end had been triggered and I was the last player. We should each have had one more turn. F5 and other attempts to reload the game did not solve the problem. A screenshot isn't really help because the only thing on the screen once the error occurred is the error message.

2021년 Oct 31일 01:38 • robinzig • 개발자가 버그를 확인했습니다:

I understand, thanks for the context. I did not expect you to provide anything more - I appreciate that this is not possible. Sadly I don't know if it will be possible to fix this game for you, but I hope to be able to at least figure out what happened and prevent this from happening for others.

2021년 Oct 31일 01:55 • King Hrothbeort • 개발자가 버그를 확인했습니다:

The card I played which triggered the bug was "Workshop" it was when I was supposed to choose which kind of buildings to get, when I hit the "redo turn" button and everything crashed.

2021년 Oct 31일 02:18 • robinzig • 개발자가 버그를 확인했습니다:

thanks for the information - that's really useful. I've done some quick glances at the code and think this must be caused by undo somehow not resetting correctly the card which is supposed to be being resolved. I still don't know why that is happening but as I said I will definitely look at this as soon as I can and see what I can do to resolve it.

2021년 Oct 31일 13:21 • robinzig • 개발자가 버그를 확인했습니다:

To give me more information which I could use to help get to the bottom of this issue - do any of you remember which cards were in that player's scientific/yellow column before the Workshop was played, and at what point was the Undo selected (ie which action were you being asked to do at the time)?

In particular, was there a Laboratory that activates blue cards in that column somewhere? The (very small amount of) additional information I've been able to discover about the error makes me think that was the case, but I would really like some confirmation.

I realise this may be hard to remember and you can't find this information anywhere, but it would greatly help me trying to understand what happened. Thanks.

2021년 Oct 31일 20:03 • King Hrothbeort • 개발자가 버그를 확인했습니다:

Yes I am almost certain there was a laboratory that let me activate a blue card, which I did, I can't remember which blue card I activated; I think it was one that gives victory points, but that might have been one of the other yellow cards. I tried to do the undo when I was supposed to select which buildings to get; I hadn't selected any buildings yet.

2021년 Oct 31일 20:16 • robinzig • 개발자가 버그를 확인했습니다:

Thank you - that's really helpful.

2021년 Nov 1일 01:43 • robinzig • 개발자가 버그를 확인했습니다:

Hi, I'm about to have to go to bed but I thought I owed you an update - and I have a minor question to ask as well.

I've so far been unable to recreate this issue by trying to set up the same scenario in games in the development environment. I've also spent quite a while of tracing through the code, and haven't yet identified a situation where it looks like this could happen. However I do have a potential theory that I will try tomorrow to see if I can get anywhere with - if you are able to confirm to me that it might be relevant.

My question is: did the affected player (KingHrothbeort, it sounds like) also have a card that draws cards (School or University) in that same yellow column? It might sound like a strange question but if so I think it might be key to the root cause of this bug, so I would like to know the answer, one way or another.

Whatever the answer - or even if I don't get one - I will continue looking at this. Unfortunately even if I am able to fix it I don't think I will be able to do anything to rescue your game, but I will still thank you for having drawn my attention to this issue because it will at least mean I can prevent other games in future from reaching this same broken state.

2021년 Nov 1일 13:20 • King Hrothbeort • 개발자가 버그를 확인했습니다:

I might have had a School card in that column, I definitely played one sometime, but that might have been in a different game. We understand that the game is in Beta and problems like this might occur. If the game can't be rescued it would be nice to have it removed so I don't keep getting notifications that it is my turn in a game I can't play. Thanks for your work on this.

2021년 Nov 1일 13:50 • robinzig • 개발자가 버그를 확인했습니다:

Thanks for the info, even if only tentative. I understand how frustrating it is to be told it's your move when you can't actually play - unfortunately this isn't something I can do anything about directly. I'd hoped there would be an option from the table page to abandon the game, but if not someone will have to ask one of the BGA admins - which could take a while :(

I'll keep you updated, both on this and (hopefully) the fix.

2021년 Nov 2일 02:31 • robinzig • 버그가 수정되었습니다:

Hi all,

Thank you for your patience - this is now, I believe, finally fixed.

And by that I mean that this issue should not come up again in any future games. But unfortunately, as I pointed out earlier, because the bug had already happened and made your game enter a corrupted state, there is nothing I can do to salvage it. You can (or at least the table creator can, I believe) quit the game from the table page (boardgamearena.com/table?table=212905995) using the "quit game" button below the big "Go to game" one. I see that your game is in "normal mode" so there may be reputation penalties for doing this - if this bothers you please let me know and I will try to ask BGA admins to cancel these.

I thank you all again for bringing this issue to my attention - it was sure to strike another table before too long given the number of games now being played so I am happy to have got it fixed, and I would never have known about the issue had you not raised this bug. (It turned out the Laboratory wasn't important - the issue would arise any time a player uses the Undo facility after a card draw, provided only that - and this was the reason I hadn't seen the issue in testing - there was at least one card to be resolved in between the drawing card and the one during whose resolution the player chooses to undo. That card was a Lab here but the same issue would arise with any card.)

2021년 Nov 2일 13:02 • King Hrothbeort • 버그가 수정되었습니다:

Thank you for fixinf the bug so other players won't encounter this problem.

The link you provided leads to this message:

Sorry, an unexpected error has occurred...

BGA service error
(reference: ST 02/11 13:00:00)

>> Get me out of here <<

2021년 Nov 2일 13:15 • robinzig • 버그가 수정되었습니다:

sorry, the text editor for these comments thought the closing parenthesis was part of the link, which it isn't. Try boardgamearena.com/table?table=212905995

Not that you should need me to give the link, I got it from the top of this page (below "what is this report all about")

리포트에 내용 추가하기

여기에 버그를 재현하거나 당신의 제안을 이해하는 데 관련 있는 내용을 아무것이나 남겨주십시오:

다른 테이블 번호 / 수 번호
새로고침을 해서 문제가 해결 되었습니까?
문제가 얼마나 자주 일어났습니까?
이 버그(좋은 예시)에 대한 스크린샷이 있으면, 호스팅 서비스의 그림을 업로드하고 링크를 복사/붙이기할 수 있습니다 (예를 들어 snipboard.io).

취소 업데이트 보고

#51805: "At almost endgame, after choosing undo game became unstable"

무엇에 대한 보고입니까?

무슨 일이 발생했나요? 아래에서 선택하세요

무슨 일이 발생했나요? 아래에서 선택하세요

같은 내용에 대하여 이미 등록된 보고가 있는지 확인해주세요

상세한 설명

보고 이력

리포트에 내용 추가하기

보고의 상태를 다음으로 변경:

도움말

기여하기

탐색하기

저희를 팔로우해주세요