Kami Client

[ItsFunToLose]

any community knowledge on common causes of BSOD while using custom clients that don't happen while using the default?

[terechgracz]

If youre getting bsod then contact repairshop as it's probably hardware or system issue

[derkami]

any community knowledge on common causes of BSOD while using custom clients that don't happen while using the default?

https://www.nirsoft.net/utils/blue_screen_view.html

You should investigate the root cause of the bluescreen.
Never had any issues using any client. Including mine.

Playing standalone? Through steam? What's your installed Java? Using included JRE? What does the Bluescreen even say?

[mvgulik]

I got different map data in both Ender and Kami. (Linux - Mint)
When I tried exporting the map data in Kami its not creating the export file. Tried different folders in case of some general java active protection, but without any luck.

Just in case.
1) When/if map export will work. Can I used those map export files safely in both directions ? (Ie: Kami => Ender & Ender => Kami)
2) if(1)=yes ... Will I now have two two duplicate sets of cached map data? ... ie: both taking up a large chunk of space.


(Also tried the export to mapper (v1) (outdated version ?), but that threw some error in the client system chat)

[derkami]

I got different map data in both Ender and Kami. (Linux - Mint)
When I tried exporting the map data in Kami its not creating the export file. Tried different folders in case of some general java active protection, but without any luck.

Just in case.
1) When/if map export will work. Can I used those map export files safely in both directions ? (Ie: Kami => Ender & Ender => Kami)
2) if(1)=yes ... Will I now have two two duplicate sets of cached map data? ... ie: both taking up a large chunk of space.


(Also tried the export to mapper (v1) (outdated version ?), but that threw some error in the client system chat)

Map export / import is a vanilla feature. Neither I nor Ender as far as I know, changed anything about that.
I actually noticed that there are problems with java on linux for some reason. I only could create a file on my home folder.

The reason why you have 2 different map data is because you get random ids for your segments.
There's a chance that an export / import will stich matching segments together. The client also stiches them once you explore different tiles from each segment. Much like my mapper is doing it.

It's actually funny because my client is still based on ender and pretty much, matches ender's except for my own additions. So all the local map cache drama is, as far as I know, vanilla design.
Again, export / import should hopefully match grid_ids and start merging. Try your homefolder without any subdirectories. Don't know if it has do to with any of the switches I have in my start files...

As for the Export to Mapper, V1 is actually the current correct version for this feature, but because of Issues, I haven't had the chance to activate this on the mappers.
Working on that one though.

[mvgulik]

O dear ... I got even more problems to contend with.
After getting a lot of new maps with Kami, Ender is now not showing a lot of its previous maps (black terrains and maps).
Effects all accounts, also tends to lockup on "building map (queued)", ... if its even starting up in the first place.
... In essence I can't really use Ender client at this moment See: Update A.

As far as I know Ender is not using the pure Vanilla export/import. As in: Vanilla export/import generally gave problems, while Ender's export/import was generally rock solid. (although things might have change, as I have not used export/import for some time now)

"Home folder" ???
"/home" is a system locked folder. (but at least that triggers an error)
No success with: "/home/<user>", ".../<user>/desktop", ".../KamiClient", ".../KamiClient/release", ".../KamiClient/jre21linux"
Hmm ... Enables "store minimap files" ... ".../KamiClient/release/map" ... Nope. no file and no error. See: Update B.

.... To be continued. (more experimenting to do on my side)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Updates:
A) Client apparent lockup was related to the client(ALL/Vanilla) merging map segments process. The problems here is that that process is:
1) Generally slow (ie: potential long waiting time depending in map segment sizes),
2) Not done as a background task (ie: The whole client(ALL/Vanilla) is waiting for it to finish. While ignoring any user input),
3) There is no merging progress feedback to the user.
(... classic combination!)

B) It turned out not to be Kami client related. Not even Ender client related. Yea you got. It was default/Vanilla client related. (+Kami did do some beta update that fixed/(worked around) it. At least on my end. ... Beta!)

[faslger]

sorry if this has been answered before... is there a way to get rid of the snow tiles on my map? or are they stuck that way?

[Kahned]

Hey there, I have found you site "https://public.hearthworld.com/cookbook/" and was wondering if it is possible to update those recipes using cookbook integration from different client? Or any other way to use it and work on my own (or semi public) cookbook?
Thank you for your wondeful work!

[derkami]

sorry if this has been answered before... is there a way to get rid of the snow tiles on my map? or are they stuck that way?

You need to revisit the tiles. It's the game mechanic, nothing I can do about.

Hey there, I have found you site "https://public.hearthworld.com/cookbook/" and was wondering if it is possible to update those recipes using cookbook integration from different client? Or any other way to use it and work on my own (or semi public) cookbook?
Thank you for your wondeful work!

Since my Stuff is not open sourced, nobody is going to integrate with my changes. Which is a fair point and will be addressed this year.
Right now you'd need to integrate that yourself and use the client of your choosing.
Since my client is open source, you can just joink the integration source files.

[mvgulik]

KamiClientUpdater, Linux.

Two things that don't seem right.

The major thing is that when toggling the "Use custom start files" On (or Off) it rewrite the related custom *.sh start files.
Those files should of course only be created if they don't exist. But should never be touched if they already exist.
Figure it might be a detection problem of those files, triggering KamiClientUpdater to always create(overwrite) them.
(Was kinda wondering what happened to my last custom setup. ... AHA. Oops, no backup.)

A second minor thing. When creating a Linux start/quick-link to the KamiClientUpdater it, instead of using the "updater.json" located in the KamiClientUpdater folder, it create a new "updater.json" in the location of the quick-link. So using a KamiClientUpdater-link on, for example, the desktop also creates a "updater.json" there.
(Locally fixed by using a link to a little additional <KamiClientUpdater>.sh script file that changes the active working directory before calling/starting the KamiClientUpdater itself.)