Re: [crossfire] Code cleaning, part 2

IMO, Old_Mode could go away. It isn't used by clients - rather it dates back before we had clients, where the method of connecting was to connect to the crossfire server (on that port), and then do something like 'add myhost:0' - at which point the server would open an x-connection to your

Re: [crossfire] Summary, was Re: The future of Crossfire

The lore idea, and discussion on it, I thought were really good. It was just something never finished - lots of things like that in crossfire. Yes, which is why we need a goal to reach, so we can focus on it. Agreed. We need client [sound] support, though. Yes, I was planning on

[crossfire] Materials

Hello. I'd dug some in the material code, and it is quite messy. But I'm not sure how to fix/change it. Here is how it works. Material is used for saving throws against attacktypes (against fire, ice, ...). When NEW_MATERIAL_CODE is defined, material will also affect an item's resistances,

Re: [crossfire] map design guideline (was: Summary)

introduce a map design guideline. Only maps which won't violate the policy are allowed to add / stay. Yes. I'd be slightly less restrictive, though - you'd be allowed to commit part of a quest, adding other elements later on, provided you document somewhere what you plan to add / you commit

Re: [crossfire] map design guideline (was: Summary)

There is already a map guide document that more or less describes good vs bad maps. However, a lot of maps predate that. Not trapping big monsters is difficult - unless you have a completely empty room, it is hard for something like a big demon not to be 'trapped' in some way. and if

Re: [crossfire] Materials

Nicolas Weeger wrote: Hello. I'd dug some in the material code, and it is quite messy. But I'm not sure how to fix/change it. Here is how it works. Material is used for saving throws against attacktypes (against fire, ice, ...). When NEW_MATERIAL_CODE is defined, material will

Re: [crossfire] Protocol version

Nicolas Weeger wrote: Hello. (this only concerns trunk) I bumped server-side s-c version to 1028 (was 1027), to denote massive removal. But it was suggested on the list to change s-c et c-s versions to 2000, to have a nice version. This would enable to remove some non required

[crossfire] Documentation / handbook / playbook / spoilers

Hello. The doc subdirectory (apart hopefully Developers) is a slight mess, with many many non working or obsolete things. Currently, there following documentations are defined: * spoiler book * player book * spell list * handbook The generation is broken for many things, so we should either