We probably don't need a log of every single update. Especially if you can't show screenshots or talk about it much. Not every project thread needs to be 50 pages.

Someone should upload a video playing through it, where you don't react to anything or even talk about what you're playing at all. In other words, an Adminn style video.

Lol my part in this is done. I'm not planning on doing anything else about this. I already assume no one is willing to touch the renderer code, so it is what it is.

I provided a film of it in the other thread. I guess someone should check to see how far back A1 can play it and see if it happens in all versions. I don't remember if film compatibility for a1 broke any time recently. For what it's worth, I certainly don't remember this ever happening back in the d...

OK, fair enough I guess. Although if we're talking about actually stickying this (who knows if that's going to happen in the first place), it seems like it would make more sense to link to the downloads themselves for the projects that are complete. I'm not sure the pfhorums threads are particularly...

Your description is fine, but taking the time to provide links to everything except Yuge, given your vocal opinions about it, seems pretty questionable to me. You're right though, the fact that you mentioned it at all is kind of surprising to me.

Or maybe if you sticky it, make it a little less biased against Yuge. Not even providing a link? lul

It has to do with the level geometry, so maybe the way Eternal's maps are made just don't result in this glitch happening very often. It happens constantly in close range for AOPID, so I guess you want to avoid a bunch of 1 WU squares

I don't think it's a matter of having more tolerance, it's just that there's not much we can do about it. Going to a super old A1 isn't an option for a lot of people.

Yeah, it's really annoying :C

When I first created a script for precipitation, you couldn't move scenery or effects, so I used projectiles. The only other option would be killing monsters and letting them fall (this caused the radar to be useless). Apparently projectiles are the least efficient because the engine will have to ca...

I think at this point everyone just uses your precipitation stuff from snowfrog. So the decision to use scenery came from you. I ended up using effects for stuff in aopid instead of scenery, because of the scenery bug. I don't work on Eternal, so I never made any decisions about their precipitation.

Annotations wouldn't solve the problem of deleting scenery though. So if you have the plugin enabled, save your game, and then turn it off and reload your game, you'd have a bunch of scenery objects frozen in the air. You still need 1.3 to clean it up.

Not that it probably matters, but is there a reason not to just set the fog color for the local player based on what liquid they happen to be in? Then everyone will see the color they're supposed to.

The media fog script I wrote changes fog globally depending on what media players are under, and will sometime show a player the wrong colo u r fog. Sounds like a lot of work for a bad result, then. If it were dependent on a plugin, then not everyone is executing the same code, therefore not everyo...

Actually yeah, your netscript idea would work. A plugin to set one variable to indicate it's on. It would only get used if the number of players is 1. A second variable that is set by a netscript, and it only gets used if there are multiple people in the game.

If the logic to enable rain is that the local player is the gatherer, and they have the plugin enabled, then the gatherer will get rain and no one else will. This is how you get OOS.

Nothing in lua is shared across the network. For example if you had this code: if Players.local_player.name == "Aaron" then Level.fog.color = whatever end It will only turn the Fog color for you to whatever. Everyone else's fog will remain the same as it was before. This is why there's a w...

That's not how it works. Variables don't get shared across netgames. Maybe I helped her with some specific issue she was having with it, I don't know. The overall concept of the script never made any sense to me, so I don't even know what it does. Also changing the fog to different colors based on t...

I don't remember working on anything like that, so you must be thinking of someone else. If it's based on what player is in what kind of media, then you don't have to pass information around, just detect where the players are. The most you could do to pass information is to have one player tap the m...

You can't tell what plugins/settings other players have. So #1 and #2 won't work. If the number of players in the game is > 1, disable it across the board IMO.

Yes, shared lua state is a thing in 1.3, as well as the fix to deleting scenery with lua. Both of those fixes make this possible. For multiplayer, I'd just say get rid of the precipitation. Multiplayer has enough problems as it is. For the 2 of you that actually play Eternal multiplayer, you can mak...

The plugin sets some variable in the shared state saying "hey, i'm active". It'd be like 3 lines of code or something. Then the embedded lua checks for this variable to see whether or not to enable precipitation. If it's not active, you'll have to check for previously created precipitation...

As to precipitation, is there a way to make Lua execution (1) dependent upon a plugin (2) that only executes in specific levels? I know I've told Eternal devs exactly how to do this before, but it requires AlephOne 1.3. I can't remember if you were there for those discussions or not, but I never re...