xzodia wrote:i really want to keep this in as plain english as possible and have different sections on separate pages, also it looks a lot better with the margines set to 1cm >_>
i think it would be better to just write the text and format it all when its finished
So, if you write a section please upload it in as a simple text document (txt) called:
[Name of Section Here].txt
then i'll put the link in the table of contents in the 1st post
But mine has pixs >_>
If your gonna do it like that then i might just write the whole thing up myself, seeing as no-one else seems to be helping anyway.. and for some reason i really feel like doing this, probably fueled by the hatred of so many idiots...
If your gonna do it like that then i might just write the whole thing up myself, seeing as no-one else seems to be helping anyway.. and for some reason i really feel like doing this, probably fueled by the hatred of so many idiots...
when you say do the whole thing yourself how do you mean? and i was actually about to go write something >_>
mb a new intro since i didn't really like yours...
xzodia wrote:i just had a thought...what if i make a forum specifically for this? would people be will to go there on a regular basis and contribute something? say at least once a week...preferably more...
edit:
eternal wrote:
Ultamis wrote: I tried to swap a few projs with bsps before
You're not the only one.
Well I think the dictionary should be first, because if a noob starts reading 'How to swap a bsp' He will be like 'well WTF is a BSP?'
*skips to next chapter*
So ya. Thats my thoughts.
i keep that in mind when i wrote the contents, the point of this isnt a load of tutorials its how modding works and how to best apply it, if you get what i mean
and the appendix is there to be looked at when the reader is unsure of a term such as bsp, and should be updated as the rest of the 'book' is written to ensure all terms are covered
A forum or a wiki would be good, I think that I would like to contribute to this as much as I can, I don't ever post any mods really, but I've learned a lot about the map structure and whatnot and could probably put a lot of stuff into beginners terms.
just incase anyone was unsure of what this project is about:
My Introduction wrote:This is not a tutorial.
This is designed to help you understand how to mod.
Hopefully, when you have finished reading this you will be able to make a decent mod without even looking at a tutorial, assuming you have an ounce of intelligence.
This 'book' has been written in the order that it should be read in, duh. It is unadvised that you skip a section even if you think you know about it because if your new to modding, then chances are that you don't know as much as you think you do.
If you see a term that you are unsure of, or want more information on then see the Appendix, found at the end of the 'book'.
tbh i can think of about only 2 other people on this forum who would actually contribute to this something meaningful. I wouldn't say your intro is any better than mine, its scope also differs from what i intend to do, so i think ill just work on my own tut. Feel free to add to the document i posted, though, and sorry for pledging my support earlier on.
Humm; late is better then never. I general "Modding" guide would be very nice. I am currently working on a halo 2 "skinning" reference. Perhaps the two might be combined one day. I would say i would help but as was pointed out indirectly I am not very "knowledgeable" in this type of thing. I USE information, not generate it, lol.
-DeToX- wrote:I think you should explain tables too.
Heres a list.
http://halo-forge.net/DeToX/Map%20Layout.txt
If you see two items on one line (Model 1 & 2, or Unicode Table & Unicode Table) it means that they jump back and forth(Example: Model 1 then Model 2, then Model 1 again, etc).
Definitely explain the map structure yes. Btw you realise the eof map padding, and yet not the index padding
No I know the padding's. Thats just of the tables.
You might want to remember that ..
A phmo's Reflexive's Translation - phmo offset is always divisible by 16.
Example: Go to entity, go to the phmo tag, all the translations are divisible by 16 when the meta offset is subtracted.
-DeToX- wrote:No I know the padding's. Thats just of the tables.
You might want to remember that ..
The eof map padding is not a 'table'.. i can see where you're coming from though as its all 'CD CD..', but replacing those bytes with others (such as all '00 00') does nothing different, its basically just a pretty pattern =x
-DeToX- wrote:A phmo's Reflexive's Translation - phmo offset is always divisible by 16.
Example: Go to entity, go to the phmo tag, all the translations are divisible by 16 when the meta offset is subtracted.
Er...what are you trying to say..? I would of thought that'd just be because the sections before the translations are all padded to 512
You first said that any offset gained from translating a reflexive from the phmo meta, is always divisible by 16.
I then said that thats probably not the case, because the sections above it are probably just padded to 512.. re-reading your post i see that you meant reflexives that pointed still within the meta, whilst i though you meant raw, oops.
..and now you've said that phmo chunks are always divisible by 16. If so, then it probably is padding.. 16, 32, 64, 128, 512.. ya know =x
kornman00 wrote:While in theory a main repository is a good idea, this community's vocabulary is too diverse (when referring to one thing) and lacking.
