|
||
|
|
#1 (permalink) |
|
Forum Novice
Join Date: Jun 2003
Location: hudson valley ny
Age: 38
Posts: 442
|
with the soon to come release of runuo 1.0 how about a seperate forum for script submissions that the author will certify has been tested and working with a stock release of 1.0 ...and if it doesnt...well then..everyone gets to beat him to a bloody pulp
![]() |
|
|
|
|
|
#3 (permalink) | |
|
I R TEH POSTING!!1!eleven
Join Date: Jan 2004
Posts: 1,617
|
See this thread? See how I prefaced it with "[b36]"? If I need to redo it for 1.0b1, I'll preface it with "[1.0b1]". Not a difficult concept, to most...
__________________
Get your C# documentation today! Quote:
abralka@doramail.com |
|
|
|
|
|
|
#4 (permalink) |
|
Account Terminated
|
C# is C#
C# 2.0 is comming out but if RunUO is released before then, it won't use and can't support that version of C# The release at that time would support it, but thats awhile as its at least 4-5 months based on Microsoft's Roadmap for the framework. The next version for Visual Studio is going to be Visual Studio 2005, the beta just started so I am told. I suspect by they will have some conferences for the upgrade then 3 months after that release the program. That would be the 1st or 2nd qtr of 2004 as they have no use to release their next version till then since Visual Studion 2003 was released in the last 8 months I believe. This suggestion is basicly pointless as C# is C# and you can make any script thats been posted EVER work with the next release. So its not really an issue unlike some emulators :-) |
|
|
|
|
|
#5 (permalink) |
|
Account Terminated
|
I bet nobody understands what I am talking about.
C# is not going to change for RunUO at least, for awhile. When the time comes, we will explain how to update the code, but the fact C# can be updated very easily to any release of RUnUO is still true. |
|
|
|
|
|
#6 (permalink) |
|
Forum Expert
Join Date: Jun 2003
Location: The Netherlands
Posts: 647
|
Never had any problems understanding you. Straight to the point, no bs and usually correct.
As for making a script section seperate with scripts that will always work with the current release. Well I don't think it is possible to predict all possible problems that can occur when mixing and matching random custom scripts. If properly written this should never be a problem, but there's not much software in general that doesn't contain a 'quick & dirty' solution every now and then and scripts here are not really a problem. As phantom said: attach a version number to your script and provide support for your creation and most of any problem can be resolved.
__________________
Captain The First _________________ Undisclosed shard (status: building since Feb. 2003) |
|
|
|
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|