安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题








This has been found, random targets (Distilled Chaos) off of two AoE cards (Flag Quake/Lightning Spear) currently crashes the game. It will be updated and fixed soon.
This is intended
Game crashed.
Version Info:
- Java version (1.8.0_144)
- Slay the Spire (12-18-2022)
- ModTheSpire (3.30.3)
Mod list:
- basemod (5.52.3)
- stslib (2.10.0)
- reliquary (0.5.2)
- spirelocations (1.1.1)
- CardAugments (1.0.1)
- coloredpowertips (2.3.0)
- HighlightPath (0.0.3)
- MysteryDungeon (2.0.2) == (character mod)
- clockworkchar (1.0.5) == (character mod)
- theflagbearer (1.2.1) == (character mod)
Mods in stacktrace:
- spirelocations (1.1.1)
Cause:
java.lang.IllegalArgumentException: n must be positive
at com.badlogic.gdx.math.RandomXS128.nextLong(RandomXS128.java:110)
at com.badlogic.gdx.math.RandomXS128.nextInt(RandomXS128.java:99)
at com.megacrit.cardcrawl.random.Random.random(Random.java:65)
at SpireLocations.nodemodifiers.special.OtherColorModifier.modifyRewards(OtherColorModifier.java:80)
at SpireLocations.patches.nodemodifierhooks.ModifyRewardsPatch.addModifiersRewards(ModifyRewardsPatch.java:21)
at com.megacrit.cardcrawl.screens.CombatRewardScreen.setupItemReward(CombatRewardScreen.java:108)
at com.megacrit.cardcrawl.screens.CombatRewardScreen.open(CombatRewardScreen.java:370)
at com.megacrit.cardcrawl.rooms.AbstractRoom.update(AbstractRoom.java:437)
at com.megacrit.cardcrawl.dungeons.AbstractDungeon.update(AbstractDungeon.java:2532)
at com.megacrit.cardcrawl.core.CardCrawlGame.update(CardCrawlGame.java:876)
at com.megacrit.cardcrawl.core.CardCrawlGame.render(CardCrawlGame.java:423)
at com.badlogic.gdx.backends.lwjgl.LwjglApplication.mainLoop(LwjglApplication.java:225)
at com.badlogic.gdx.backends.lwjgl.LwjglApplication$1.run(LwjglApplication.java:126)
Hi there,
Downloaded Spire Locations to see if I could replicate this. I passed through a node for picking up a Defect card and another one for a Silent card and StS did not crash. I wonder if this is maybe a one off bug? Additionally, in the stack trace it only seems to say it was Spire Locations but I recognise that SL might've been trying to access something it couldn't in another mod (because idk if that'd show in the stack trace).
At the moment I don't think there's anything I can do about it and I'm not sure what else I can think of.
Since we know what node it happened around, maybe just keep note of what color it's giving you for that particular node and see if it crashes (as this may point to another character mod)?
If it happens again in my mod lmk and I can look into it again.
Thanks!
Thanks! This has been fixed with 1.3.1 =)
There is currently no fix for this but may be fixed in a future patch.
Got this via running a power heavy build with the relic that sets a card's cost to 0 when a power is played + banner ignition and the Trinket (from the Trinket's mod) that is innate and draws a random power from deck.
Hello again, I tried to replicate this bug by using the console and was unable to replicate it.
What I did:
>Remove my current hand (not discarded, exhausted)
>Add/Play three upgraded rewinds and a banner ignition (last, so I only had 2 cards)
>Add two strikes and allow the end of turn to discard them
Result:
>2 strikes were added next turn
>5 cards were drawn
Were there any other conditions you can think of during the crash? I'm not sure if you would like to, but could you can try replicating it on your end with console commands? I'm also wondering if it might also be a strange interaction with something from the Trinket's mod.
Since moving on from that particular fight, have not reproduced this. Will keep an eye out, but a mod interaction is entirely possible.
Will keep an eye and let you know if I can get a reliable reproduction of it.
Figured it out - this was an issue from the Hallownest mod, not an issue with this mod. I had thought I had that mod disabled when this occurred, but that was incorrect.