Search results

You are *probably* trying to run it from some protected location (like "\Program Files" or "\Windows" - I don't know the full list). Try making a new folder somewhere aways from system locations, copying the jar there, and running it from there?

Are they +0 even if you use all of them combined? Also try seeing what happens if you ad +current

Sometimes that's the kind of thing you need to do if you don't want to regress to some extremely ineffective general solution.

My "svn update" ends like this Updating all SVN projects... Installing dependencies Starting Checkout... Validating repo... svn: E160013: '/Ezandora/Detective-Solver/branches/Release' path not found: 404 Not Found (https://github.com) Something went wrong while fetching svn directory info Done...

Most scripts I can just go something like, for example: svn delete Ezandora-Bastille git checkout Ezandora/Bastille Release but I found one script where svn allowed checking out a subfolder, which is something can't figure out with git: original: svn checkout...

> ash $location[guard] Changing "guard" to "The Royal Guard Chamber" would get rid of this message. (char 11 to char 16) I think that's what you want, in mafia namespace?

a) does <![CDATA[MA<MD,CA<CD,PA>PD]]> work? 2) is that human readable enough? iii) is that something that can be usefully used (so that you would only use it to encapsulate values that need it, and not every single line, especially not lines where html *should* be mirrored as-is)?

File asssociations (what runs when you doubleclick a file) are a completely separate thing. There might be other launch ways with their own configuration of what gets run.

As far as I can tell, "shadow jar" is one of many generic terms for "jar that also includes all dependencies .. but kolmafia already includes all of its dependencies in its own sources, and so they are compiled into the normal jar instead of being distributed as separate precompiled jar files...

Now I am getting: FAILURE: Build failed with an exception. * Where: Build file '/home/xkiv/src2/kolmafia-git/build.gradle' line: 198 * What went wrong: Could not determine the dependencies of task ':jar'. > Resolving dependency configuration 'implementation' is not allowed as it is defined as...

AFAIK, that has been reported as a bug in the docs.

Warnings for building with 21: 1) current-er gradle requires that tasks always have defined order of execution. Older gradle already gave warning about this, 8.5 upgrades them to errors. I added the following: startScripts.mustRunAfter shadowJar distTar.mustRunAfter shadowJar...

Warnings for building with 21: 1) current-er gradle requires that tasks always have defined order of execution. Older gradle already gave warning about this, 8.5 upgrades them to errors. I added the following: startScripts.mustRunAfter shadowJar distTar.mustRunAfter shadowJar...

go to the file, edit it, go to line 115, find where it says Rene C. Corman and instead use Rene C. Corman (Zombie Slayer)

IIRC in the relay browser, near the right edge of top frame. But I never actually used that. Low confidence.

My thrifshop coupon has survived in my DC for quite some time already. Buying a 28 meat cool whip from The Armory and Leggery didn't use it up. Can you verify that the coupon is actully in your DC after you run the script? Then grep -i "thriftshop" $your_session_files maybe something is pulling...

I think only if you have (regular) backups that include your kolmafia data folder. Or at least a backup from before it was deleted. They are in the ccs/ subfolder, and each macro is its own file ... so a deleted macro means deleted file.

the json I am getting has collections (with an s at the end) where the code expects collection (without the s) (IOW it's not a mafia change, it's a change on the remote side)

Perhaps unnecessary - but a gentle reminder that javascript as designed does not have normal non-float [1] numbers. (there's BigInt but that's not very interoperable with other numbers). What we are seeing here might be that 1) literal integers are somehow represented by an internal value that...

I think there are two other things that can be done to alleviate this: 1) after such popup is created, do not let it accept regular input for some (configurable?) amount of time. Like a second or two. Long enough that we will notice we are suddenly typing/clicking into something that didn't...