#(ikuria) Cannot modify read-only score

26 messages · Page 1 of 1 (latest)

lime canyonBOT
#

(ikuria) Cannot modify read-only score

#

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.

untold heron
nocturne terraceBOT
# untold heron !checklog https://paste.denizenscript.com/View/118971
Server Version

Paper version git-Paper-349 (MC: 1.20.4)-- (Current build :white_check_mark:)

Plugin Version(s)

Denizen v1.3.0-SNAPSHOT (build 6965-DEV) -- (Current build :white_check_mark:)

Checked For

@untold heron

Online/Offline

Offline, but proxied.

UUID Version

4 (:white_check_mark: Online)

Java Version

17 :white_check_mark:

Other Noteworthy Plugin(s)

WorldGuard v7.0.9+5934e49, ProtocolLib v5.1.1-SNAPSHOT-669

Possibly Relevant Plugin(s)

ViaVersion v4.9.3-SNAPSHOT - Mixed client vs server versions can sometimes cause packet-related issues.
HeadDatabase v4.18.3 - HeadDatabase has been known to cause issues with skins.
CMI v9.6.9.3 - CMI tends to mess with a large variety of server features and often gets in the way of issue debugging.
Multiverse-Core v4.3.12 - Multi-world configuration plugins may affect NPCs in unexpected ways.
FastAsyncWorldEdit v2.8.5-SNAPSHOT-639;a4a1126 - This plugin has been known to break the plugin load order on many servers, due to usage of the 'loadbefore' directive in its 'plugin.yml'.

Potentially Bad Line(s)

Starting Minecraft server on *:25569 - server is offline but has no address bind. This might mean you're using a system level firewall, but if not, it means your proxy is bypassable by hackers. Either enable a system level firewall, or bind your server to localhost in server.properties via server-ip=127.0.0.1.
[10:12:18] [Server thread/ERROR]: Error occurred while enabling Denizen v1.3.0-SNAPSHOT (build 6965-DEV) (Is it up to date?) :warning: Log contains error messages.

untold heron
#

denizen wants to modify a read-only score?! all scripts deactivated

#

found the problem in scoreboard.yml

  TEST:
    Viewers: []
    Objectives:
      Patient:
        Criteria: health
        Display slot: BELOW_NAME
        Scores:
          Ikuria: 20
      Sekunden:
        Criteria: dummy
        Display slot: SIDEBAR
        Scores:
          Lacri: 30
      player:
        Criteria: dummy
        Display slot: NONE

it was an old test that was not valid (read-only change)
would be handy to make a kind of check for this, to dont break the full plugin

#

possible /bugthread ?

neat ridgeBOT
#
Changed to Bug

Thread is now a Bug thread. This indicates a core code bug that a developer must resolved, not an error message or other support topic. Please do not misuse the Bug label. Use </helpthread:1028674284870180883> to switch the thread back to a normal help thread if you are not 100% confident it is a code bug.

thorny field
untold heron
#

dont ask, as i can see it was a "TEST" maybe wrong typing or something... its old, so i removed it

neat ridgeBOT
#
Changed to Help/Support

Thread is now a Help/Support thread. A helper will check your thread when available.

fading otter
untold heron
#

its not manually changed

#

but yes, i dunno what i've tested or which command i used wrong to get that scoreboards.yml

#

but it looks like this example:

#Make the defined player see the health of other players below their names
- scoreboard add viewers:<[player]> id:test obj:anything criteria:health displayslot:below_name```
fading otter
#

That code needed a cleanup anyway, so while cleaning I also made sure ScoreboardHelper definitely cannot save score values when the criteria is read-only

neat ridgeBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@untold heron

neat ridgeBOT
#
Resolved

Thread closed as resolved.

#
Thread Reopened

Thread was manually reopened by @untold heron.

deep verge
#

!rule 8

nocturne terraceBOT
# deep verge !rule 8
Rule 8

Don't overuse the edit/delete buttons. https://denizenscript.com/discord_rules#rule8
Use the edit button to fix typos, and the delete button to remove an accidental post shortly after posting.
Do not remove a post that pings someone, do not edit or delete a post that people have already replied to.

deep verge
#

@untold heron

neat ridgeBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@untold heron