Code Resources & Patch 1.23b

So, many of you already know of the new patch coming. This new patch will remove the return bug and add a lot of new natives.
However, this is bad news for some of us. With this new patch I risk saying that at least 30% - 40% of the resources in wc3c will be immediately deprecated, unusable, untestable and worst of all, unplayable. These resources are resources that are old and still use Kattana system, or simply because they have a return bug.
So, I would like to know, what is the administration of wc3c going to do about this??
Current solutions:
1 - doing nothing
2 - update the resources section deleting all old resources
3 - update the resources section fixing all old resources
4 - Mark all resources as under 1.23b. Then new resources become 1.23b resources. The old will have a 'Warning, this might not work in Warcraft 3 Versions with version 1.23b or higher' message
5 - Grave all resources that are not compatible with 1.23b and wait for the owners to re-submit them
6 - Create a new temporary section that only has 1.23b compatible resources

How is it going to be? Your opinion may be important =D

Solution 4:
Mark all resources as under 1.23b. Then new resources become 1.23b resources. The old will have a 'Warning, this might not work in Warcraft 3 Versions with version 1.23b or higher' message.

I suggest using solution 4.

Also allow to update to Version 1.23b, by a button or something.

+1
(and mark for the 1.23- maps requirment to 1.18 (due the GetLocationZ etc.))

as for me i may update uploaded systems here... we will see.
the key feature is s2i =|

Anyone who cares about their system working will have it updated almost immediately. Cohadar has already updated all of his systems to have a 1.23b compatability.

+1
Depends. You give Cohadar as 1 example, but other people such as Dusk (or me) did not updated any resources yet because we decided to wait for the new patch to be released and because we don't know how to make ubber use of the new natives.
I my case I don't need to know how to use new natives, but I will still wait for the new release before I update my spells. Besides, it looks like this new patch still has a few bugs (seems the return bug was not solved yet) so it is almost certain that the patch will suffer modifications before it's final release.

If we accepted stuff with LHV, etc., as resources, we'd have a problem.

We don't. A few things may have type casting problems (due to the stronger types) which might be a bit harder to fix, but most shouldn't really have any problems besides changing H2I for GetHandleId.

The scripts section is not that large, just unapprove everything that wouldn't work with the new patch if it is not updated within a few weeks...

?

Ya ... but the spell section ... many of it's spells use their own versions of LHV if you know what I mean ... what about those spells?

I suggest using the solution 4, while its showing most accepters and can be used again. (Just for the posability wc3 changes again back to return bug in a later patch).

If we hope for people update their scripts and spells immediatly, we can just close this side. Most of the spells and systems authors are not really active anymore, because they are busy with reallife.

I can't agree just hoping for those to update their spells and systems, so we know if they work or not.

Simply group maps by version, and display warnings for compatibilty.

Fledermaus imagine i know what i am talking about...

That's hard to do.. :p

Any spell that uses LHV-like systems was decapricated anyway, so so what?

My question is, if we don't use solution 4 (suggested by Anachron) what do we do with the spells ?? Delete them, remake them or we simply do nothing ? Doing nothing will allow the resources section to have (even more) outdated resources that don't work properly.
The main point of this thread, is to find a solution that prevents what I explained before from happening.

So Griffen, you also vote 4 ?
PS: I bet Griffen will vote for option 5 - none of them xD

I suggest to open a subforum and move all the problematic code there. So the authors or other person update them and resubmit a workable version. But I'd wait until the patch becomes release just in case other stuff get added or improved.