Anonymous Login
2021-09-24 15:35 UTC

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0001943OpenClonkScenariospublic2017-12-26 21:30
Assigned ToLuchs 
Product Version 
Target Version8.0Fixed in Version8.0 
Summary0001943: Boomshire: Goal not implemented correctly
DescriptionIn Boomshire you'll spawn on a random checkpoint, followed by a massive amount of ERROR spam in the console (when debug mode is active)
TagsNo tags attached.
Attached Files




Caesar (developer)

Uh, what are the conditions for triggering this? (I just opened the editor and moved my clonk to the first checkpoint and then into lava. It didn't happen.)


K-Pone (developer)

Last edited: 2017-09-24 14:50

View 2 revisions

Just started the game. NativeException joined the game, and it happend right at the beginning. I spawned at checkpoint 10, which is not where you start normally. Also had a respawn delay of 10 seconds which should also not happen.


Clonkonaut (developer)

Cannot reproduce locally. Is it a network-only bug?

The goal itself in Boomshire is nothing special. It's the regular Parkour goal.


K-Pone (developer)

I can still reproduce this as of afa348ab21. I can recheck this once the new snapshots are built and available.


Clonkonaut (developer)

I can reproduce this with the snapshot not with my self-built engine though. This is scary.


Caesar (developer)

I can reproduce this with my self-built engine. But I need two players.


Caesar (developer) seems to set the wrong priority on an internal effect, which causes all those beautiful errors. But if you fix that, the problem of spawning in the wrong position remains.


Clonkonaut (developer)

Why is the priority causing these effects?


Caesar (developer)

I don't know, I don't understand effects. I just set the priority to 1 and that does it. Wasn't there something that effects with priority != 1 have some weird replacement/stacking semantics?

Also, I debugged around a bit further and saw that the position gets set correctly in Objects.ocd/Goals.ocd/Parkour.ocd/Script.c:468 (JoinPlayer). So it gets messed up somewhere else after that. Good luck. (I have no idea how to debug something like this. Maybe stack-dump all calls to SetPosition from the Engine. Brrr.)


Maikel (developer)

I can't reproduce this unfortunately.

Maybe you can overload SetPosition in C4Sript to see if something remarkable happens there:

global func SetPosition(...)
  Log("%d", FrameCounter());
  return _inherited(...);

Framecounter I typically use to see if stuff happens in the same frame.


occ (reporter)

Hi! There's been a check-in that references this bug. For more information you can visit the repository browser at this address:

Changeset 2ab1408 by Lukas Werling <>
Fix Boomshire spawn position (0001943)


Caesar (developer)

Last edited: 2017-12-26 21:30

View 2 revisions

For future reference:
22:28:14 < Luchs> The Relaunch rule has its own spawn position handling that kicks in if the rule is created.
22:28:33 < Luchs> I didn't investigate why this only happens in network rounds...
22:29:48 < Luchs> In any case, the Parkour goal also creates a restart entry in the rule menu, so that call isn't necessary in any case.


-Issue History
Date Modified Username Field Change
2017-09-21 23:10 K-Pone New Issue
2017-09-24 01:30 Caesar Note Added: 0005780
2017-09-24 14:50 K-Pone Note Added: 0005781
2017-09-24 14:50 K-Pone Note Edited: 0005781 View Revisions
2017-10-25 12:47 Clonkonaut Status new => feedback
2017-10-25 12:47 Clonkonaut Note Added: 0005802
2017-10-25 14:12 K-Pone Note Added: 0005814
2017-10-25 14:12 K-Pone Status feedback => new
2017-10-25 23:45 Clonkonaut Status new => confirmed
2017-10-25 23:45 Clonkonaut Note Added: 0005826
2017-10-28 04:02 Caesar Note Added: 0005884
2017-10-28 04:24 Caesar Note Added: 0005885
2017-11-01 00:40 Clonkonaut Note Added: 0005889
2017-11-02 12:43 Caesar Note Added: 0005890
2017-11-10 16:17 Maikel Note Added: 0005896
2017-12-24 10:31 Luchs Assigned To => Luchs
2017-12-24 10:31 Luchs Status confirmed => assigned
2017-12-26 13:16 occ Note Added: 0005967
2017-12-26 13:16 Luchs Status assigned => resolved
2017-12-26 13:16 Luchs Resolution open => fixed
2017-12-26 13:16 Luchs Fixed in Version => 8.0
2017-12-26 21:30 Caesar Note Added: 0005975
2017-12-26 21:30 Caesar Note Edited: 0005975 View Revisions
+Issue History