Comments - Maveritchell

Hey, Warlord81 was me. I used an alias when submitting it to the contest because I also ran the site the contest was hosted on and didn't want to salt the voting. Not really news; just FYI.

Most of them are charged abilities, so hold down the button (like you're using the arc caster in the vanilla game) and release when you're ready to use it. Most charge for a few seconds max.

If nothing in the mod has changed since 2009 and stuff just started crashing, then the mod's not the source of the problem. You may want to check settings changes you've made or other mods you might have added.

This isn't a glitch.

The hero characters can block, it's just an active ability now rather than a fire-and-forget. To block, you need to constantly click the block button, which cycles through a block-attack combo. The AI heroes can't do this consistently just as a limitation of the game itself, but human players should have no issue.

Use a standalone installer for the 1.3 patch (linked in the most recent news post) and reinstall that patch. It has config options to allow you to change HUD settings.

So you're catching me away from somewhere I can check, so this may not be exactly correct, but I believe it's custom_gc_11.lvl. It should be located in your ...\Star Wars Battlefront II\GameData\DATA\_LVL_PC folder

It's in the secondary hangar on the Rebel cruiser.

There's a known, unfixable issue with the game's memory management that causes a crash if you play too many modded modes/maps in a single session in a queue. There's no real fix other than to suggest to either keep the queue low or to put any maps that you see causing an issue at the top of your queue.

The 2.2 patch won't fix your issue, but it will address the bugs mentioned in the newspost, so I'd suggest grabbing it when you can.

Yep, removing the map files won't change the number of missions.

Re: 1, you may want to check the resolution on your screen. I know at max res the hero selection can be occasionally clipped, but I've never seen it as unselectable. If that's not your experience, there's no way to scroll the screen, so I'd suggest using the in-game prompt to switch to heroes (i.e. "Press F1 to play as X"), since that auto-selects them.

Re: 2 - You could remove the map assets that way, but the missions are all baked into the single mission.lvl file, which doesn't solve your issue. If you're over 500 missions, you pretty much have to do some folder shuffling once in a while. If you don't already have it, download the 2.2 patch (and make sure it's properly installed), as it reduces the mission content the mod uses.

Nope. That's part of the package, and having the heroes there is part of the thematic reason for the hero support class being there.

It's used in the classic conquest mode.

Tutorials are available on Gametoast for how to add the era to a map. Follow the link out in the sidebar.

Follow the included manual install instructions. If you don't see anything installed, you probably don't have the pack installed correctly. It doesn't default to the Steam location of the game.

All this is is a map.

You're super-violating terms of use here by making a mod with models ripped from another game.

Thanks for the kind words. Please look back a page or two to comments I just made recently to read the status of updating any KotOR content.

Yes. Download the 2.2 patch.

It sounds like you may have let the installer install to the wrong location. The 1.3 patch actually detects SWBF2 install location; the Conversion Pack installer does not.

I'd suggest you go ahead and try performing a manual install (there's an included FAQ doc that covers that). Start by extracting everything directly to your desktop.

You probably have a sides replacement mod also installed that's overwriting the vanilla sides. That will potentially break compatibility with anything that looks for resources from the vanilla sides.

Okay, I think I know what your issues are. Some issues are simply known issues that will persist, and some aren't the issues you think they are.

1) There's a recurrent issue across many mods where if you play specific types of missions/sides in sequence, the game will CTD. It's a memory issue with the game when too many different kinds of sides are loaded. If you try and play Classic Conquest after loading a regular conquest map, you'll get a CTD. The only solution to that is to work around it by playing Classic Conquest first or exclusively (in that game session).

2) Stock Geonosis uber mode was cut in the 2.2 patch, but it was incorrectly left as still selectable. If you see a mode crash like that, doublecheck the cut list (on the 2.2 patch release news item) to see if I just screwed up there and left something selectable that shouldn't be.

3) Classic Conquest shouldn't let you sprint. It's an emulation of SWBF1 gameplay, so it has the same movement mechanics and the same (only) core units.

There's no real way to extract bits and pieces from a compiled mod like this; unfortunately, you can't do what you want to do.

If you can let me know exactly what maps and modes you are seeing issues with and exactly what maps and modes you aren't, then I can probably help narrow the issue down.

Yeah, that's what I suspected. The vanilla rep.lvl is 144419 KB. What happened is you had some sides replacement mod installed and you uninstalled the game through Steam. Steam won't remove non-stock files (it assumes they're unique data and that you created and want to keep it).

What you need to do whenever you're setting up a fresh install is clear the install directory folder. For this game, if you delete the whole GameData folder before installing, you'll be setting up a fresh install. Otherwise, it's still dirty from whatever mods you might have had installed before.

Sidebar: Whatever sides replacement mod you had installed before is going to give you grief with more than just this mod. Mods that replace vanilla content are "dirty," and if any other mod (like this one) relies on certain files being present in the vanilla content and it's not there because of a careless mod author, you'll see issues like this one.

The only way you'll actually get the result you described is if you've got something that overwrites vanilla .lvl data installed as well. If you had some kind of overhaul mod installed before you reinstalled SWBF2, you may not have fully uninstalled that mod.

An easy way to check is to browse to your "...\Steam\steamapps\common\Star Wars Battlefront II\GameData\data\_LVL_PC\SIDE" folder. Please verify the size of the rep.lvl you find there.

What do you see when you try and play (for example) Bespin: Platforms CW conquest?

The Steam version is the official 1.1 by default (you should see v1.1 in the top-right-hand corner of the main SWBF2 menu when you load it).

Install this mod (following the manual install instructions if necessary) and then install (on top of everything else) the updated (MP-fix) 1.3 patch last.

The conquest on the Conversion Pack maps is different, but that's not one of the default modes of the vanilla game. There may be a terminology confusion here. Loading up Coruscant: Jedi Temple conquest will be the same as vanilla (because it is a default mode). Loading up Tatooine: Dune Sea conquest will have added units (because there's no such thing as default SWBF2 Dune Sea). Loading up Tatooine: Dune Sea classic conquest will have the SWBF1 defaults (because it was a default in SWBF1).

As for the patch settings, I took a look at the installer in the link above, and I see the reason for the confusion. The guy who edited the 1.3 patch to update it for Steam multiplayer didn't add back in the configuration settings from the original patch. Download the latest version of the patch from this thread:
Gametoast.com

And then reinstall the link from the topic mentioned above (to overwrite the necessary files for MP compatibility).

You're correct. The KotOR GC is just the KotOR era.

If you want to play conquest just like it was in SWBF1, play the "Classic Conquest" gamemode. It's straight-up just the five classes from SWBF1, only-AI heroes, etc.

None of the default gamemodes from SWBF2 are changed by this mod either.

The HUD is a totally separate thing and definitely reconfigurable. Take a look at the most recent news post for the current version of the 1.3 patch, and you should be able to use that to reconfigure the HUD to your liking.