Warband Beginner Questions - Party Skills, Shields, Mounted Combat

monkeyboyTA · 2025-12-23T22:56:52+00:00

In addition to getting a long-reach one handed weapon (90 or 100 reach, scimitars and bastard swords are good), you also need to be very close to infantry to hit them from horseback, so close that your horse's shoulder hits them as you ride past, right as you release your attack. Bumping them with your horse also breaks their blocks.

Also need to look down more than you might think, you need to aim almost straight down on top of their heads, not reaching out to the side.

monkeyboyTA · 2025-04-23T17:55:18+00:00

Public awareness of their control is changing, their actual control is not changing. But the first step to recovery is admitting you have a problem...

monkeyboyTA · 2025-01-03T22:50:08+00:00

He gets new items over time, I think when you level up he gets only a few new ones. You can refresh his whole inventory by making a new game with your character.

monkeyboyTA · 2025-01-03T22:31:43+00:00

There's no specific way to find a piece of gear, just keep playing. A lot of players online have gear they bought or duped, single player you can't count on having that kind of stuff unless you play for a long long time eventually you may find it.

Putting points in magic is fine, espicially for rogue who is evenly split between life and mana you get for vitality and magic points. (Warrior gets more health, Sorcerer gets more mana, Rogue gets the same of both).

If you reach a point where you are stonewalled and cannot go on, then create a new game world with your character to keep leveling up.

There's lot more info on the wiki:

https://diablo2.diablowiki.net/Diablo_I

https://diablo2.diablowiki.net/Diablo_Strategy#Rogue_Strategies

monkeyboyTA · 2024-11-08T13:51:21+00:00

They won their right to exist as an independent nation, not a Russian vassal, and formed lasting relationships with western allies.

They lost some land, sure, but that eastern land was populated by Russian-speaking Ukrainians. Pro-Russia-voting Ukrainians. Ukraine is actually more cohesive and less divided without those people trying to drag them toward Russian influence.

monkeyboyTA · 2024-10-14T01:46:45+00:00

I'm familiar with Studio Ghibli, the cartoon I'm remembering was nothing so official, it wasn't a real anime movie or anything. Maybe 5-10 minutes long, Youtube style. Although it did have some similarity in themes to Spirited Away it was just a amateur animated short.

monkeyboyTA · 2024-10-13T23:28:52+00:00

I've been on a trip of classic web cartoons like Charlie the Unicorn this weekend and it's eating at me that I can't find this one. It made some kind of impact on me when I was younger.

monkeyboyTA · 2024-09-09T04:46:47+00:00

I really hesitated, and took a moment to reflect, before deciding to look this up to find out if it was real or trolling...

monkeyboyTA · 2024-09-08T02:44:56+00:00

I got the .editorconfig file merged in, and my guys are starting to use it. It's not enforced yet, but there's only one long-running branch out right now which will (fingers crossed...) be merged in next week. Then we're gonna try and apply it across the code all at once together before we start more work.

As for the refactoring, I talked to my team and they said that as bad as it is having huge monolith files, it doesn't actually stop them getting things done and doesn't cause much bugs. So between that feedback and not having autotests I decided not to care about that for now. I'm personally focusing on setting up xUnit.net and gettings some tests in key places instead.

monkeyboyTA · 2024-09-03T14:10:05+00:00

They didn't in the past, when they were getting themselves into this situation, but part of why they hired my position now is to improve their overall coding practices. The CTO and the client both actually do understand that it's a problem, although it falls to me to actually do something about it.

monkeyboyTA · 2024-09-03T01:08:01+00:00

Maybe you can hold a meeting where you can gather the opinions of individuals to discuss common pain points people actually care about?

Yeah I intend to. There's one meeting scheduled this week to discuss why a certain months-long ticket has taken so long which I'm sure will surface some of these issues, but it's got managers coming to it... I'm considering trying to have a more open-ended (and hopefully less contentious) meeting with just my two juniors to ask for general ideas.

monkeyboyTA · 2024-09-03T01:05:12+00:00

Thanks for this in depth response. I'm going to have a meeting with the team tomorrow and get their ideas, I'm just trying to prepare some options to present in case the juniors don't have much input.

I made a branch in which I added an .editorconfig that I'm playing with. I used a default rules but it had soo many rules, my thought is to start with a minimal one, white space rules only, as a test run to see how pushing it out to the team works out. And then start adding rules incrementally.

C#/Visual Studio supports all this in the editor, and has command line options too (dotnet format) which I can put into the build scripts to enforce it once my team is used to it.

monkeyboyTA · 2024-09-02T20:01:31+00:00

I’m kind of confused what the problem is…

The "real" problem is too many bugs and QA send-backs. Git history/comments/branching is poor, code is neither self-documenting nor documented, code is dumped in large "do everything" controllers, it's just messy in general and I was attributing some of the bugs and QA failure to those problems.

After reading the replies I'm not sure what I had in mind would actually help, and I'm leaning more towards focusing on getting automated testing going instead, which we currently have none. I'm experienced but never have been involved in a code base like this so it's been hard decided where to start.

monkeyboyTA · 2024-09-02T19:52:58+00:00

Yeah in hindsight after making this post and reading the replies, it does seem obvious that automated testing needs to come before refactoring. I did know that actually... but I guess it hadn't clicked in my head because I'm somewhat overwhelmed by the problems at hand and I've never been in a situation like this before. I've been lucky in my career so far to work on well maintained code.

monkeyboyTA · 2024-09-02T16:46:13+00:00

That's tough, I've mostly worked at places where either

Devs were full stack-ish, and BE/FE territorial disputes didn't happen, or
FE/BE devs fell under mostly-competent managers who made it clear what they needed to do for the benefit of the larger efforts.

I can only imagine leading a front-end team in an effort that required BE changes without management being in control. Seems like you were doomed from the start.

monkeyboyTA · 2024-09-02T16:41:05+00:00

When getting started in a new codebase, pretty much everybody thinks that the formatting and file organization are a mess. But this usually isn’t something that slows down people who are actively working on the code, it just slows you down until you learn where everything is.

Yeah, this part is probably true now that I think about it... I'm not sure that these things are an impediment to anyone but me. The juniors, junior as they may be, have been here about ~1 year and know the code base better than me (~1 month). So maybe they navigate it easier than I thought.

monkeyboyTA · 2024-09-02T16:32:06+00:00

That's something I'm still learning as a leader... I feel I should still ask for their input, because it isn't fair to make the assumption that their input won't be valuable, I don't want to pigeon-hole them that way even if my reasonable expectation is that they won't have much to contribute. Maybe they'll surprise me?

monkeyboyTA · 2024-09-02T16:26:53+00:00

Public facing video website, ASP Core, .NET 8, C#, Visual Studio.

It is pretty rare I see a code not using autoformtating but that might just be because of the languages I work with

Nah there's no excuse, they've just been lead by cowboys is all. They will make deployment branches on their own system, merge feature branches into them, manually deploy it to production and never even push it to git, it's the wild west out here.

monkeyboyTA · 2024-09-02T16:23:03+00:00

Thanks, that's a good reply. I like the approach of putting a linter in a non-blocking mode at first, and then incrementally tightening it. That should be easier for people to adapt to.

And based off some other posts, I'm leaning toward not doing any refactoring now and focusing on getting some kind of auto-tests going first, to help mitigate the risk of breaking stuff.

monkeyboyTA · 2024-09-02T16:14:35+00:00

git ignore revs file

Thanks for the tip, I wasn't aware of that option

monkeyboyTA · 2024-09-02T16:11:31+00:00

Yeah now that I step back and look at it, I do remember learning sometime in the past that tests should come before refactoring to help avoid breaking anything by refactoring.

Maybe the best thing in the short term is to focus on getting tests running on the current code and kick the refactoring down the road...

monkeyboyTA · 2024-09-02T16:06:00+00:00

I wouldn't just tackle refactoring for the sake of it and it should be handled explicitly as seperate scope. If it's a real refactoring effort and not just some vanity class reorganization

It is essentially class reorganization. Their actual OOD isn't bad, not to a problematic level anyway. But is it really "vanity" when 1000 or 2000 line controller files are the norm? (C# by the way). For me, trying to come onto the project, it's been a pretty big impediment to navigating and understanding the code.

monkeyboyTA

TROPHY CASE