Real Time Tag Editor

[malolo420]

What makes it so you can't get it done right now?

Probably his lazy ass. Not trying to put him down, if it seemed that way.

[nuttyyayap]

You're right, it IS my lazy ass, i hate having to modify a few fields, compiling, then waiting 10 minutes for halo to load...

[Amit]

You're right, it IS my lazy ass, i hate having to modify a few fields, compiling, then waiting 10 minutes for halo to load...

10 Minutes? Jesus. It shouldn't take more than 20 seconds to start the game with tons of custom map files.

[nuttyyayap]

It takes 20 minutes when you have 24.3 GB of maps...

[Futzy]

Move them to a different folder when you don't need them.
Someone made a real time dependency swapper for halo pc a while ago, is this editing actual tags for ce or is it like that?

[ShadowSpartan]

Someone made a real time dependency swapper for halo pc a while ago, is this editing actual tags for ce or is it like that?

They are both editing the same thing, the tag data that is stored in memory. A dependency swapper only lets you edit the tag reference fields though.

[Amit]

It takes 20 minutes when you have 24.3 GB of maps...

Well then your user title definitely suits you because nobody should have that many maps in their map folder lol.

[Goldkilla]

RELEASE!!!! Guerrilla really is a pain on me sometimes... wait are you testing your map before its finished!

[FireScythe]

Bump! Had a few of ideas for this that would be pretty handy. First is to be able to open a tag based on its datum index, which i'd guess would be pretty simple to put in since you must be using the tag cache already. Second is to show the memory address for the tag fields when hovering over the field or ctrl click to copy it to the clipboard or something. Lastly, I couldn't see any in the video, but being able to view the contents of skips/pads would be useful, either by default or by using a console argument to unhide them.

[ShadowSpartan]

First is to be able to open a tag based on its datum index, which i'd guess would be pretty simple to put in since you must be using the tag cache already.

Wouldn't be hard to implement, but I don't see the point. It doesn't seem like it would be all that useful, care to explain your reasoning?

Second is to show the memory address for the tag fields when hovering over the field or ctrl click to copy it to the clipboard or something.

Well, currently the tooltip is reserved for extra information about a particular field. It displays the same text that guerilla does for it's tooltip. Yet again, I don't see much of a point for displaying the memory addresses for each field, because you can already edit any value as it is.

Lastly, I couldn't see any in the video, but being able to view the contents of skips/pads would be useful, either by default or by using a console argument to unhide them.

I suppose that would be useful for determining which pad/skip fields were used at runtime so that you could overwrite the ones that weren't, but Korn has always been against editing the stock tag definitions like that. Beyond that, what other purpose would it serve showing the fields, or was that your intent?

Sorry if it seems like I'm attacking your ideas, but I'm not. I welcome ideas, I just want to make sure that adding the new features will actually be useful and the time spent adding them will be justified.