[pk3] New Release - Ninja Pack v1!

[[-z-]]

Yesterday I've officially released the ninja pack.

What Is It?
The ninja pack is a simple no risk, drop-in solution for getting your Nexuiz configured like a ninja. The ninja pack breaks down useful configuration scripts into a logical framework. Thus giving you an out of the box solution with advanced configuration options in a module based system.

What does it offer?

Demo Management - Take advantage of Nexuiz's built in demo review/recording features with loadable keybinds
Weapon Mangement - Utilizing the Nexuiz 'bestweapon' function which allows weapon fallbacks, this pack has broken down the weapon management into logical divisions of use.
Team Messages - Enhanced defaults and mousewheel messages
Variable FOV - Change your field of view with your mousewheel
HUD ehancements - An enhanced HUD, netgraph, fps and speedometer
Very Customizable - Your current binds will run on top of it! If you already use 'autoexec.cfg', just rename it to 'personal_binds.cfg" and it will take priority over the ninja pack keybinds / scripts



More information and download here

[Psychcf]

There's only one bind missing... the hook (although, ninjas are too cool for hooks)

Nice job though.

[[-z-]]

There's only one bind missing... the hook (although, ninjas are too cool for hooks)

Nice job though.

Thanks.

Hook's on my mouse . I mention this in the readme.

[[-z-]]

I thought there would be more interest in this. Any care to fill me in?

[GreEn`mArine]

looks interesting. I've been wondering about this "An enhanced HUD, netgraph, fps and speedometer" thing, though. Do you just mean that you provide keys to turn these off and on, or do you mean that you changed something of these HUD elements?

[[-z-]]

looks interesting. I've been wondering about this "An enhanced HUD, netgraph, fps and speedometer" thing, though. Do you just mean that you provide keys to turn these off and on, or do you mean that you changed something of these HUD elements?

It is just the defaults, sbar_hudselector 1, netgraph 1, etc.

I have not stylized anything. This is all cfgs currently, no CSQC.

The ninja pack aims to establish a hierarchy for config files. Making them easier to create, maintain, share and understand. The original idea was based around the fact that I wanted to travel with my settings on a USB stick or download a pack. I wanted everyone to be able to edit their own keybinds and add their own scripts but still have strong core as a base.

Because of the way it's designed, it's very easy for a user to customize their config to their needs but still have the luxury of having a maintained core set of scripts, settings, keybinds or whatever else they want to put in their ninja pack.

[esteel]

Well for an beginner that might be too much info at once and could be too distracting. I play without netgraph as i see little use in it. Its easy to not when ping is high or changes a lot and most of the time a look at the scoreboard is good enough.

Though the idea with keyboard-sheet is good, maybe one with the default keys could be added to the Docs dir.

[[-z-]]

Well for an beginner that might be too much info at once and could be too distracting. I play without netgraph as i see little use in it. Its easy to not when ping is high or changes a lot and most of the time a look at the scoreboard is good enough.

This is a minor change that's easily made to fit your needs. As I've noted in the documentation:

nn_conf.cfg - the 'general nexuiz configuration' file
This file contains general nexuiz tweaks and sensitivity / fov settings for AoT's zoom script.

All the user has to do is extract that file from the zip and edit the line they'd like different. Optionally they can rename the pack with a prefix or suffix and load the edited files back in to create their own custom pack.

The ninja pack is catered more towards serious games, as most of the Nexuiz Ninjaz projects and applications are. It offers ~out of the box~ advanced functionality that's well explained and documented.

Though the idea with keyboard-sheet is good, maybe one with the default keys could be added to the Docs dir.

The CSS keyboard is built off an XML file, so it's pretty easy to create new keybind definitions. I plan to write all sorts of functions that will act as middleware in helping users configure, reference and share keybinds. I'd like to complete this project before releasing it into the wild. I'll likely write a generator before the time 2.5 (2.4.3?) is released.

In the mean time, I would be more than happy to add the defaults to my application.


Edit:

Also, something that had me caught up was the fact that the German keyboard apparently looks like this:



Does it really look like that?

I wanted to make it available to Germans too but that's some tricky CSS.

[GreEn`mArine]

The German keyboard is correct.

[[-z-]]

I know I convinced a few people on IRC to take a look... but still no feedback .

Help me help you!