Testing 170 - Report issues here

Here’s a death-murder-beast without stripes, taking about 12-16 shots with a copper crossbow to kill.

It seems to me (middle-aged memory notwithstanding) that fossils were more prevalent before. I went on an expedition to get them and ended up with about a 6-to-1 ratio of tech pieces to fossils. Should I be expecting that?

Meanwhile, I was killed by this guy, not just with a single hit, but with no warning. Couldn’t hear it coming, it didn’t make any noise at all. (I was in the cave where you see it…it hung around after I reached Sanctum and I had to wait for it to move away from the portal before running for dear life.) I did a side-by-side comparison of killing a spitter versus a goort, and spitters are the easier kill by far. That seems wonky to me.

Once again, after Steam Update, Boundless [Testing] is crashing before I get to Sanctum on load. I’ve tried deleting and reloading. Last time it appeared to be fixed with another Steam update a week or so later.

OoCuriosity is there some way to directly download? I’d like to be able to eliminate Steam as a possible culprit. I find it hard to believe that my system is so unique that this occurs regularly (though not always) upon update, and I am one of the lucky few it occurs to.

The machine is likely resource poor, and my net connection isn’t the greatest, so I suspect that both are more than the majority of the reason I regularly run into problems.

I’ve included what appears to be the most relevant sections (in oder to fit into the max post size) of what appears to be the crash-report for the latest failure.

Crash Report

Process: cloudd [33235]
Path: /System/Library/PrivateFrameworks/CloudKitDaemon.framework/Support/cloudd
Identifier: cloudd
Version: 651.14 (651.14)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: cloudd [33235]
User ID: 501

Date/Time: 2017-07-30 19:42:32.083 -0400
OS Version: Mac OS X 10.12.4 (16E195)
Report Version: 12
Anonymous UUID: 03559D3F-9B3F-6BCB-C041-0F65769FFC4E

Sleep/Wake UUID: 991FCFBF-2EC0-426A-8086-C49C8DCB4099

Time Awake Since Boot: 460000 seconds
Time Since Wake: 640 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.cloudkit.systemAvailabilityQueue

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
*** Terminating app due to uncaught exception ‘NSGenericException’, reason: ‘Error executing SQL: “pragma journal_mode = WAL” (13) - errcode:000d, msg:“database or disk is full”, size: 81920, path:/Users/USER/Library/Caches/*/CloudKitMetadata, fs:0/91473068032’
abort() called
terminating with uncaught exception of type NSException
rdar://problem/28724618 Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd.

Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff9863337b __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fffad42748d objc_exception_throw + 48
2 CoreFoundation 0x00007fff986b1c3d +[NSException raise:format:] + 205
3 CloudKit 0x00007fff97ed91ea +[CKSQLiteError raise:code:extended:] + 1553
4 CloudKit 0x00007fff97ed444a -[CKSQLite raise:] + 1229
5 CloudKit 0x00007fff97ed4735 -[CKSQLite executeSQL:arguments:] + 206
6 CloudKit 0x00007fff97ed4652 -[CKSQLite executeSQL:] + 142
7 CloudKit 0x00007fff97ed2e4c -[CKSQLite openWithError:] + 946
8 CloudKit 0x00007fff97ed3644 -[CKSQLite open] + 42
9 CloudKitDaemon 0x00007fffa31e0e7c -[CKDMetadataCache init] + 286
10 CloudKitDaemon 0x00007fffa31e0d25 __31+[CKDMetadataCache sharedCache]_block_invoke + 41
11 libdispatch.dylib 0x00007fffadcd68fc _dispatch_client_callout + 8
12 libdispatch.dylib 0x00007fffadcd68b9 dispatch_once_f + 38
13 CloudKitDaemon 0x00007fffa31e0cf9 +[CKDMetadataCache sharedCache] + 45
14 cloudd 0x00000001004c2c84 cloudd + 11396
15 CloudKitDaemon 0x00007fffa3016bb8 __52-[CKDSystemAvailabilityMonitor _systemMayNowBeReady]_block_invoke + 596
16 libdispatch.dylib 0x00007fffadcd68fc _dispatch_client_callout + 8
17 libdispatch.dylib 0x00007fffadcd7536 _dispatch_barrier_sync_f_invoke + 83
18 CloudKitDaemon 0x00007fffa30168b3 -[CKDSystemAvailabilityMonitor _systemMayNowBeReady] + 262
19 CloudKitDaemon 0x00007fffa3016340 __37-[CKDSystemAvailabilityMonitor _init]_block_invoke + 34
20 SetupAssistantFramework 0x00007fffa9ee9a06 +[SAUserSetupState notifyWhenUserIsSetup:withCompletionBlock:] + 519
21 CloudKitDaemon 0x00007fffa30162cc -[CKDSystemAvailabilityMonitor _init] + 293
22 CloudKitDaemon 0x00007fffa3016146 __45+[CKDSystemAvailabilityMonitor sharedMonitor]_block_invoke + 41
23 libdispatch.dylib 0x00007fffadcd68fc _dispatch_client_callout + 8
24 libdispatch.dylib 0x00007fffadcd68b9 dispatch_once_f + 38
25 CloudKitDaemon 0x00007fffa301611a +[CKDSystemAvailabilityMonitor sharedMonitor] + 45
26 cloudd 0x00000001004c1e40 cloudd + 7744
27 cloudd 0x00000001004c2955 cloudd + 10581
28 libdyld.dylib 0x00007fffadd0c235 start + 1
29 ??? 0x0000000000000001 0x0 + 1

Thread 0 Crashed:: Dispatch queue: com.apple.cloudkit.systemAvailabilityQueue
0 libsystem_kernel.dylib 0x00007fffade3ad42 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fffadf285bf pthread_kill + 90
2 libsystem_c.dylib 0x00007fffadda0420 abort + 129
3 libc++abi.dylib 0x00007fffac8f684a abort_message + 266
4 libc++abi.dylib 0x00007fffac91bc4f default_terminate_handler() + 267
5 libobjc.A.dylib 0x00007fffad4296fe _objc_terminate() + 103
6 libc++abi.dylib 0x00007fffac918d69 std::__terminate(void (*)()) + 8
7 libc++abi.dylib 0x00007fffac918de3 std::terminate() + 51
8 libdispatch.dylib 0x00007fffadcd6910 _dispatch_client_callout + 28
9 libdispatch.dylib 0x00007fffadcd68b9 dispatch_once_f + 38
10 com.apple.cloudkit.CloudKitDaemon 0x00007fffa31e0cf9 +[CKDMetadataCache sharedCache] + 45
11 cloudd 0x00000001004c2c84 0x1004c0000 + 11396
12 com.apple.cloudkit.CloudKitDaemon 0x00007fffa3016bb8 __52-[CKDSystemAvailabilityMonitor _systemMayNowBeReady]_block_invoke + 596
13 libdispatch.dylib 0x00007fffadcd68fc _dispatch_client_callout + 8
14 libdispatch.dylib 0x00007fffadcd7536 _dispatch_barrier_sync_f_invoke + 83
15 com.apple.cloudkit.CloudKitDaemon 0x00007fffa30168b3 -[CKDSystemAvailabilityMonitor _systemMayNowBeReady] + 262
16 com.apple.cloudkit.CloudKitDaemon 0x00007fffa3016340 __37-[CKDSystemAvailabilityMonitor _init]_block_invoke + 34
17 com.apple.SetupAssistantFramework 0x00007fffa9ee9a06 +[SAUserSetupState notifyWhenUserIsSetup:withCompletionBlock:] + 519
18 com.apple.cloudkit.CloudKitDaemon 0x00007fffa30162cc -[CKDSystemAvailabilityMonitor _init] + 293
19 com.apple.cloudkit.CloudKitDaemon 0x00007fffa3016146 __45+[CKDSystemAvailabilityMonitor sharedMonitor]_block_invoke + 41
20 libdispatch.dylib 0x00007fffadcd68fc _dispatch_client_callout + 8
21 libdispatch.dylib 0x00007fffadcd68b9 dispatch_once_f + 38
22 com.apple.cloudkit.CloudKitDaemon 0x00007fffa301611a +[CKDSystemAvailabilityMonitor sharedMonitor] + 45
23 cloudd 0x00000001004c1e40 0x1004c0000 + 7744
24 cloudd 0x00000001004c2955 0x1004c0000 + 10581
25 libdyld.dylib 0x00007fffadd0c235 start + 1

Thread 1:
0 libsystem_kernel.dylib 0x00007fffade3b44e __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fffadf25695 _pthread_wqthread + 1426
2 libsystem_pthread.dylib 0x00007fffadf250f1 start_wqthread + 13

Thread 2:: Dispatch queue: com.apple.cloudkit.packagepurger
0 com.apple.Foundation 0x00007fff99f9df30 NSClassFromObject + 0
1 com.apple.Foundation 0x00007fff99fa37d1 -[NSURL(NSURL) _cfurl] + 15
2 com.apple.CoreFoundation 0x00007fff98591bb3 -[NSURL getResourceValue:forKey:error:] + 51
3 com.apple.cloudkit.CloudKitDaemon 0x00007fffa307e591 -[CKDPackageDirectoryPurger purgeRootDirectory:] + 684
4 com.apple.cloudkit.CloudKitDaemon 0x00007fffa307e21e __37-[CKDPackageDirectoryPurger purgeAll]_block_invoke + 427
5 libdispatch.dylib 0x00007fffadcdf524 _dispatch_call_block_and_release + 12
6 libdispatch.dylib 0x00007fffadcd68fc _dispatch_client_callout + 8
7 libdispatch.dylib 0x00007fffadcec9a0 _dispatch_queue_serial_drain + 896
8 libdispatch.dylib 0x00007fffadcdf306 _dispatch_queue_invoke + 1046
9 libdispatch.dylib 0x00007fffadcd86b5 _dispatch_root_queue_drain + 476
10 libdispatch.dylib 0x00007fffadcd848c _dispatch_worker_thread3 + 99
11 libsystem_pthread.dylib 0x00007fffadf25616 _pthread_wqthread + 1299
12 libsystem_pthread.dylib 0x00007fffadf250f1 start_wqthread + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fffade3b44e __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fffadf25502 _pthread_wqthread + 1023
2 libsystem_pthread.dylib 0x00007fffadf250f1 start_wqthread + 13

Thread 4:
0 libsystem_kernel.dylib 0x00007fffade3b44e __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fffadf25695 _pthread_wqthread + 1426
2 libsystem_pthread.dylib 0x00007fffadf250f1 start_wqthread + 13

Thread 5:
0 libsystem_pthread.dylib 0x00007fffadf250e4 start_wqthread + 0
1 ??? 0x6f72726500270200 0 + 8030606863674835456

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff5f73f168 rdx: 0x0000000000000000
rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff5f73f190 rsp: 0x00007fff5f73f168
r8: 0x00007fffaddc9650 r9: 0x00007fffadd8ba50 r10: 0x0000000008000000 r11: 0x0000000000000206
r12: 0x00007fff5f73f2f0 r13: 0x0000000000000030 r14: 0x00007fffb6c1e3c0 r15: 0x0000000000000008
rip: 0x00007fffade3ad42 rfl: 0x0000000000000206 cr2: 0x00007fffad9ebfb0

Logical CPU: 0
Error Code: 0x02000148
Trap Number: 133

VM Region Summary:
ReadOnly portion of Libraries: Total=268.0M resident=0K(0%) swapped_out_or_unallocated=268.0M(100%)
Writable regions: Total=56.5M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=56.5M(100%)

                            VIRTUAL   REGION 

REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Activity Tracing 256K 2
Dispatch continuations 8192K 2
Kernel Alloc Once 8K 2
MALLOC 37.5M 22
MALLOC guard page 32K 7
Stack 10.5M 7
__DATA 25.1M 261
__IMAGE 528K 2
__LINKEDIT 114.1M 4
__TEXT 153.9M 266
__UNICODE 556K 2
mapped file 24.7M 2
shared memory 336K 7
=========== ======= =======
TOTAL 431.6M 581

The non-test servers load fine, and in fact load much faster than the current test build.

That error seems to say your disk is full:-

, msg:“database or disk is full”, size: 81920, path:/Users/USER/Library/Caches/*/CloudKitMetadata, fs:0/91473068032’

@Haelos, @Omnifob, @brook-monroe and anyone else I’ve forgotten, thanks for the information about the creatures. This issue has been touched on in previous topics. We are still looking to re-balance the creatures and their aggressiveness. Tagging @olliepurkiss so that he can see some of the replies here.

Thanks for the report, we’ve added the the information to our bug database.

You need to unlock the necessary skill to see that information over their heads.

Can you describe in more detail about how frequently they are appearing? What’s the maximum number of creatures have you seen in the game and what’s the average time you had to wait before you encountered a creature again?

Did you have any portals near you at the time?

Is that from the Recipes tab? We haven’t been able to reproduce this, other than when ingredients have run out, which sounds like it doesn’t apply in your case. How many times have you seen this occur?

Is this also the case on the current live version?

1 Like

Will answer some questions after biz hours in Seattle. On airplane to there now now. Can’t play until I get back at end of the week.

Yes, and it happens all the time for me, like every 3-4 click or so. It might be because of what else is in the crafting table?

Gonna shorten the three basic rocks/stones to MM, IG and SD.
1 slot: Plotter Smartstack { Beacon Plotter, Beacon Plot Remove }
2 slot: 36 MM Stone
3 slot: Rock Smartstack { 67 MM, 99 IG, 10 IG, 59 SD, 99 SD, 68 MM, 99 SD, 99 SD, 90 SD }
4 slot: 15 Gravel
5 slot: 99 Fibrous Leaf
6 slot: 33 Sand
7 slot: Soil Smartstack { 71 Silty, 20 Clay, 8 Peaty }
8 slot: Rock Smartstack { 99 SD, 99 SD }

Are you able to provide a video of what you’re experiencing? If not, would you be able to provide some steps to reproduce using specific ingredients so that we can give it another go?

Seems it was simpler to reproduce than I thought. Apparently this will happen if the submenu is expanded in the lower part of the screen.

I made a new crafting table and put 60 metamorphic stone in it. It will display 5 recipes. Slab, step, wall, crucible and fire pit. Make sure you are scrolled all the way up to the top, then select Stone Fire Pit and click Craft a couple of times in rapid succession (if not done fast enough, it doesn’t seem to trigger).

When I log in to my largest holding, there will be at most four outside. Once they’re dead (or move off) then they’re not replaced. There aren’t any portals around that I’m aware of, since there’s almost no activity in the region I inhabit. If I head up into the desert areas north of my holding the situation changes to be more like what the release notes describe until I stop again. I think I’ve seen the situation repeated when I go to my mining area. There will be four or five and once they’re dead no more show up. In both cases I’ve portaled in (once from Sanctum, and once from my major holding, but technically those disappear once I’ve transited).

I haven’t checked the live version (there’s no good mining nearby, and I’m in Seattle for a week with no Boundless-enabled computer).

If you kill all the creatures at your current location, then no more will appear for a while if you stay where you are. But if you move further away from that location, then creatures should spawn eventually as you’re travelling.

Thanks for the extra information about how to reproduce this, we’ve got it to occur on our end, so we’ve logged a bug.

Ghack… thanks. interesting that only the test server is failing. I’ll try to clear up some space and retry.

Broke a hammer and saw that I’d completed the feat “Bunt as a Hammer.” Is that supposed to be “Blunt as a Hammer,” or is “Bunt as…” some Britonism I’ve never encountered before?

I didn’t see these two issues being acknowledged, so I’m bringing it up again. I’m sorry if it already was being considered.

Not a dev but sharing my initial thoughts on the bar!

I believe the segments are there to indicate the tier of the mobs and not specifically its exact health. For example, roadrunners have 500 hp/bar, wildstocks have 1000 hp/bar. All or most mobs on starter planets should only have 1 bar and as you go to higher tiered planets, the number of bar increases to show that they are somewhat “higher tiered” or “stronger” version.

With that said, this somewhat contradicts the fact that wildstocks on starter planets have 4 (or 3 can’t remember) bars. So I’m considering that the wildstocks’ stats on starter planets was somehow misconfigured?

This is working as intended, although maybe it’s not clear enough given the confusion.

The number of segments is based on the amount of health as relative to the amount of health a level 1 creature has of that type.

So a level 1 Wildstock has 2000 health, and a level 3 Wildstock has 6000 health, hence you see three segments because it has three times as much as the lowest level Wildstock.
On the other hand a level 1 Roadrunner has 400 health, and a level 3 Roadrunner has 1600 health, hence you see four segments because it has four times as much as the lowest level Roadrunner.

This might be a little clearer when the creatures show their levels in the their names (that will be coming soon).

I hope that clears it up a little. As always, please feed-back – this is far from set in stone.


Bunt is an actual word, although it’s not correct in the context of this feat. This should be sorted in the next version.

Ok. So I’ve cleaned up as best I can (consolidated Drive partitions, reinstalled OS, and restored my basic data). I am still crashing when trying to start boundless. Could my local data be corrupt? What should I delete to start fresh?

I’ve reviewed the tblz_log.txt, and the error seems to be with getting world data. I can post the log, anywhere in particular you’d like me to post it?

[2017-08-05 23:47:43] INFO : GET https://gs-testing.playboundless.com:8902/planetdata/use_c1_home/settlements
[2017-08-05 23:47:43] ERROR : failed to get world data (runtimeplayerstartworld)
end snippet

Bunt is an actual word,

Yes, it’s a type of attenuated hit in American baseball, there’s probably some sort of cricket version as well, and if I recall correctly, there’s a phrase that Eric Idle used in a Monty Python sketch that went “…silly bunt.” :stuck_out_tongue_winking_eye:

1 Like