Search the Community
Showing results for tags 'c#'.
Found 4 results
220 downloadsItemSync is tool for keeping your Item.dbc up to date with your server's database. It can also insert items which are n DBC, but are missing in database, into database. This can come in very handy for mass-importing NPC-only items (like glaives for sentinels and so on) into database, so players can use them as well. For tutorial how to use this tool, compatibility and other useful info, check README in repository. Repo: https://github.com/Amaroth/ItemSync2 Credits: Barncastle (and people who helped him) - for WDBXLib for DBC/DB2 and code revision&suggestions. Kaev for some small yet very useful tips about WPF. Смердокрыл for DO STUFF(tm) button suggestion.
150 downloadsVersion 2.0 is under development at the moment. Repo: https://github.com/Amaroth/GobGenerator2 Upcoming features: Change UI to WPF Provide configuration options via XML (thus extending compatibility) Direct DBC editing (without need of conversions to CSV) Include features ensuring avoidance of duplicate display and gameobject creation Extend possibilities of choosing what gets generated and what not Video tutorial: Yet another little tool from me. This one creates gamobject displayIDs and template gameobjects out of listfile, which means that it can create thousands of gameobjects in a few seconds - great for projects making their custom models and retro-porting them from newer expansions. Listfile can be anything containing full paths to files separated by line breaks. It creates gameobjects only for M2 and WMO files, others are ignored. Tool also generates template gameobjects with their model names as names (and optional prefix/postfix), which means that generated models are easily recognisible and that when you find nice-looking model in WMV and want to use it for spawn or for creating some gameobject you need, you can find that gameobject's template generated version just by typing its name into lookup command. This makes this tool viable even for usage on models which already are in WotLK client, as it makes life of spawners much, much easier. - Generate your GameobjectDisplayInfo's CSV file and put it into directory where GobGenerator is. - Get or create a listfile. The easiest way of doing so is simply creating an MPQ with all models you want to have gameobjects made of and just extracting its listfile. Note that you can also use listfiles of blizzlike MPQs, if you want to generate gameobjects for all blizzlike models as well. - Open GobGenerator. Select input listfile (you can also type into model path field, which makes using larger number of listfiles with similiar names in the same path very easy). - Fill in your database credentials. You may want to test a connection before proceeding. - Start displayID is being taken from your GameobjectDisplayInfo.dbc (its 1 higher than the highest ID found in DBC). If you happen to see value 1 here, something is really wrong and check if your CSV is OK and in GobGenerator's directory. - Start entry is by default 400000 and I'd suggest you to keep it that way. There are some gobs on 300000+ entries in blizzlike TC2 DB, thats why I've used 400000. Final entry of generated gameobject will be start entry + gob's displayID. This means that gob with displayID 96835 will have entry 496835 - and that can be sometimes very handy. - Fill in prefixes and postfixes of gob names. Don't forget to add space behind prefix and in front of postfix, if you want to have it there. Gob's name will be prefix + its model name + postfix. So, if you choose "[Gen] " as prefix and " [DO NOT EDIT]" as postfix, result gob name might be something like "[Gen] mymodel.m2 [DO NOT EDIT]". - By default INSERT queries are being used, which means that if any gameobject entry is already taken in DB, it will result in error. You can choose REPLACE, which will overwrite whatever might be on entries where gameobjects are to be put. - Done, click on generate. If you have multiple listfiles, just select the 2nd one and click on generate again and so on. - If anything goes wrong while SQL queries are being executed, those which weren't successful are being held in a backup file. There is also a file which keeps all possible SQL errors. Thats all, C# src is, as always, included, and DBC to CSV convertor DBCUtil I use for this kind of quick tasks as well. If you happen to find any critical bug, let me know, but I don't really have a spare time to make source nicer or something like that, so report really only issues with functionality itself.
129 downloadsVersion 2.0 is under development at the moment. Repo: https://github.com/Amaroth/NPCGenerator2 Upcoming features: Change UI to WPF Provide configuration options via XML (thus extending compatibility) Direct DBC editing (without need of conversions to CSV) Include support of items held in hand A tool for generating CreatureDisplayInfo.dbc, CreatureDisplayInfoExtra.dbc and optionally creature_model_info and creature_template data for a character created in WMV. How to use: - Convert your up to date CreatureDisplayInfo.dbc and CreatureDisplayInfoExtra.dbc to CSVs and place them into the folder with this tool. - Open a WMV. Create your character, and save it as .chr file (F7 hotkey). Also save its texture (by using File>Export Model>X3D... option you'll get texture you want and some mess you can delete). Repeat this step for each character you want to create creature displayID for. - Open an NPCGenerator. Fill database connection credentials (you need to do so even if you turn off creature_model_info and creature_template generation, because NPCGenerator will need to get item display IDs from your database). - Now just click on Select .chr file, select your .chr file. Click on Select texture, select your character's texture. Check if there's anything else in window you'd like to change (you'll probably find yourself using all other options with their default values). Click on Generate. Repeat for each character. - ?? - Profit. C# src is included. I'm opened to suggestions and feedback, however, I'm quite busy so I'll probably just fix critical bugs if you find any.
142 downloadsAbout: This Launcher's main purpouse is to be easy, fast and convenient to use for both players and admins. Players get their client updated by clicking on one buttons, and admins don't have to spam news with patch releases, links to new versions of patches and so on. Launcher is nearly fully configurable and src is included, so you can do basically whatever you want with it. You can also fully translate your Launcher to your native language (or correct any posible mistakes I made since english ins't my mature language :D). You can also create multiple versions with different languages - all this without actually changing a src. If you happen to need to change src anyway, its written in C# (WinForms) and hopefully not too messy or too badly documented for you. Please note that this is the first version to ever be released (its actually a configurable remake of already released software, but... well). It is possible there are some unhandled exceptions or even bugs. I have been testing this tool for some time and there shouldn't be any real major issues, but one never really knows for sure. Keep a backup of your game client and don't set KeepBackups in config to 0 unless you are really confident this works correctly. Launcher is capable of following things: Deleting Cache folder. Removing (I use different word because optionally the most recent backups are being kept) outdated (or on web's filelist missing) MPQs in Data folder. Downloading any files specified in web's filelist into any specified local path in WoW's client folder. Unziping zipped folders (sadly, only zip is supported, rar, 7z and others not). Useful for AddOns. Dividing files into two categories - optional, and non-optional. User can choose which optional files are to be downloaded. All files can be organized into LinkedLists. If a file with a LinkedList is optional, it is an optional group. Player can either keep all files from an optional group, or none of them. Optional group can contain both files and zipped folder (AddOns). Self-updating, if a new version is released. Version system is based on one simple double-typed version number. Using different filelists. Which means you can have separated filelist (and files) for GMs/Devs and for players. Launcher also includes Changelog Browser (changelog entries have name, date, description and optionally a picture). There is also a Changelog Editor. To access it, you need to enter FTP login information. This serves for authentization of staff members, and also enables Launcher to upload edited changelog to FTP (so you don't have to put it there by hand). File downloading fully asynchronously, so users can browse changelog while files are being downloaded. Download speed, progress bar, percentage and stuff like that are being shown as well. Displaying of "hello image" which can for example be an image with some breaking news and stuff like that. How to configure: Rename your Launcher to whatever you want. Something like MyProjectsLauncher. Create a folder on your web where web side files will be kept. You can divide multiple things into multiple paths, but I'd recommend you to just have everything at one place. I'll call this a web's root folder (root folder for launcher stuff, not for web as whole, hopefully you understand me). Your web's root folder must contain file with current Launcher's version (I use launcherversion.conf). This file must contain only one double-typed number with . as a separator. Version of Launcher I'm releasing here is 1.0. You can change your Launcher's version in Core/Config.cs. If Launcher finds that value in launcheversion file is higher that its version, it attempts to update itself. Your web's root folder also must contain a zip file with a Launcher, its LauncherConfig.conf and optionally with its LauncherIcon.ico. I've named it Launcher.zip, again, you can rename it. Your web's root folder also should contain changelog.xml. If it is empty or isn't found, a new one will be created when you'll try to create a changelong in Changelog Editor. Add a hello image (in my case hello.jpg) into your web's root folder. This image will be displayed in Launcher's main window and will most likely be used by you for displaying some breaking news. Add a realmlist.wtf file into web's root folder, if you want Launcher to change realmlist of players to your server. Also add the most important file for Launcher to your web's root folder: a filelist. I've called it filelist.conf. You can have multiple filelists on your web and release multiple Launcher versions which use different filelists. By using this technique you can release a Launcher for developers and a Launcher for players, which use different filelists and thus can download different files. Set your filelist. Follow examples in my filelist which you can find in an example web root folder I've added into this release. Read instructions very carefully, as filelist syntax should be strictly followed. Launcher can handle some fooled up entrys, but not all, and if filelist isn't succesfully readen (or if any files mentioned in it are missing/paths to those files in a filelist are incorrect), Launcher will simply refuse to update a game client. Open a ChangelogConfig.xml. You'll need to change all data in Paths element - make really sure that those paths are correct. By doing this you'll connect a Launcher to your website. Pay especially high attention to FTP path to a folder where changelog.xml is, what it should look lile- You may want to change something in Main element. Its not very likely, but take a look there. MainWindow element contains WindowName subelement. You'll most likely want to edit this. ChangelogEditor element contains DateFormat subelement. If you want to change this, DO SO BEFORE YOU CREATE A CHANGELOG. Otherwise you will end up with incompatible changelog and Launcher. The rest of ChangelogConfig.xml contains names for UI elements and various messages Launcher can output. Create your own icon in PNG format, google some online PNG to ICO converter. Done. Test if everything works correctly and release a Launcher. Launcher is to be put into WoW's root directory and thats pretty much all. Making this application took really some time and effort, I had to learn a lot of things to make it work and plan to make more tools and apps for WoW development. If you really like my Launcher and want to give me at least something in return to support me back, my Paypal account is: email@example.com Its ofc up to you. Launcher is here for free, with source included. Do whatever you want with it. You may both keep using just my Launcher (and future releases, it runs on my project ad well, so I'll probably keep releasing bug fixes and so on) or create a new one based on this. I do realize that some parts of an app need improvement, let me know if you have any ideas or if you want to contribute to code of this public version. Contact: Skype: striker159753 Mail: Amaroth7@seznam.cz Repo on GitHub: https://github.com/Amaroth/WoWMod-Launcher