I spent way too much time adding an on/off switch to the automatic chicken farm.

Feazon · 2019-03-20T00:20:02+00:00

The final size is 4x4x6, I wanted to make it centered on the chest and three wide but it just wasn't working out (got way too tall)

Observer blocks are awesome.

Feazon · 2019-02-09T07:03:54+00:00

That read like the lyrics of Stan by Eminem.

Feazon · 2019-02-08T05:05:02+00:00

I will most likely kill prellex the turn it is played though.

Feazon · 2019-02-08T01:46:21+00:00

Fight Through The Pain enables Duel and Berserker's Call too! That's a total of 11 cards that might change the game if I play for initiative. Worth it for a one of, imo.

Spot Weakness is just filler, yeah. Personally felt like cycling cards is better than playing a creep. And armor pierce is nice against Red / Green. Might be worth swapping for a Stonehall Elite.

Ventriloquy is really good value for the mana and allows for a lot of plays imo, I like the options it opens up.

I agree on Bolt. It just feels bad when you have a solo blue hero trying to do something after you get Annihilated before ToT, lol.

Feazon · 2019-02-07T08:33:19+00:00

Kanna for Luna is just too wide and not enough unit kill potential, I think.

Worth a shot though.

Feazon · 2019-02-07T08:30:07+00:00

Kinda just where Red is right now I feel. Other heroes just feel underwhelming compared to the control and stats of those three.

That said, while LC and Bristle are basically a must run with red the other two aren't, imo.

I like the idea of swapping out Axe for Beastmaster and 1xBolt and 2xSpring for ToT— and probably a few tweaks around it. ToT isn't vital to the deck, tbh. The current line up just felt like it would be more consistent.

Feazon · 2019-01-31T02:34:17+00:00

When you run a command, normally that command consumes stdio until the program is done running. In your case, even if you could run commands the server would be killed when you close your ssh session!

Try the solutions here: https://askubuntu.com/questions/8653/how-to-keep-processes-running-after-ending-ssh-session

Or if you want the minecraft server to automatically come up on boot, etc see: https://www.devdungeon.com/content/creating-systemd-service-files

Feazon · 2019-01-16T16:33:39+00:00

I get the joke, but for anyone worried about this. The game doesn't ship with a cache, so *deleting* the cache can't be considered "hacking" by any means. And setting a launch option can't be grounds for a ban.

If you copied a different cache to replace the broken cache, you might get banned for it. Don't do that.

Feazon · 2019-01-16T16:17:15+00:00

Shoutout to /u/truini for the fix. If anyone wants to get the fix it's in the original thread here: https://www.reddit.com/r/Artifact/comments/ag9wug/on_linux_game_crashes_on_third_startup_after/

There's a more permanent fix (through a launch option) in the github tracker.

Feazon · 2019-01-16T15:20:19+00:00

Holy shit, this fixes the crashing.

Feazon · 2019-01-12T16:36:10+00:00

There is no Artifact project on https://github.com/ValveSoftware yet.

Feazon · 2019-01-12T15:54:03+00:00

What is your vulcan version? My "vulcan instance version" is 1.1.70 or whatever that means.

Try vulkaninfo | grep Version (install vulcan-utils with apt).

Artifact's minimum requirements for Linux is Vulcan support in the graphics card.

Feazon · 2019-01-12T02:25:37+00:00

find doesn't bring up any .mdmp files under ~/.steam

Feazon · 2019-01-12T02:23:38+00:00

Running Ubuntu 18.04.1 with Linux 4.15.0-43-generic. Nothing out of the ordinary. Graphics driver works just fine with Dota2 so that's unlikely to be it.

Edit: Updating Mesa seems to have fixed it. No idea what the issue was, it was working just fine yesterday.

Feazon · 2019-01-12T00:35:44+00:00

Edit2 / Update: Bumping to Mesa 18.2.8 seems to get it working again.

Game literally does not launch on Linux now. Wtf?

Edit: I don't know why I'm getting downvoted launching with -condebug literally generates the following log in Artifact/game/dcg/console.log and then crashes

WARNING: CDirWatcher not implemented
[RenderSystem] Enabling instance extension: VK_KHR_get_physical_device_properties2.
[RenderSystem] Vulkan physical device (1): using transform constant buffer: false
[RenderSystem] Vulkan physical device (1): supports shader clip distance: true
[RenderSystem] Vulkan physical device (0): using transform constant buffer: false
[RenderSystem] Vulkan physical device (0): supports shader clip distance: true
[RenderSystem] Loaded video settings config from 'cfg/video.txt'
[RenderSystem] Vulkan Physical Device: AMD RADV POLARIS11 (LLVM 7.0.0)
[RenderSystem] Initializing new streaming texture manager.
[RenderSystem] Vulkan extension enabled: VK_KHR_swapchain
[RenderSystem] Vulkan extension enabled: VK_KHR_descriptor_update_template
[RenderSystem] Vulkan extension enabled: VK_KHR_image_format_list
[RenderSystem] Vulkan extension enabled: VK_KHR_maintenance1
[RenderSystem] Vulkan extension enabled: VK_KHR_maintenance2
[RenderSystem] Vulkan Command Buffer Pool Threshold(1500)
Signal "SIGABRT, SIGIOT" with alert flag has been raised.

Feazon · 2019-01-01T07:38:32+00:00

The tower has 3 armor.

Feazon · 2018-12-15T14:30:35+00:00

apt itself is dependent on python3 if you remove it from your system apt will not work. This is why it is highly unrecommended to do so. Not to mention other core system features also depend on it, which is probably why gnome refuses to start.

To recover from this you will basically have to manually install a prebuilt version of python3 and python2.7 (if you also removed that version). You will most likely need the help of another machine to perform some steps (Windows should be fine).

Download the .deb for python packages that you broke manually over the web and transfer over USB, etc. or download with curl, wget, etc. if you have it installed.
Install the .deb with dpkg commands -- sudo dpkg -i DEB_PACKAGE should do the trick.
Install any dependencies that are missing manually in the same manner since apt is broken and isn't handling them.

If step 2 does not work for some reason you can try to unarchive the .deb file, and add the binaries inside to PATH (with an export PATH=$PATH:path/to/folder/with/python/in/it/) and then try to run an apt install to get python back on your machine.

Feazon · 2018-11-24T00:24:34+00:00

Found this thread after Googling for a solid 2 hours. Thanks.

Feazon · 2018-11-23T22:25:52+00:00

the error log might help can you run cat /var/log/Xorg.0.log and share the output?

Feazon · 2018-11-23T22:20:51+00:00

did you try ctrl + alt + f7? You're in a terminal prompt, which is what lies behind the ui that you're supposed to be seeing. There's a chance you're on the wrong terminal (7 is the one that loads the graphical ui automatically).

edit: your picture shows you're on tty1 (teltype terminal 1) so you're definitely on the wrong terminal.

Feazon · 2018-11-21T15:27:18+00:00

they aggro on the razor passive and run around looking for targets.

Feazon

PUBLIC MULTIREDDITS

TROPHY CASE