This is a read only copy without any forum functionality of the old Modcraft forum.
If there is anything that you would like to have removed, message me on Discord via Kaev#5208.
Big thanks to Alastor for making this copy!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Synric

Pages: [1] 2 3 4
1
Miscellaneous / Re: Server functionality
« on: March 18, 2017, 05:41:14 am »
Awesome, thanks for the reply

2
Miscellaneous / Server functionality
« on: March 16, 2017, 10:27:58 pm »
I was just curious, last time I checked (a VERY long time ago), due to the opcode change bullshit they started in Cata, post-WOTLK servers were extremely lacking in capability/features compared to their WOTLK counterparts. Has this improved on the Warlords branch?

3
General / Shoutout to Steff and the Rest
« on: March 07, 2017, 04:34:29 pm »
The new site looks great, feels much improved. Thanks to you guys for keeping all this stuff running, it's much appreciated yall!

4
Noggit / Re: [Question] File list for current Noggit build
« on: February 28, 2017, 01:05:20 am »
I got it to work. I had missed a DLL when i was switching out the ones that are in the repo with x64 versions.

5
Noggit / [Question] File list for current Noggit build
« on: February 27, 2017, 04:20:44 pm »
Hey yall, just compiled the newest version of Noggit off the repo, was wondering if anyone could tell me what all the DLLs needed to run it are. When I tried to start it I got alternating errors between error 0007b and missing DLL files when starting noggit. I went and copied all the DLLs from my lib builds, and I'm down to just the error.

I built each library and noggit itself for x64 and everything in terms of builds went off perfectly, so I don't think its anything from the builds themselves with MSVC14.0. I set up the noggit conf and all that, so I'm down to wondering if I missed a DLL to copy.

6
Random / Re: Wiki Formatting
« on: August 17, 2016, 07:18:56 pm »
Sorry, real life and moving got the best of me trying to do this "little" project. I should get some work done on it this weekend!

...

Edit: Or... maybe not...

7
Software Development / Re: [PROJECT] [Cataclysm] Database Editor
« on: August 17, 2016, 07:12:00 pm »
Might a make a suggestion? Right now you only edit a handful of tables and DBCs, but as more are implemented the interface as it stands will likely get incredibly cluttered. On the same note, you have a lot of spare room within the interface itself that has nothing taking it up. Might I suggest moving the tabs from going across the top to perhaps going down the side? It'd both take up a bit of the large amount of free space, and (with a scrolling option) would allow a person to easily add new tabs/editor tables without making it look bad. For example, right now you have:

Creature           Game Object          Item         DBC
Search             Edit          Location           Loot            Involved In          Smart AI        Code

Id propose:
Creature
Gameoobject
Item
DBC

Then maybe make it collapseable, so if you,, for example, were working on a Gameobject it'd look like:

- Creature
+ Gameobject
Search
Edit
Location
Loot
Involved In
Smart AI
Code
-Item
-DBC

I'd do a similar method with the DBC section. Right now the edit functions down the side don't serve much purpose. They could easily be moved to their own pop-up box or something. What would be nice is a listing of the DBCs in your DBC directory that you defined, as opposed to having to go into the tab and open them individually. I think the DBC section could also be a hybrid of what you have now and what I'm suggesting, as you do have a ton of options specific to DBCs. So maybe...

Open         Apply Scheme      Save Scheme       Search    ....

-Creature
-Gameobject
-Item
+DBC
Achievement
Achievemet_Category
Achievement_Criteria
....
ZoneMusic

That's how I'd go with it for what you currently have, but ANOTHER  suggestion would be to make the schemes not even part of the editor interface itself, and move them to a text file, then simply have a reload scheme button. Personally I'd rework it to:

Open         Save      Reload Scheme     Search   Go To    Insert Line         Copy Line        Delete Line

-Creature
-Gameobject
-Item
+DBC
Achievement
Achievemet_Category
Achievement_Criteria
....
ZoneMusic

I think the Save As, Close, clear line, copy line to, Search Column and Replace in Column buttons kinda just take up space as they'd be rarely used I'd imagine. I'd replace the close line with a dialog box when attempting to close the editor or leave the line asking if you'd like to save changes. Those are just my suggestions though. Otherwise, good editor!

8
Random / Re: Wiki Formatting
« on: July 19, 2016, 05:28:57 pm »
Thanks for the suggestion Ascathos, it's a good idea in theory but I don't think I'm gonna go with it. I just have my doubts about it being the most effective way of displaying the information. We're just gonna continue with version-based tables for now.

On a related note, I'm gonna try and work through all the tables sometime next week, so if you have anything you'd like to see done you have until Tuesday to explain it if you want me to do it when I do the rest of this.

9
Random / Re: Wiki Formatting
« on: July 18, 2016, 09:11:43 pm »
Well if we do that are we not just in the same place we currently are?

10
Random / Re: Wiki Formatting
« on: July 18, 2016, 08:54:36 pm »
Thats rare, but it does happen. (See: spellpower.db2. Originally contained manacost, turned into PowerCost basically).  

Still though, how do we handle the changing columns? For example (I dont have a DBC thats done this pulled up, but it does happen), in one patch the columns could be ordered like

ID
SpellID
Cost
Powertype
etc.

and then it gets re-ordered like

Cost, PowerType, SpellID, ID

How do we handle re-orgranization between patches?

Also, how do you propose handling when a column is removed? Like spell.dbc goes from a max of 315 columns to 8. I think theres just a bit too much changing to use 1 table on the page.

11
Random / Re: Wiki Formatting
« on: July 18, 2016, 07:10:34 am »
My plan had been to do this this previous weekend, but RL got the best of me. Eight days from now I'll have a bit of time to myself, and I'll update the wiki.

Problem with the variable idea: We keep the information presented in order. Blizzard does not. They sometimes randomize certain DBC columns from xpac to xpac... Any ideas to get around that?

Also, the columns in a dbc can change patch to patch. Doesnt happen often but for example theres a DBC who had a column added between 3.0.2 and 3.3.5. So, at least we'd need to add patch as well as expansion.

12
Random / Re: Wiki Formatting
« on: July 14, 2016, 06:59:10 pm »
1) Must have switched off __FORCETOC__ at some point. My bad.
2) Thanks for the note on the version boxes. I'll go ahead and start using those
3) I can change it up if anyone else has a problem with the expansion level heading. As far as struct/table labels I propose 3 options, it's up to yall
- Keep them as is
- Keep them, but hide from the ToC (I dunno why we'd do this, but hell its an option)
- Remove them. Up to yall, I'm cool with whatever.
As far as repeating comments I don't really see the harm in the tables. Comments don't create new lines therefor not using up more space, and would alleviate the need to jump around with the definitions. If a comment needs to take up subsantial space it really should be in the extra information sections, in my opinion.
4) I can see why, but I can also see why not. It's kinda nice in my opinion to be able to search by version... I guess I don't really care either way
5) No comment. Don't really follow what you're saying.

Edit: After looking at how a few look with and without the expansion headers, I'm just gonna go ahead and remove those.

13
Random / Wiki Formatting
« on: July 14, 2016, 05:44:25 pm »
Hey everyone,

As some of you may have noticed, over the last few days I've kinda taken it upon myself to reformat the pages on the wiki. I'm not making any content deletions (for the most part, more on that later), I'm simply changing the presentation of the pages to be more standardized. As of writing this I am around 100 out of 427 DBC pages in.

Obviously I am not in sole control of the wiki, and a lot of people contribute to it. Therefor I'm writing this post to try and explain my thoughts behind my changes and, more importantly, to get feedback about what I could do better, other users thoughts, and anything else you may have to say about the wiki.

Tables of Contents


I've been adding a Table of Contents to each page in the DB section. I know this may seem superfluous on pages with one entry, but for most pages, to me at least, it's about quick and easy navigation, and for the pages with one entry it's about standardization and presentation.

DBC Information


Directly under the TOC I like to include any short information that would relate to the DBC regardless of the version. This is information such as when it was added or removed, and a short explanation of the function of the DBC if necessary.

Version Sections


One of my major problems with the wiki is the randomness of a specific builds information within a page. I've begun to rearrange into a new setup. It goes something like this: Expansion (Oldest first) - Build - Table/Struct. Specifically formatted as follows

==Version==
Version number and build number, i.e., 3.3.5.12340

===Type of information===
Depending on who wrote it it's either ===Struct=== or ===Table===. Sometimes we have both.

Addendum: On this note, this will probably be the most controversial statement to some people in this thread: I prefer both. The wiki, in my opinion, should not be able helping one type of person versus another. Programmers would prefer it in struct form, content developers probably prefer it in table form. I prefer to have both types of information, it takes nothing away from the page. I'm not a programmer, I'm a content developer, and it helps me far more to have the table for quick referencing. On the flip side, the guy who writes the tools my server uses is able to easily copy/paste the struct. Everyone has their way and need of presenting information. I say let the users decide how they need it, it really isn't about us.

Extraneous Information


I try to keep extraneous information at the bottom of the page. This type of information includes any information that explains the information contained above. Usually this is information like Flags and what they do. I try to separate them based on version, usually by placing some sort of stop notice between expansions. Whenever something is added that takes up a value in a previous list (for example, in Wrath only values 1-25 work, then in Cata add 26-30, but also go and add value #3) simply note it for that value.

Categories


There seems to have been some different ideas of how the category section at the bottom should be handled. It looks like the prevailing theory ended up being listing the DBC category, then the specific expansion DBC category we have information on that table for, and specific version category. So, we're going with that. The style I'm using is Expansion - Build, so for example a page with information for 3.3.5.12340 and 6.0.1.18179 looks like this:

Category: DBC | DBC WOTLK | 3.3.5.12340 | DBC WoD | 6.0.1.18179

Other Information


Schlumpf prefers DBC information added in a structure style, I add information in Table form. Each one serves  a purpose. Feel free to add either, only Schlumpf will judge ;)
This post is for discussion about my changes, your ideas, things we can do in the future, and anything about these changes. Thank you for reading.

Edit: Removed expansion headings. Back to just by version

14
Noggit / Re: [QUESTION] Noggit not compiling
« on: July 13, 2016, 03:15:02 am »
http://pastebin.com/gDrX79sv

and it was a cache delete/reload when I tried, I dunno what happened :/

15
"Retro-Porting" / Re: Lets play a game of mix-and-match: Spell.dbc
« on: July 13, 2016, 02:48:55 am »
Alright, I've updated it with everything I've ascertained so far. I'll add more as I get around to having reasons to update them. Theres a bunch of unknown values spread around, but at least I could fill in a good amount of blanks on the following DBCs:

SpellDispelType
AnimationData
ModelFileData
TextureFileData
FileDataComplete
ItemDisplayInfoMaterialRes ‎
ItemDisplayInfo
Spell
SpellEffect - (This is the only one whose values I've fully listed may not be correct...)
SpellxSpellVisual
SpellTotems
SpellTargetRestrictions
SpellShapeShift ‎
SpellReagents
SpellPower ‎
SpellMisc
SpellLevels
SpellInterrupts
SpellEquippedItems
SpellDescriptionVariables
SpellCooldowns
SpellCategory
SpellCategories
SpellCastingRequirements
SpellClassOptions
SpellAuraRestrictions
SpellAuraOptions
CreatureModelData

I also hope its okay with y'all that I made a new category called SpellData to house all the DB2s directly related to Spell.DB2/Spell.DBC, and I put an interactive table on there with direct links to where to find all the data that's been sifted around since 3.3.5 (largely just the above table, with formatting). I also hope you don't mind that I sorted a few of the pages by their version number if they had enough headers to warrant a table of contents.

Pages: [1] 2 3 4