Luclin models smooshed? - Page 23

Zaela · #**221** 09-12-2015, 09:13 PM

Quote:

Originally Posted by jcr4990 [You must be logged in to view images. Log in or Register.]

an exploit people were using on Red server to turn Skeleton models into Human models to circumvent people using AoN's to remove their nameplates.

Unless they added some specific checks for skeleton models, you could still do this using the same method as the luclin model workaround, though. With a little extra work, it might be possible to force nameplate to show up on plain classic skeles, too.

jcr4990 · #**222** 09-12-2015, 09:51 PM

I think we can all agree that Skeletons not having nameplates was an oversight by the original devs anyway right? I don't think anyone ever intended for AoN's to be a PvP strategy.

Zaela · #**223** 09-12-2015, 10:27 PM

The original devs probably didn't intend a lot of things, but I don't think that's what nostalgia for classic is really about.

Anyway, after thinking about it a little more, I felt like saying some stuff to no one in particular:

The reason locking the text of the global load file doesn't really prevent anything is this:

1. Models are loaded by name (well, by a 3-letter identifier like "HUM" for human male)
2. The client's model loader works in a "first thing loaded with this name wins" fashion -- whatever is loaded with the name "HUM" first blocks anything that tries to load with that name later.
3. None of the data files indicated by the globalload file are checked for integrity.

The result is that you can just shove any model you want into a file that is loaded before the "correct" one, and give it the name of the thing you want to replace. For Luclin models this is a bit limited in that there are only two (pointless) files in globalload that are flagged to allow them to load their extra-special player model animations correctly. NPC models like skeletons don't have this limitation and could be shoved into any file in globalload.

The easiest way to block this without also blocking people from doing harmless texture fixes/replacements would be to extract the .wld files from the .s3d files loaded by globalload and subject them to some integrity checks -- putting them through a few different crc / hash methods would probably be the lowest-effort way while still being fairly resilient against cheesing.

If you were only concerned about player models and skeletons, you could just move global_chr to the top of globalload and only do the integrity checks on its .wld file. This would ensure that all the player models and classic skeles are loaded before anything that could replace them. Edit: I think classic iksars are in a different global#_chr file so you'd need that one too.

Psionide · #**224** 09-12-2015, 11:19 PM

Am I the only one that actually LOVES that classic UI. Shit is just so fucking classic it is awesome.

Messie · #**225** 09-13-2015, 01:53 AM

Quote:

Originally Posted by Psionide [You must be logged in to view images. Log in or Register.]

Am I the only one that actually LOVES that classic UI. Shit is just so fucking classic it is awesome.

There are many of us who never used the Luclin models in the first place. Here we can observe those who did clawing desperately at the final strategies to get their non-classic aesthetic pleasures back. It's quite interesting to read.

Honestly I don't care what graphics people prefer, but I can say that if I was FORCED to use Luclin models, me and 90% (maybe more?) of the community would scream non-classic and the servers integrity would be in question. But since we are forced to NOT use Luclin models, it is very few who do complain about it. Hard to win an argument supporting Luclin models with that thought process. It is simply not classic to have Luclin models on. There is no debate.

So although I feel general sympathy for those who have a different gaming experience, and I wouldn't really mind if they found a way to fix it for individuals, I'm glad the models have been removed from the general public, in order to further progress this CLASSIC server's classic environment.

fiveeauxfour · #**226** 09-13-2015, 01:59 AM

Quote:

Originally Posted by Messie [You must be logged in to view images. Log in or Register.]

There is no debate

That's debatable.

Thiefboy777 · #**227** 09-13-2015, 07:32 AM

I never used Luclin models on p99, but I still can't understand why it bothers some people what the game looks like on someone else's screen.

Shjade · #**228** 09-13-2015, 07:44 AM

Quote:

Originally Posted by fiveeauxfour [You must be logged in to view images. Log in or Register.]

That's debatable.

Considering the forums can't even agree on what "classic" means, yes, yes it is.

@Thiefboy: apparently the different models also allowed for some kind of geometry exploits or something.

Swish · #**229** 09-13-2015, 08:20 AM

Quote:

Originally Posted by Psionide [You must be logged in to view images. Log in or Register.]

Am I the only one that actually LOVES that classic UI. Shit is just so fucking classic it is awesome.

Messie · #**230** 09-13-2015, 11:32 AM

Quote:

Originally Posted by Shjade [You must be logged in to view images. Log in or Register.]

Considering the forums can't even agree on what "classic" means, yes, yes it is.

Is this server currently planning on going to Luclin? The answer is no. Therefore, Luclin models should not exist on this server.

And before you try to say, "but who knows, maybe we will go to luclin one day!!!", let me just answer that for you now...

EVEN IF the server was planning on moving onto Luclin, only when we log in and see on the server MOTD - "Welcome to Luclin!" will the luclin models be classic.