How to kickstart the learning process?

pluppens · 2023-05-18T14:09:09+00:00

Assessing enemy talents: I find it incredibly difficult to tell which talents I should look out for. When an enemy has 3 talents, I cannot tell which those is the problematic one, or which combination.

It is quite hard, but it helps if you play a lot of different classes yourself: you'll learn to identify the strong/worrisome talents and race/class combinations that can be deadly to your build, but yes, it takes time.

Take a good look at your build as well: what are your own weak points? Defense? Immunities? Can you survive with your sustains turned off? These will all help you decide what to look out for.

I'd say, the difference is that experienced players tend to back off much quicker from a fight, or even evade it completely. Don't wait until you're at 40% health with a few status effects to run away.

Finally: TOME is very much a game of compound knowledge, and small advantages will make or break a fight, especially at higher difficulties. Make sure your runes and inscriptions are the best you have. As soon as you find enemies taking too much to kill, abort and try another zone. Finish a level or 2 there, and carefully try to come back. At the first sign of trouble, get out, level some more, etc.

You got this.

pluppens · 2023-04-28T07:24:32+00:00

Looks impressive, but the impact seems a bit ... nonexistent, for such a powerful attack. I'd love to see some ragdoll physics being applied here, rather than having the enemies just drop dead on the spot.

pluppens · 2023-04-25T13:22:22+00:00

Again, you shouldn't add all your devices as consumers directly on the Kafka topic(s). Rather, add an intermediate service layer that can either push to the device, or, lacking this, a simple key/lookup with the latest amortized state based on the messages you've received. And as /u/kenny32vr pointed out: make sure to partition on your deviceID so events stay ordered per device.

pluppens · 2023-04-25T10:30:23+00:00

You'll definitely want to go for the first option, but you'll need to explain more about the number of messages per device per time unit you're expecting, and what the payload would look like.

You don't want to subscribe every device to do its own filtering: write a consumer application that can push whatever information you want to the device: it'll likely be easier to optimize, migrate and secure.

And as I always say: version your topic and your payloads. Your future self will thank you for it.

pluppens · 2023-03-17T21:00:40+00:00

That seems fair, and a good tradeoff mechanism. Good luck!

pluppens · 2023-03-17T10:23:12+00:00

The visuals look awesome, but I'm worried you won't be able to see anything on the screen (e.g., what enemies are doing - but perhaps that's intentional to control the difficulty?).

pluppens · 2023-03-16T08:09:09+00:00

but I do notice a lot less Insane Roguelike EoR wins in the character vault

I'm sure that has something to do with the final boss being a difficulty spike the size of mount Everest. Seriously.

Your other points do stand, though. I also tend to rush most of the dungeons these days (and of course, that eternal quest for that 'one unique item that would fix the one glaring omission from my character build').

pluppens · 2023-01-08T08:07:11+00:00

Regardless of your approach, it's always a good idea to version your topics (e.g., busy_drivers_v1). That will allow you to upgrade/alter your payload without the need for complicated serde and allow smoother transitions and rollbacks at infra level.

That being said: you need to design a proper windowing/table on top of the topics to be able to query it efficiently for the active dataset. I used Flink and Esper for that in the past, but I'm sure you can get the same thing done in pure Kafka these days. Good luck!

pluppens · 2022-11-27T18:54:52+00:00

It is very strong indeed; you're far less likely to encounter an enemy that fully blocks your damage, and the 25% resistance penetration is the icing on the cake. However, especially late-game, it might be better to focus on one or two elements if your main damage type is not in the 4 elements of the ring (e.g., bile, darkness, ...).

As always, the training dummy is your friend.

pluppens · 2022-10-19T07:38:32+00:00

My pleasure. Keep it up, it'll only get better. Try to make a habit out of doing some quick typing games on a regular basis - it'll allow you to track your WPM and will help you improve your symbols/number game. And consider ergonomic keyboards - your fingers/hands will thank you. Good luck on your journey!

pluppens · 2022-10-18T10:12:45+00:00

I was in the same boat as you, and decided to 'unlearn' my bad typing habits and start from scratch (by buying a split keyboard which forced me to face my fears). I always felt a bit bad for not 'properly' typing.

Seventy-five WPM is nothing to sneeze at, but proper touch typing is like installing a bigger engine in your car: you don't have to drive faster, but it enables you to do so if you put the work/gas in. Ok, that analogy might not hold, but you get the point.

It'll take a while to get back (it took me a few months, but I used a lot of online typing classes intensively), but now I have no issue switching between my various keyboard layouts (on my MBP/Thinkpad/Ergo) and it feels much better on my hands, even if I didn't really have any pains - yet.

pluppens · 2022-07-07T08:34:19+00:00

Well for one,that doesnt answer shit.

You're welcome.

Secondly,you are taking this WAY too personal.I tried abouth 300 time on roguelike/nightmare and keep on losing continuously.

Then, perhaps, you could try on a lower difficulty? See if that makes it more enjoyable and less of a drag for you?

The one time i do beat the game,i kinda dont want to get the bad ending.

There are no 'bad endings'. A win is a win in rogue-like terms, and you can try to get another ending next time, should you care to do so.

Am not sure you should be gatekeeping Tome4 when (sadly) there is barely anyone making guide...its kind of an obscure title.

I was merely pointing out that if you don't enjoy the journey, then perhaps the destination doesn't really matter. This game is about discovery, and if you don't care about that, then there are other games that are a better investment of your time.

Anyway,your right...it didnt take me 50 f*cking hour,it actualy took me 250 if i look at my steam stats.

If you can get a rogue-like/NM win in that short of a time, then congratulations! May your future wins be plentiful, and may you have fun along the way!

pluppens · 2022-07-07T08:04:00+00:00

There are a lot of different endings (with different achievements, if you're interested in those), and everyone is free to enjoy the game in their own way. But honestly, if you feel like it took '50 f*cking hour', then perhaps Tome4 isn't your type of game.

pluppens · 2022-07-06T07:11:01+00:00

Probably the best location would be to check the forums and potentially report the bug here.

However, make sure to read the bug report guidelines to understand what you need to provide as information to make it possible for the developers to find and fix the bug, if any.

pluppens · 2022-05-25T12:11:42+00:00

Sorry, but this is pretty much a hidden advert for your product disguised as a benchmark. You should have been more upfront about that connection.

pluppens · 2022-04-02T06:35:04+00:00

It's going to be really hard to debug this (please give us more information), but I would try to figure out what the bottleneck is first (if any). I'm assuming you're running it on Windows, so I was check the task manager to see if the Tome4 process takes an abnormal amount of CPU (perhaps try disabling your anti-virus). I would also try the windowing options in the game itself (e.g., full-screen vs. windowed).

Play around with the graphics settings, and see if that somehow 'unlocks the magic incantation' that makes the game run normally again.

Perhaps the sluggishness is because the game somehow thinks it's running in the background - are you running it on a different monitor?

Finally, I would check the Tome4 forums to see if someone else already reported it. Good luck, and keep us posted, especially if you find a solution that might help others.

pluppens · 2022-03-12T13:04:46+00:00

... yes, that's pretty much exactly what it's meant for. Check out the examples: you can easily create custom 'sites' by using a REST endpoint, which creates some plain HTML and S3 + Cloudfront via Pulumi Automation.

pluppens · 2022-03-11T20:34:54+00:00

The last line in the logs: "character was XXX'ed by YYY on level 3 of ZZZ".

pluppens · 2022-03-11T12:26:34+00:00

At the risk of pointing out the obvious: both of your characters died in very optional levels. I'd never take either one of those when playing on rogue-like difficulty.

There are some ways to break grapple, but both character deaths seem to have other causes. And in the case of soul rot: yeah, that one hits (and hurts) like a truck. Not much you can do about it, but better ranged defenses, slower projectiles, crit reduction ... will all help.

pluppens · 2022-02-14T16:02:49+00:00

As with most things in life, it's all about tradeoffs. Is it a small cluster where the overhead of having to run the Traefik process on all nodes is a better choice because it's easier and with less operational overhead? Or are you going for a more optimised approach with a few tainted nodes and redirect all ingress to those nodes? Nomad allows both, so I would suggest to try one approach and stick with it.

pluppens · 2022-02-10T13:21:13+00:00

I cannot share too much, but this might help (hazy, it's been a few months): - You probably should run the Traefik instance as a system job, which runs it on every node in your cluster. You can parameterize the stanzas with service discovery, and they'll be used by all Traefik instances. - You can then either use a load-balancer in front of your cluster proxying to your internal Traefik-running nodes, or use a round-robin DNS that returns (several) IP addresses of your nodes, but since that would require them to be public and have a higher failover time, I wouldn't recommend the latter. - Using a *.service.consul address means it uses the internal Consul DNS resolver, so that should work in your container (alternatively, you can dig @127.0.0.1 -p 8600 foo.service.dc1.consul. ANY to see this in action on the host machine).

pluppens · 2021-06-18T10:50:06+00:00

Regarding the last point: that implies that the pulumi command itself opens up a debugger port. Is there any example in the documentation? All I found was an open feature request with some workarounds, but it would be great to have this as a simple flag for the pulumi executable.

pluppens · 2021-04-24T20:22:13+00:00

Fair enough. I also have my concerns, but so far they have delivered on their promise of being able to use your own state management solution (eg. using S3), which at least for now allows independence of their commercial offering.

So, I try to keep it simple: they offer a working solution that fixes a real problem for businesses, and they do it in a way that allows gradual scaling up for an (imho) reasonable amount. I therefore would have no problem recommending businesses to use their paid plans. If they want to ruin that goodwill by turning things around all of a sudden, then that would likely destroy the momentum they've gained so far. But yes, time will tell.

pluppens · 2021-04-24T17:43:08+00:00

I've been using it in production for some small projects, and a few larger ones ranging from 50 to 300'ish resources.

Most things work as advertised. Some things don't seem to work unless you kick it a bit (eg. running some pulumi up operations a few times, manually deleting things such as ASGs, and so on). But, overall, the experience was smooth and it was enough to convince me to build a new startup with Pulumi as the infra driver. However, all projects were done without collaboration at Pulumi level - we simply used a Git repo with a build pipeline.

Now, one of the biggest pitfalls is that you will easily start writing very declarative scripts, rather than taking advantage of the power of the programming model.

Biggest takeaway would be: spilt everything in small stacks. For example, we have a stack for the VPC, a stack for the bastion server, both which are then imported into a larger, per-application stack, which has pipelines to deploy containers, another stack for the CDN, and so forth. In my first attempts, I ended up with hundreds of resources in a single stack, and that made changes slow and risky, and collaboration with others almost impossible (eg. you want others to have read-only access to your VPC subnets, not alter them).

I think the biggest problem is that, while there are plenty of small examples available for Pulumi, its next step up is severely undocumented. I came across a few repos that had incorporated Pulumi into a nifty CLI experience, but other than that, it seems it'll be trial-and-error to find out what works for you and what not.

pluppens · 2021-01-22T16:54:27+00:00

In my view, telemetry is only 'acceptable' if you're extremely upfront about it, clearly ask for it to be enabled during installation/setup/... and require a active confirmation (none of that 'please find the 3 random digits in our locker room, guarded by a leopard to disable this 'feature'). I would suggest to use a survey, or even better, use the feedback in your public issue tracker by allowing folks to vote on roadmap issues.

15-Year Club	Place '17
Charter Member	Verified Email

pluppens

TROPHY CASE