#149334: "Earning one more brutality scroll while already capped leads to many js errors"
What is this report about?
What happened ? Please select from below
What happened ? Please select from below
Please check if there is already a report on the same subject
If yes, please VOTE for this report. Reports with the most votes are taken care of in PRIORITY!
| # | Status | Votes | Game | Type | Title | Last update |
|---|
Detailed description
-
• Please copy/paste the error message you see on your screen, if any.
Error occured during notification scrollMoved, while B2-18 is revealed and the active beheaded already have the maximum number of brutality scroll
see snipboard.io/UINhP8.jpg
-
• Please explains what you wanted to do, what you do and what happened
• What is your browser?
Google Chrome v131
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
Error occured during notification scrollMoved, while B2-18 is revealed and the active beheaded already have the maximum number of brutality scroll
see snipboard.io/UINhP8.jpg
• What is your browser?
Google Chrome v131
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Error occured during notification scrollMoved, while B2-18 is revealed and the active beheaded already have the maximum number of brutality scroll
see snipboard.io/UINhP8.jpg
• What is your browser?
Google Chrome v131
-
• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)
Error occured during notification scrollMoved, while B2-18 is revealed and the active beheaded already have the maximum number of brutality scroll
see snipboard.io/UINhP8.jpg
• What is your browser?
Google Chrome v131
-
• Which part of the rules was not respected by the BGA adaptation
Error occured during notification scrollMoved, while B2-18 is revealed and the active beheaded already have the maximum number of brutality scroll
see snipboard.io/UINhP8.jpg
-
• Is the rules violation visible on game replay? If yes, at which move number?
• What is your browser?
Google Chrome v131
-
• Which was the game action you wanted to do?
Error occured during notification scrollMoved, while B2-18 is revealed and the active beheaded already have the maximum number of brutality scroll
see snipboard.io/UINhP8.jpg
-
• What do you try to do to trigger this game action?
-
• What happened when you try to do this (error message, game status bar message, ...)?
• What is your browser?
Google Chrome v131
-
• At which step of the game did the problem occurs (what was the current game instruction)?
Error occured during notification scrollMoved, while B2-18 is revealed and the active beheaded already have the maximum number of brutality scroll
see snipboard.io/UINhP8.jpg
-
• What happened when you try to do a game action (error message, game status bar message, ...)?
• What is your browser?
Google Chrome v131
-
• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
Error occured during notification scrollMoved, while B2-18 is revealed and the active beheaded already have the maximum number of brutality scroll
see snipboard.io/UINhP8.jpg
• What is your browser?
Google Chrome v131
-
• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Is this text available in the translation system? If yes, has it been translated for more than 24 hours?
Error occured during notification scrollMoved, while B2-18 is revealed and the active beheaded already have the maximum number of brutality scroll
see snipboard.io/UINhP8.jpg
• What is your browser?
Google Chrome v131
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Error occured during notification scrollMoved, while B2-18 is revealed and the active beheaded already have the maximum number of brutality scroll
see snipboard.io/UINhP8.jpg
• What is your browser?
Google Chrome v131
Report history
Javascript error:
During notification scrollMoved
Cannot read properties of undefined (reading 'addItem')
TypeError: Cannot read properties of undefined (reading 'addItem')
at Object.moveItemByType (x.boardgamearena.net/data/themereleases/current/games/deadcells/241212-1405/modules/Area.js:535:41)
at Object.moveScroll (x.boardgamearena.net/data/themereleases/current/games/deadcells/241212-1405/deadcells.js:1:109757)
at Object.notif_scrollMoved (x.boardgamearena.net/data/themereleases/current/games/deadcells/241212-1405/deadcells.js:1:135846)
at r. (x.boardgamearena.net/data/themereleases/241212-1404/js/dojoroot/dojo/dojo.js:1:23207)
at r.i [as onscrollMoved] (x.boardgamearena.net/data/themereleases/241212-1404/js/dojoroot/dojo/dojo.js:1:43133)
at o.emit (x.boardgamearena.net/data/themereleases/241212-1404/js/dojoroot/dojo/dojo.js:1:39135)
at o.emit (x.boardgamearena.net/data/themereleases/241212-1404/js/dojoroot/dojo/dojo.js:1:39762)
at r.emit (x.boardgamearena.net/data/themereleases/241212-1404/js/dojoroot/dojo/dojo.js:1:42740)
at Object.publish (x.boardgamearena.net/data/themereleases/241212-1404/js/dojoroot/dojo/dojo.js:1:42381)
at Object.publish (x.boardgamearena.net/data/themereleases/241212-1404/js/dojoroot/dojo/dojo.js:1:36320)
Script:
Url: boardgamearena.com/2/deadcells?table=601300069
BGA version 241212-1404
U=83876995
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
lordalx's scroll moves forward
Following refresh (F5), game is unable to load and following error is visible in the browser console:
Area.js:535 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'addItem')
at Object.moveItemByType (Area.js:535:41)
at Object.moveScroll (deadcells.js:1:109757)
at Object.setup (deadcells.js:1:15757)
at Object.completesetup (ly_studio.js:1:498947)
at deadcells?table=601300069:2532:28
similar thing happened but in solo when forced to give a scroll to the companion that was already maxed. Reloaded table and now it will not load at all.
Add something to this report
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.
