The Nineteenth Byte - 2014-04-11 (page 2 of 2)

« first day (1168 days earlier) ← previous day next day → last day (3678 days later) »

undergroundmonorail

10:05 PM

I like the idea of honorable mentions for wolves that are amusing in a cheaty way.

I want to suggest "dishonorable mentions" as a joke but you know someone will take it seriously...

For the record, I have an even cheatier solution now

that never dies

I made a faster Game.java, uses threads and hopefully doesn't break anything: ThreadedGame.java

Currently is only a dissapointing 20% faster, but still, saves time on those long tests

I don't think making the game faster helps much

no, that's a lie

When doing a 1000 run avg with Deep in there it does

lol yeah

he takes a bit of time :p

10:08 PM

exacerbated by Hybrid calculating him again

haha

I'm not sure if I should post my newfound cheaty solution that never dies, I've already posted 2 answers

Gist it to us here first? I wanna see

it's pretty simple, really

reflection to make the non suicide attacks actually commit suicide

make suicide not commit suicide

and then always return Attack.SUICIDE

That was already tried, didn't work

it's working for me..

maybe that's because I'm running a slightly altered game? I'll have to try it with vanilla

10:12 PM

Didn't work for this guy: codegolf.stackexchange.com/a/25542/20169

I'm pretty psyched that I have a "Vanilla" of something. Just sayin.

And I'm (probably everyone really) already modding it, wanna try ThreadedGame?

I should try the vanilla game, then

all my files are altered lol

because I created them back from the sandbox era, when you didn't post source

and I had to disassemble and manually clean it up

yup, no deaths in vanilla either

What's different in yours than in Mirror?

I'm not sure, honestly...

let me look more closely

oh of course

he's changing the references themselves, so they all point to the Attack.SUICIDE object

I'm leaving the references intact, but changing the ordinal fields inside each attack

10:22 PM

Ah, interesting that that works and his doesn't

So then EmoWolf is actually amazing in your tests, right?

oh wait

this doesn't work either

Well.

well, it does work, just not the enum changing thing exactly

it does do the enum changing, but I accidentally left in the TotallyAStone code

so it also has the letter 'S'

and for some reason, that gives it 100% survivability

but... for some reason, this enum thing seems to make stones invincible?!

Does everything else die en masse?

not really

I can't tell, simulation is way too slow on vanilla

10:27 PM

Remove the JFrame code and the sleep()

print the stats.toString on completion

I think it's the fact that it's still not using stringbuilder

also don't need to stats.update until sim is done

I don't really understand these results

deepwolf gets slaughtered, but other ones like omegawolf do relatively okay

Put the code in a Gist and I'll try it

(I won't be a tard and submit it or anything)

gist.github.com/Runer112/ffac1b8582c835ee0127

I didn't clean it up at all, so there's lots of unnecessary stuff in ther still

so basically it's a stone, but with that reflection stuff

both it and stones never die lol

honestly I'm not even sure how it works any more

10:34 PM

Yeah, weird: ChemicalWarfareWolf 99.9
Stone 99.9
HerjanWolf 75.0
HybridWolf 73.7
OmegaWolf 70.3
ProAlpha 66.7
HonorWolf 64.5
WaryWolf 63.4
SpyWolf 60.3
AlphaWolf 55.3
LazyWolf 53.4
ShadowWolf 52.0
DeepWolf 48.8
BlindWolf 44.3

99.9? I got 100

Rounding?

only one test, I guess

although I did run like... one test, five separate times

That there is 10 tests avg

looks like you ran 10 tests and one died once

I've tried my best to reflect into the game board itself, but I don't think it's possible without a reference to the game itself :p

so for now, this is my best reflection solution I guess

I should probably go home, I'm just hanging around at work after hours

10:38 PM

I changed these: System.out.println(attack + " -> " + newOrdinal + "=PAPER"); etc to System.out.println(attack + " -> " + newOrdinal + " = " + ATTACKS[a]);, prints this: ROCK -> 3= ROCK
PAPER -> 3= PAPER
SCISSORS -> 3= SCISSORS
SUICIDE -> 1 = SUICIDE

why did you change them

the idea was to test the switching

it has some effect on switches somehow...

enum switches are a little funny and still a bit beyond my understanding

I'm heading home from work now, so won't be here to communicate any more

I believe the switches switch on the value of an enum field (the ordinal), not the reference itself.

Cya

yeah, which is why the ordinal thing seems to work I guess

undergroundmonorail

11:30 PM

Google code jam started

And I'm reminded why I'm not the programmer on my programming team ;_;

« first day (1168 days earlier) ← previous day next day → last day (3678 days later) »

Transcript for

Apr '1411

The Nineteenth Byte

The Nineteenth Byte: General discussion for codegolf.stackexc...

join this room
about this room

00:00

06:00

12:00

18:00

all times are UTC

site design / logo © 2024 Stack Exchange Inc; legal

mobile